Orca CLI
stablyai/orca
Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…
Install, verify, and recover the modern Spec Kitty 2.0.11+ operating surface.
$ npx skills add spec-kitty/spec-kitty --skill spec-kitty-setup-doctor -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install spec-kitty/spec-kitty spec-kitty-setup-doctor --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/spec-kitty/spec-kitty.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/charter/offering/skills/spec-kitty-setup-doctor .claude/skills/spec-kitty-setup-doctor && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "spec-kitty-setup-doctor" agent skill from https://github.com/spec-kitty/spec-kitty/tree/main/src/charter/offering/skills/spec-kitty-setup-doctor into .claude/skills/spec-kitty-setup-doctor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-kitty-setup-doctor", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/spec-kitty/spec-kitty/tree/main/src/charter/offering/skills/spec-kitty-setup-doctorType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add spec-kitty/spec-kitty --skill spec-kitty-setup-doctor -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install spec-kitty/spec-kitty spec-kitty-setup-doctor --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/spec-kitty/spec-kitty.git skills-src && mkdir -p .agents/skills && cp -r skills-src/src/charter/offering/skills/spec-kitty-setup-doctor .agents/skills/spec-kitty-setup-doctor && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "spec-kitty-setup-doctor" agent skill from https://github.com/spec-kitty/spec-kitty/tree/main/src/charter/offering/skills/spec-kitty-setup-doctor into .agents/skills/spec-kitty-setup-doctor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-kitty-setup-doctor", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add spec-kitty/spec-kitty --skill spec-kitty-setup-doctor -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install spec-kitty/spec-kitty spec-kitty-setup-doctor --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/spec-kitty/spec-kitty.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/src/charter/offering/skills/spec-kitty-setup-doctor .cursor/skills/spec-kitty-setup-doctor && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "spec-kitty-setup-doctor" agent skill from https://github.com/spec-kitty/spec-kitty/tree/main/src/charter/offering/skills/spec-kitty-setup-doctor into .cursor/skills/spec-kitty-setup-doctor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-kitty-setup-doctor", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/spec-kitty/spec-kitty.git --path src/charter/offering/skills/spec-kitty-setup-doctor--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add spec-kitty/spec-kitty --skill spec-kitty-setup-doctor -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install spec-kitty/spec-kitty spec-kitty-setup-doctor --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/spec-kitty/spec-kitty.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/src/charter/offering/skills/spec-kitty-setup-doctor .gemini/skills/spec-kitty-setup-doctor && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "spec-kitty-setup-doctor" agent skill from https://github.com/spec-kitty/spec-kitty/tree/main/src/charter/offering/skills/spec-kitty-setup-doctor into .gemini/skills/spec-kitty-setup-doctor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-kitty-setup-doctor", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install spec-kitty/spec-kitty spec-kitty-setup-doctorInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add spec-kitty/spec-kitty --skill spec-kitty-setup-doctor -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/spec-kitty/spec-kitty.git skills-src && mkdir -p .github/skills && cp -r skills-src/src/charter/offering/skills/spec-kitty-setup-doctor .github/skills/spec-kitty-setup-doctor && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "spec-kitty-setup-doctor" agent skill from https://github.com/spec-kitty/spec-kitty/tree/main/src/charter/offering/skills/spec-kitty-setup-doctor into .github/skills/spec-kitty-setup-doctor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-kitty-setup-doctor", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add spec-kitty/spec-kitty --skill spec-kitty-setup-doctor -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install spec-kitty/spec-kitty spec-kitty-setup-doctor --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/spec-kitty/spec-kitty.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/src/charter/offering/skills/spec-kitty-setup-doctor .opencode/skills/spec-kitty-setup-doctor && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "spec-kitty-setup-doctor" agent skill from https://github.com/spec-kitty/spec-kitty/tree/main/src/charter/offering/skills/spec-kitty-setup-doctor into .opencode/skills/spec-kitty-setup-doctor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-kitty-setup-doctor", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
spec-kitty-setup-doctorInstall, verify, and recover the modern Spec Kitty 2.0.11+ operating surface.
Spec Kitty Setup Doctor is an agent skill from spec-kitty/spec-kitty. Install, verify, and recover the modern Spec Kitty 2.0.11+ operating surface. Triggers: "set up Spec Kitty", "skills missing", "next is blocked", "runtime is broken", "doctrine assets are missing", "my agent can't find the skills". Does NOT handle: generic coding questions with no Spec Kitty context, direct runtime loop advancement, or editorial glossary maintenance.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/agent-path-matrix.md` and `references/common-failure-signatures.md`).
It sits in Agent Workflows. The repository describes itself as: Spec-Driven Development with organizational governance. Specs tell AI agents what to build; Charter governs how they build it. Git-native missions, enforceable workflows, and… The licence is MIT.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit e533131. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 1 file in scripts/, which the agent can run.
Shell commands in SKILL.md call:
pipxgitFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use pipx and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Spec Kitty Setup Doctor loads about 1.4k tokens when it runs, and up to ~3.9k if it reads all its reference files. Until then it costs about 98 tokens; SKILL.md has 589 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from spec-kitty/spec-kitty at commit e533131, republished under its MIT licence (© spec-kitty). 589 words, ~1,410 tokens.
.claude/skills/spec-kitty-setup-doctor/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.Diagnose and repair the Spec Kitty installation for the current project and agent.
Use this skill when the user reports that Spec Kitty is not working, skills are missing, slash commands are unavailable, or the runtime environment appears broken.
Determine the active agent, repository state, and working directory.
What to check:
.kittify/ directory exists (indicates prior initialization)Commands:
git rev-parse --show-toplevel
ls .kittify/config.yaml
spec-kitty --versionExpected outcome: You know the agent identity, repo root path, and whether Spec Kitty was previously initialized.
Check that skill roots, wrapper roots, manifest, and generated artifacts are present.
What to check:
references/agent-path-matrix.md).kittify/skills-manifest.json for legacy canonical skills and/or
.kittify/command-skills-manifest.json for command-skill agentsCommands:
spec-kitty doctor skills --jsonIf spec-kitty is not installed:
pipx install spec-kitty-cli
pipx ensurepath
spec-kitty --versionExpected outcome: spec-kitty doctor skills --json reports a healthy command
and skill surface, or lists specific missing/drifted files.
Verify that the working environment meets runtime requirements.
What to check:
.kittify/config.yaml is present and validCommands:
spec-kitty agent tasks status
spec-kitty agent config statusExpected outcome: Status output shows the current kanban board, configured agents, and active missions without errors.
Match observed symptoms against known failure patterns.
What to check:
Consult references/common-failure-signatures.md for a catalog of known issues.
Common patterns include:
.kittify/ directory missing or corruptedHow to diagnose:
spec-kitty doctor skills --json
spec-kitty agent config statusReview error messages and match them against the failure signatures. Each signature includes a symptom, cause, and deterministic recovery step.
Expected outcome: You have identified the specific failure pattern(s) affecting this installation.
Apply deterministic recovery steps for each identified issue.
Recovery actions by issue type:
| Issue | Recovery Command |
|---|---|
| Missing skill files | spec-kitty doctor skills --fix |
| Missing wrapper root | spec-kitty doctor skills --fix |
| Missing skill root | spec-kitty doctor skills --fix |
| Manifest drift | spec-kitty doctor skills --fix |
| Runtime not found | spec-kitty init . --ai <agent> |
| Corrupted config | Back up and remove .kittify/config.yaml, then run spec-kitty init . --ai <agent> |
Commands:
# Full re-initialization (fixes most issues)
spec-kitty init . --ai <agent>
# Targeted skill repair (preserves existing config)
spec-kitty doctor skills --fixExpected outcome: After recovery, spec-kitty doctor skills --json reports no
issues and spec-kitty agent tasks status shows a healthy installation.
After recovery is complete, point the user to the correct next step.
Decision tree:
spec-kitty init . --ai <agent>/spec-kitty.specifyspec-kitty agent tasks status/spec-kitty.implementspec-kitty doctor skills --jsonWhat to communicate:
references/common-failure-signatures.md
for additional patterns or filing an issuereferences/agent-path-matrix.md -- Agent skill roots and wrapper roots for supported agents; verify against AI_CHOICES, AGENT_COMMAND_CONFIG, and AGENT_SKILL_CONFIGreferences/common-failure-signatures.md -- Known failure patterns with symptom/cause/recovery© spec-kitty, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 3 other files (scripts, references) in src/charter/offering/skills/spec-kitty-setup-doctor of spec-kitty/spec-kitty.
Open the folder on GitHubat commit e533131
Spec Kitty Setup Doctor next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Spec Kitty Setup Doctor this skillspec-kitty/spec-kitty | 1.7k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Orca CLIstablyai/orca | 88k | 2 repos | ~593 | Automated safety check: Pass | MIT | |
| OpenSpec Guided OnboardingFission-AI/OpenSpec | 71k | 1 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Claude Code Plugin Structureanthropics/claude-plugins-official | 38k | 10 repos | ~3.4k | Automated safety check: Pass | Apache-2.0 | |
| Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills | 21k | — | ~1.9k | Automated safety check: Pass | MIT | |
| O2 Review Loopopenobserve/openobserve | 22k | — | ~3.7k | Automated safety check: Pass | AGPL-3.0 |
stablyai/orca
Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…
Fission-AI/OpenSpec
Walks you through a complete OpenSpec workflow cycle with narration while doing real work in your codebase.
anthropics/claude-plugins-official
Explains the directory layout, plugin.json manifest and component organization of a Claude Code plugin, including auto-discovery and portable paths.
KKKKhazix/khazix-skills
Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.
openobserve/openobserve
Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.
uditgoenka/autoresearch
Runs an autonomous modify, verify, keep-or-discard loop against any metric, with subcommands for planning, debugging, fixing, security audits, shipping and more.
spec-kitty/spec-kitty
Explain Spec Kitty work with compact, checkable visuals. An agent skill from spec-kitty/spec-kitty.
spec-kitty/spec-kitty
Understand how Spec Kitty manages git: what git operations Python handles automatically, what agents must do manually, worktree lifecycle, auto-commit behavior, merge execution, and the safe-commit…
spec-kitty/spec-kitty
Curate and apply canonical terminology across Spec Kitty missions.
spec-kitty/spec-kitty
Understand how Spec Kitty missions work: the 4 built-in mission types, how they define workflows via step contracts and action indices, how missions and work packages relate, how templates are…
spec-kitty/spec-kitty
Teach agents and external systems how to use spec-kitty orchestrator-api to drive workflows from outside the host CLI.
spec-kitty/spec-kitty
Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback.
Categories
Install, verify, and recover the modern Spec Kitty 2.0.11+ operating surface. Spec Kitty Setup Doctor is an agent skill from spec-kitty/spec-kitty.11+ operating surface.
Spec Kitty Setup Doctor fits situations like: agent Workflows work in your project.
Run `npx skills add spec-kitty/spec-kitty --skill spec-kitty-setup-doctor -a claude-code`. Or copy the skill folder (src/charter/offering/skills/spec-kitty-setup-doctor in spec-kitty/spec-kitty) into .claude/skills/spec-kitty-setup-doctor in your project. Claude Code loads it when a task matches its description.
Run `npx skills add spec-kitty/spec-kitty --skill spec-kitty-setup-doctor -a codex`. Or copy the skill folder (src/charter/offering/skills/spec-kitty-setup-doctor in spec-kitty/spec-kitty) into .agents/skills/spec-kitty-setup-doctor in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add spec-kitty/spec-kitty --skill spec-kitty-setup-doctor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/spec-kitty-setup-doctor, .gemini/skills/spec-kitty-setup-doctor, .github/skills/spec-kitty-setup-doctor and .opencode/skills/spec-kitty-setup-doctor in your project.
Going by SKILL.md and its folder, Spec Kitty Setup Doctor needs the command-line tools its instructions call (pipx and git).
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Spec Kitty Setup Doctor is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.5k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Spec Kitty Setup Doctor: Orca CLI (stablyai/orca, 88k stars), OpenSpec Guided Onboarding (Fission-AI/OpenSpec, 71k stars), Claude Code Plugin Structure (anthropics/claude-plugins-official, 38k stars) and Neat-Freak Knowledge Closeout (KKKKhazix/khazix-skills, 21k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
spec-kitty (a GitHub organization) maintains it in spec-kitty/spec-kitty, which has 1,678 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 9, 2026.
Source: spec-kitty/spec-kitty on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.