API Design Principles
jh941213/my-cc-harness
REST 및 GraphQL API 설계 원칙 가이드. An agent skill from jh941213/my-cc-harness.
SPEC.md 명세서 대비 구현 완료도를 검증합니다. An agent skill from jh941213/my-cc-harness.
No licenceAuto-check passed
Install Spec Verify
$ npx skills add jh941213/my-cc-harness --skill spec-verify -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jh941213/my-cc-harness spec-verify --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/jh941213/my-cc-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/spec-verify .claude/skills/spec-verify && 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-verify" agent skill from https://github.com/jh941213/my-cc-harness/tree/main/skills/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 install https://github.com/jh941213/my-cc-harness/tree/main/skills/spec-verifyType 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 jh941213/my-cc-harness --skill spec-verify -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jh941213/my-cc-harness spec-verify --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jh941213/my-cc-harness.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/spec-verify .agents/skills/spec-verify && 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-verify" agent skill from https://github.com/jh941213/my-cc-harness/tree/main/skills/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.
$ npx skills add jh941213/my-cc-harness --skill spec-verify -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jh941213/my-cc-harness spec-verify --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jh941213/my-cc-harness.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/spec-verify .cursor/skills/spec-verify && 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-verify" agent skill from https://github.com/jh941213/my-cc-harness/tree/main/skills/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 https://github.com/jh941213/my-cc-harness.git --path skills/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.
$ npx skills add jh941213/my-cc-harness --skill spec-verify -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jh941213/my-cc-harness spec-verify --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jh941213/my-cc-harness.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/spec-verify .gemini/skills/spec-verify && 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-verify" agent skill from https://github.com/jh941213/my-cc-harness/tree/main/skills/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.
$ gh skill install jh941213/my-cc-harness spec-verifyInstalls 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 jh941213/my-cc-harness --skill spec-verify -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jh941213/my-cc-harness.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/spec-verify .github/skills/spec-verify && 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-verify" agent skill from https://github.com/jh941213/my-cc-harness/tree/main/skills/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.
$ npx skills add jh941213/my-cc-harness --skill spec-verify -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jh941213/my-cc-harness spec-verify --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jh941213/my-cc-harness.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/spec-verify .opencode/skills/spec-verify && 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-verify" agent skill from https://github.com/jh941213/my-cc-harness/tree/main/skills/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
- ~384 tokens
- SKILL.md length
- 101 words
- Files
- 1
- Skills in repo
- 62
- Repo updated
- First seen
- Licence
- None found
At a glance
SPEC.md 명세서 대비 구현 완료도를 검증합니다. An agent skill from jh941213/my-cc-harness.
- Works in 3 steps: SPEC-REVIEW.md 내용을 사용자에게 보여줌 → 수정 여부 확인 (AskUserQuestion 사용) → 승인 시 누락 사항 구현
- SKILL.md covers 트리거, 워크플로우, 검증 체크리스트 and 핵심 원칙
- 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. SPEC.md 명세서 대비 구현 완료도를 검증합니다. Triggers on: 스펙 검증, spec-verify, 명세서 검증, 구현 검증. NOT for: 코드 리뷰, 단위 테스트, 빌드 검증.
Its SKILL.md is about 380 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
Example prompts
- “/spec-verify”
Requirements
- Pre-approved tools (allowed-tools): Read, Grep, Glob, Write, Task, AskUserQuestion
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- SPEC-REVIEW.md 내용을 사용자에게 보여줌
- 수정 여부 확인 (AskUserQuestion 사용)
- 승인 시 누락 사항 구현
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:
ReadGrepGlobWriteTaskAskUserQuestion
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 384 tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 101 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.
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 101 words (~384 tokens).
“명세서 기반 작업 완료 후 검증하는 스킬입니다.”
- name
- spec-verify
- allowed-tools
- Read, Grep, Glob, Write, Task, AskUserQuestion
- user-invocable
- true
- disable-model-invocation
- true
- context
- fork
Files
Just SKILL.md in skills/spec-verify of jh941213/my-cc-harness.
Open the folder on GitHubat commit e9210e2
More from jh941213/my-cc-harness
All 62 skills in this repoTailwind Design System
jh941213/my-cc-harness
Build scalable design systems with Tailwind CSS, design tokens, component libraries, and responsive patterns.
Docs Architecture
jh941213/my-cc-harness
Generate/update architecture docs — ARCHITECTURE.md (codemap), architecture diagrams (C4 mermaid), ADRs (MADR), data model ERD.
Auto Memory
jh941213/my-cc-harness
A skill your agent uses when starting substantial work in a repo (implementation, fixes, deploys, debugging), when first exploring a new repo, or when finishing work that produced reusable knowledge.
Async Python Patterns
jh941213/my-cc-harness
Python asyncio 및 async/await 패턴 가이드. An agent skill from jh941213/my-cc-harness.
Python Testing Patterns
jh941213/my-cc-harness
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development.
Questions about Spec Verify
What does Spec Verify do?
SPEC.md 명세서 대비 구현 완료도를 검증합니다. An agent skill from jh941213/my-cc-harness. Spec Verify is an agent skill from jh941213/my-cc-harness.md 명세서 대비 구현 완료도를 검증합니다.
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/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/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 384 tokens (SKILL.md is roughly 1.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
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.