Agent skill
speckit-check
Run `specify check` to verify that Spec Kit required tools (git, claude, gemini, code, cursor-agent, windsurf, qwen, opencode, codex, shai, qoder, etc.) are installed and available; interpret results and suggest next steps. Use when the user says "check Spec Kit environment", "specify not working", or "slash commands not showing".
Install this agent skill to your Project
npx add-skill https://github.com/partme-ai/full-stack-skills/tree/main/skills/speckit-skills/speckit-check
SKILL.md
Spec Kit Check Skill
Run specify check to verify that the Spec Kit CLI and required tools (git, AI agents, editors) are installed and detectable. Use this after speckit-install or speckit-initial to confirm the environment, or when the user reports that slash commands are missing or specify does not work.
When to Use
- After initializing a project with speckit-initial to confirm the environment.
- When slash commands do not appear or the user says "specify not working".
- In CI or scripts to ensure dependencies are present before running Spec Kit steps.
Prerequisites
- Specify CLI must be installed (see speckit-install). If
specifyis not in PATH, direct the user to speckit-install before runningspecify check.
Workflow
-
Ensure CLI is available
- If the user has not installed the CLI or reports "specify: command not found", direct them to speckit-install first. Do not run
specify checkuntilspecifyis available.
- If the user has not installed the CLI or reports "specify: command not found", direct them to speckit-install first. Do not run
-
Run the check
- From the project root (or target directory):
specify check - The command reports which tools are detected (e.g. git, claude, gemini, code, cursor-agent, windsurf, qwen, opencode, codex, shai, qoder) and which are missing or not in PATH.
- From the project root (or target directory):
-
Interpret the output
- All required tools present: Environment is ready; suggest proceeding with speckit-constitution or speckit-specify.
- CLI missing: Direct to speckit-install.
- Agent or editor missing: Suggest installing the corresponding Agent/editor or adding its executable to PATH. If the user only needs templates and
.specify/(no slash commands), suggest re-running speckit-initial with--ignore-agent-tools.
-
Summarize and recommend
- Provide a short summary: what is OK, what is missing.
- Give concrete next steps: install CLI (speckit-install), re-init with different agent (speckit-initial), or fix PATH / install Agent.
Outputs
- Summary: Which tools are detected and which are missing.
- Recommendations: List of next actions (install CLI, run init, install Agent, add to PATH, or use
specify init --ignore-agent-tools).
Next Steps
- If something is missing: use speckit-install (for CLI) or speckit-initial (to re-init or use
--ignore-agent-tools), or install the missing Agent/editor. - If check passes: proceed with speckit-constitution or speckit-specify.
Example Output (reference)
See examples/sample-output.md for an example of specify check output and how to interpret it.
Troubleshooting
- "specify: command not found": Use speckit-install.
- Agent reported as missing: Ensure the Agent app is installed and its CLI or executable is on PATH; or use
specify init --ignore-agent-toolsif only templates are needed. - Git missing: Install git or run
specify init --no-gitif git is not required for the workflow.
References
- GitHub spec-kit — CLI: specify check
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
ocrmypdf-batch
OCRmyPDF batch processing skill — process multiple PDFs, Docker automation, shell scripting, and CI/CD integration. Use when the user needs to OCR many PDFs, set up automated OCR pipelines, or integrate OCR into workflows.
ocrmypdf-optimize
OCRmyPDF optimization skill — compress PDFs, configure PDF/A output, JBIG2 encoding, and lossless optimization. Use when the user needs to reduce PDF file size, create archival PDF/A files, or optimize OCR output.
ocrmypdf-image
OCRmyPDF image processing skill — deskew, rotate, clean, despeckle, remove border from scanned documents. Use when the user needs to improve scanned PDF quality, fix skewed pages, remove noise, or clean up scanned documents before OCR.
ocrmypdf-api
OCRmyPDF Python API and plugin skill — use OCRmyPDF programmatically from Python, integrate with applications, and extend with plugins (EasyOCR, PaddleOCR, AppleOCR). Use when the user needs to call OCRmyPDF from Python code, build OCR pipelines, or use alternative OCR engines.
ocrmypdf
OCRmyPDF core skill — add searchable OCR text layer to scanned PDFs, convert images to searchable PDFs, support 100+ languages via Tesseract. Use when the user needs to OCR a PDF, make a scanned PDF searchable, or extract text from scanned documents.
svelte
Guides Svelte and SvelteKit development including reactive components, stores, transitions, lifecycle hooks, SSR, file-based routing, and deployment. Use when the user needs to build Svelte components, create SvelteKit applications, implement reactivity patterns, or configure Svelte with Vite.
Didn't find tool you were looking for?