partme-ai/speckit-check
skills/speckit-skills/speckit-check/SKILL.md
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 --global
skillsauthnpx skillsauth add partme-ai/full-stack-skills speckit-checkInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 10, 2026, 9:07 AM28.6s2 files scanned
SKILL.md
- name:
- speckit-check
- description:
- 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".
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
Related Skills
partme-ai/uniapp-project
development
VerifiedTrustedCommunity
Provides per-component and per-API examples with cross-platform compatibility details for uni-app, covering built-in components, uni-ui components, and APIs (network, storage, device, UI, navigation, media). Use when the user needs official uni-app components or APIs, wants per-component examples with doc links, or needs platform compatibility checks.
456SKILL.mdUpdated Jun 4, 2026
partme-ai/uniapp-project-creator
tools
VerifiedTrustedCommunity
Creates new uni-app projects via the official CLI or HBuilderX with Vue 2/Vue 3 template selection, manifest.json and pages.json configuration, and directory structure setup. Use when the user wants to scaffold a new uni-app project, initialize project files with a single command, or set up the development environment.
456SKILL.mdUpdated Jun 4, 2026
partme-ai/uniapp-plugin
tools
VerifiedTrustedCommunity
Browses, installs, configures, and manages plugins from the uni-app plugin market (ext.dcloud.net.cn) including component plugins, API plugins, and template plugins with dependency handling. Use when the user needs to find and install uni-app plugins, configure plugin settings, manage plugin dependencies, or integrate third-party components.
456SKILL.mdUpdated Jun 4, 2026
partme-ai/uniapp-native-plugin
tools
VerifiedTrustedCommunity
Develops native Android and iOS plugins for uni-app including module creation, JavaScript-to-native communication, and plugin packaging for distribution. Use when the user needs to build custom native modules, extend uni-app with native capabilities (camera, Bluetooth, sensors), or create publishable native plugins.
456SKILL.mdUpdated Jun 4, 2026