Agent skill

Spec Verify

Verifies implementation completeness against SPEC.md specification.

No licenceAuto-check passedTesting & QA

Install Spec Verify

skills CLI

$ npx skills add jh941213/my-cc-harness --skill spec-verify -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install jh941213/my-cc-harness spec-verify --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/jh941213/my-cc-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills_en/spec-verify .claude/skills/spec-verify && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "spec-verify" agent skill from https://github.com/jh941213/my-cc-harness/tree/main/skills_en/spec-verify into .claude/skills/spec-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-verify", 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

$skill-installer install https://github.com/jh941213/my-cc-harness/tree/main/skills_en/spec-verify

Type 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.

skills CLI

$ npx skills add jh941213/my-cc-harness --skill spec-verify -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install jh941213/my-cc-harness spec-verify --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jh941213/my-cc-harness.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills_en/spec-verify .agents/skills/spec-verify && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "spec-verify" agent skill from https://github.com/jh941213/my-cc-harness/tree/main/skills_en/spec-verify into .agents/skills/spec-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-verify", 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.

skills CLI

$ npx skills add jh941213/my-cc-harness --skill spec-verify -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install jh941213/my-cc-harness spec-verify --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jh941213/my-cc-harness.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills_en/spec-verify .cursor/skills/spec-verify && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "spec-verify" agent skill from https://github.com/jh941213/my-cc-harness/tree/main/skills_en/spec-verify into .cursor/skills/spec-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-verify", 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

$ gemini skills install https://github.com/jh941213/my-cc-harness.git --path skills_en/spec-verify

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add jh941213/my-cc-harness --skill spec-verify -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install jh941213/my-cc-harness spec-verify --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jh941213/my-cc-harness.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills_en/spec-verify .gemini/skills/spec-verify && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "spec-verify" agent skill from https://github.com/jh941213/my-cc-harness/tree/main/skills_en/spec-verify into .gemini/skills/spec-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-verify", 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.

GitHub CLI

$ gh skill install jh941213/my-cc-harness spec-verify

Installs 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).

skills CLI

$ npx skills add jh941213/my-cc-harness --skill spec-verify -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/jh941213/my-cc-harness.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills_en/spec-verify .github/skills/spec-verify && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "spec-verify" agent skill from https://github.com/jh941213/my-cc-harness/tree/main/skills_en/spec-verify into .github/skills/spec-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-verify", 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.

skills CLI

$ npx skills add jh941213/my-cc-harness --skill spec-verify -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install jh941213/my-cc-harness spec-verify --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jh941213/my-cc-harness.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills_en/spec-verify .opencode/skills/spec-verify && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "spec-verify" agent skill from https://github.com/jh941213/my-cc-harness/tree/main/skills_en/spec-verify into .opencode/skills/spec-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-verify", 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.

Facts

Skill name: spec-verify
GitHub stars: 126
Token cost: ~654 tokens
SKILL.md length: 122 words
Files: 1
Skills in repo: 62
Repo updated: Aug 3, 2026
First seen: Oct 7, 2026
Licence: None found

At a glance

Verifies implementation completeness against SPEC.md specification.

Works in 3 steps: Create Sub-Agent → Address Feedback → Completion Report
Specification verification
SKILL.md covers Triggers, Workflow, Verification Checklist and Core Principles
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Spec Verify is an agent skill from jh941213/my-cc-harness. Verifies implementation completeness against SPEC.md specification. Triggers on: spec verify, spec-verify, specification verification, implementation verification. NOT for: code review, unit tests, build verification.

Its SKILL.md is about 650 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Unit testing.

When your agent uses it

Specification verification
Implementation verification

Example prompts

“Use the spec-verify skill to verify implementation completeness against SPEC.md specification”
“/spec-verify”

Requirements

Pre-approved tools (allowed-tools): Read, Grep, Glob, Write, Task, AskUserQuestion

Workflow steps

3 steps, taken from the step headings in SKILL.md.

Create Sub-Agent
Address Feedback
Completion Report

What it can do on your machine

Read from SKILL.md and the folder at commit e9210e2. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Read
- Grep
- Glob
- Write
- Task
- AskUserQuestion
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Spec Verify loads about 654 tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 122 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~57
When it runs · the whole SKILL.md, loaded when a task matches: ~654

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.

Safety

Auto-check passed

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); files beside SKILL.md are not scanned.

SKILL.md

Without a licence we can't republish the file, so here is its outline and opening line. It has 122 words (~654 tokens).

“Skill for verifying completion after specification-based work.”

— opening of SKILL.md by jh941213

name: spec-verify
allowed-tools: Read, Grep, Glob, Write, Task, AskUserQuestion
user-invocable: true
disable-model-invocation: true
context: fork

Read the full SKILL.md on GitHub

Files

Just SKILL.md in skills_en/spec-verify of jh941213/my-cc-harness.

Open the folder on GitHubat commit e9210e2

Compare with similar skills

Spec Verify 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.

