Speckit Check

github/speckit-check

Check the local environment for Spec Kit by running `specify check` (and `specify version`). USE FOR: verifying required tools are installed, diagnosing a broken spec-kit setup, reporting CLI version/feature capabilities. DO NOT USE FOR: installing or upgrading the CLI itself (use the speckit-self skill).

340 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/github/spec-kit-copilot --skill speckit-check

The instruction itself

4 sections, as written by the author

Spec Kit — check & version

Inspect the local Spec Kit environment with the Specify CLI. This skill exposes

the read-only specify check and specify version commands.

> Prerequisite: needs the specify CLI. If specify --version fails, install it

> with the speckit-cli-setup skill first.

When to use

Before/after specify init to confirm required tools are present.
To report the installed CLI version and feature capabilities.

How to invoke

# Check that all required tools are installed
specify check

# Show version and system information
specify version

# Show local CLI feature capabilities
specify version --features

# Machine-readable capabilities
specify version --features --json

Notes

These commands are read-only and safe to run without confirmation.
If the user reports a version problem, hand off to the speckit-self skill to

check for and apply CLI upgrades.

How to use it

Copy the folder

Take github/speckit-check from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.