Operate Spec Kitty tracker workflows, tracker service discovery, binding, hosted routing, and tracker recovery.
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add Priivacy-ai/spec-kitty --skill spk-team-tracker --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Spk Team Tracker?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/priivacy-ai-spk-team-tracker)More formats (shields.io, HTML) on the badges page.
---
name: spk-team-tracker
description: "Operate Spec Kitty tracker workflows, tracker service discovery, binding, hosted routing, and tracker recovery."
---
# spk-team-tracker
Use this skill when the user asks about tracker setup, tracker sync, tracker
binding, hosted tracker routing, or tracker diagnostics.
## Flow
1. Inspect tracker status and service discovery output.
2. Confirm the active project and tracker binding.
3. Use hosted sync only when the workflow requires it.
4. Route auth failures to `spk-team-auth`.
5. Route transport/offline replay failures to `spk-team-sync`.
## Local Dev Note
When testing tracker flows from the CLI on this computer, opt into hosted mode
with `SPEC_KITTY_ENABLE_SAAS_SYNC=1`. Prefer writing it once into
`.kittify/.kitty.env` (repo-scoped) or `${SPEC_KITTY_HOME}/.kitty.env`
(machine-wide) over a per-shell `export` — a shell export arms every project
that shell subsequently touches, not just the one you're testing. Run
`spec-kitty doctor env-file` to confirm which tier is active.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