Spec Verify compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Spec Verify this skilljh941213/my-cc-harness	126	—	~654	Automated safety check: Pass	None	2 mo ago
Rust TDD Workflowrtk-ai/rtk	83k	—	~753	Automated safety check: Notes	Apache-2.0	yesterday
RTK Filter TDD in Rustrtk-ai/rtk	83k	—	~1.9k	Automated safety check: Notes	Apache-2.0	yesterday
Test GuardamElnagdy/guard-skills	1.3k	2 repos	~2.1k	Automated safety check: Pass	MIT	3 mo ago
Creating A Packagec15t/c15t	1.9k	—	~913	Automated safety check: Pass	Apache-2.0	today
Run Pre Gen ChecksGoogleCloudPlatform/magic-modules	974	—	~492	Automated safety check: Pass	Custom licence	today

Similar skills

Rust TDD Workflow
rtk-ai/rtk
Enforces red-green-refactor for Rust work, with idiomatic test patterns, a naming convention and a pre-commit gate of cargo fmt, clippy and test.
83k GitHub stars~753 tokensUpdated yesterday
Testing & QAAuto-check: notes
RTK Filter TDD in Rust
rtk-ai/rtk
Enforces red-green-refactor for new RTK output filters in Rust, using real captured fixtures, snapshot tests with insta and token-savings assertions.
83k GitHub stars~1.9k tokensUpdated yesterday
Testing & QAAuto-check: notes
Test Guard
amElnagdy/guard-skills
Reviews newly written or edited tests against nine rules that cut test bloat, such as mock-heavy checks and near-duplicate cases, before they are committed.
1.3k GitHub starsUsed in 2 repos~2.1k tokens
Testing & QAAuto-check passed
Creating A Package
c15t/c15t
Scaffold a new workspace package in the c15t monorepo. An agent skill from c15t/c15t.
1.9k GitHub stars~913 tokensUpdated today
Testing & QAAuto-check passed
Run Pre Gen Checks
GoogleCloudPlatform/magic-modules
Run fast static checks that don't require generating downstreams, including git submodule verification, gofmt formatting, YAML linting, template validation (version-guard and unused-tmpl), mmv1 core…
974 GitHub stars~492 tokensUpdated today
Testing & QAAuto-check passed
Simple Modern Uv
jlevy/simple-modern-uv
Start, selectively modernize, fully migrate, or update Python projects using simple-modern-uv practices: uv, ruff, BasedPyright, pytest, GitHub Actions CI, and tag-driven PyPI publishing.
301 GitHub stars~1.9k tokensUpdated 1 mo ago
Testing & QAAuto-check passed

Questions about Spec Verify

What does Spec Verify do?

Verifies implementation completeness against SPEC.md specification. Spec Verify is an agent skill from jh941213/my-cc-harness.md specification.

When should I use Spec Verify?

Spec Verify fits situations like: specification verification; implementation verification.

How do I install Spec Verify in Claude Code?

Run `npx skills add jh941213/my-cc-harness --skill spec-verify -a claude-code`. Or copy the skill folder (skills_en/spec-verify in jh941213/my-cc-harness) into .claude/skills/spec-verify in your project. Claude Code loads it when a task matches its description.

How do I install Spec Verify in Codex?

Run `npx skills add jh941213/my-cc-harness --skill spec-verify -a codex`. Or copy the skill folder (skills_en/spec-verify in jh941213/my-cc-harness) into .agents/skills/spec-verify in your project. Codex loads it when a task matches its description.

Can I use Spec Verify in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jh941213/my-cc-harness --skill spec-verify -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-verify, .gemini/skills/spec-verify, .github/skills/spec-verify and .opencode/skills/spec-verify in your project.

What does Spec Verify need to run?

SKILL.md names no scripts, command-line tools or credentials: Spec Verify is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Glob, Write, Task, AskUserQuestion.

Does Spec Verify access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Spec Verify safe to install?

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. Review the folder before installing.

What licence does Spec Verify use?

No licence was found for Spec Verify or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Spec Verify use?

About 654 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Spec Verify?

Skills that share tags, products or a category with Spec Verify: Rust TDD Workflow (rtk-ai/rtk, 83k stars), RTK Filter TDD in Rust (rtk-ai/rtk, 83k stars), Test Guard (amElnagdy/guard-skills, 1.3k stars) and Creating A Package (c15t/c15t, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Spec Verify?

jh941213 (a GitHub user) maintains it in jh941213/my-cc-harness, which has 126 GitHub stars. The repository holds 62 skills in this directory. The repository was last updated on August 3, 2026.

Source: jh941213/my-cc-harness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Spec Verify

Install Spec Verify

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Files

Compare with similar skills

Similar skills

Rust TDD Workflow

RTK Filter TDD in Rust

Test Guard

Creating A Package

Run Pre Gen Checks

Simple Modern Uv

More from jh941213/my-cc-harness

API Design Principles

Tailwind Design System

Docs Architecture

Auto Memory

Async Python Patterns

Python Testing Patterns

Questions about Spec Verify

Install Spec Verify

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Files

Compare with similar skills

Similar skills

More from jh941213/my-cc-harness

Related

Questions about Spec Verify