PR Design Doc
OpenHands/OpenHands
For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…
A skill your agent uses when asked for client-submission SI/AO deliverables (architecture design doc, interface spec, DB design doc, requirements traceability matrix, test result reports, manuals…
Install Client Docs
$ npx skills add jh941213/my-cc-harness --skill client-docs -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jh941213/my-cc-harness client-docs --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_en/client-docs .claude/skills/client-docs && 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 "client-docs" agent skill from https://github.com/jh941213/my-cc-harness/tree/main/skills_en/client-docs into .claude/skills/client-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-docs", 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_en/client-docsType 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 client-docs -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jh941213/my-cc-harness client-docs --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_en/client-docs .agents/skills/client-docs && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "client-docs" agent skill from https://github.com/jh941213/my-cc-harness/tree/main/skills_en/client-docs into .agents/skills/client-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-docs", 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 client-docs -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jh941213/my-cc-harness client-docs --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_en/client-docs .cursor/skills/client-docs && 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 "client-docs" agent skill from https://github.com/jh941213/my-cc-harness/tree/main/skills_en/client-docs into .cursor/skills/client-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-docs", 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_en/client-docs--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 client-docs -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jh941213/my-cc-harness client-docs --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_en/client-docs .gemini/skills/client-docs && 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 "client-docs" agent skill from https://github.com/jh941213/my-cc-harness/tree/main/skills_en/client-docs into .gemini/skills/client-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-docs", 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 client-docsInstalls 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 client-docs -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_en/client-docs .github/skills/client-docs && 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 "client-docs" agent skill from https://github.com/jh941213/my-cc-harness/tree/main/skills_en/client-docs into .github/skills/client-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-docs", 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 client-docs -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 client-docs --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_en/client-docs .opencode/skills/client-docs && 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 "client-docs" agent skill from https://github.com/jh941213/my-cc-harness/tree/main/skills_en/client-docs into .opencode/skills/client-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-docs", 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
client-docs- GitHub stars
- 126
- Token cost
- ~883 tokens
- SKILL.md length
- 366 words
- Files
- 1
- Skills in repo
- 62
- Repo updated
- First seen
- Licence
- None found
At a glance
A skill your agent uses when asked for client-submission SI/AO deliverables (architecture design doc, interface spec, DB design doc, requirements traceability matrix, test result reports, manuals…
- Works in 8 steps: Output location:… → Common skeleton: cover (project… → Client template wins: if… → …
- Asked for client-submission SI/AO deliverables (architecture design doc
- SKILL.md covers Deliverable routing, Generation rules, Entry points and Forbidden
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Client Docs is an agent skill from jh941213/my-cc-harness. Use when asked for client-submission SI/AO deliverables (architecture design doc, interface spec, DB design doc, requirements traceability matrix, test result reports, manuals, operations reports). Triggered by acceptance/delivery/deliverable requests. On-demand only — produce exactly the deliverable requested
Its SKILL.md is about 880 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 Development, covering Architecture decision records.
When your agent uses it
- Asked for client-submission SI/AO deliverables (architecture design doc
- Requirements traceability matrix
- Test result reports
- Operations reports)
Example prompts
- “/client-docs”
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Output location: {project}/deliverables/[name]_[YYYY-MM-DD].md
- Common skeleton: cover (project name·date·version) → revision history → TOC → body → appendix. Body structure follows each deliverable's…
- Client template wins: if ~/.claude/templates/client/ or {project}/templates/ has the client's template, follow its structure and field…
- Facts only: only content verified from code/docs/run output. Leave unverified items empty marked [NEEDS CONFIRMATION] — never fill plausibly
- If sources are stale, run /docs sync first, then generate
- After generating, add a deliverables/ routing row to memory/INDEX.md if absent (keywords: deliverable, acceptance, delivery)
- Acceptance-grade requirements (rejection-prevention rules from independent evaluation)
- After generating, verify facts (number reproduction) with a separate agent when possible — the generator must not grade its own deliverable
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 nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
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
Client Docs loads about 883 tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 366 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 366 words (~883 tokens).
“Principle: deliverables are infrequent. Generate only the requested one, by transforming materials that already exist (docs/, code, actual run output).”
- name
- client-docs
Files
Just SKILL.md in skills_en/client-docs of jh941213/my-cc-harness.
Open the folder on GitHubat commit e9210e2
Compare with similar skills
Client Docs 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Client Docs this skilljh941213/my-cc-harness | 126 | — | ~883 | Automated safety check: Pass | None | |
| PR Design DocOpenHands/OpenHands | 90k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Cto AdvisorIbrahim-3d/orchestrator-supaconductor | 380 | 4 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Improve Codebase Architectureywwynm/EverythingDone | 144 | 15 repos | ~1.3k | Automated safety check: Pass | GPL-3.0 | |
| Domain Modelingbrim-borium/spotify_sdk | 166 | 5 repos | ~806 | Automated safety check: Pass | Apache-2.0 | |
| Design Doc MermaidSpillwaveSolutions/design-doc-mermaid | 175 | 1 repos | ~5.6k | Automated safety check: Pass | None |
Similar skills
Cto Advisor
Ibrahim-3d/orchestrator-supaconductor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.
Improve Codebase Architecture
ywwynm/EverythingDone
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/.
Domain Modeling
brim-borium/spotify_sdk
Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.
Design Doc Mermaid
SpillwaveSolutions/design-doc-mermaid
Create Mermaid diagrams (flowchart, sequence, class, ER, state, C4, architecture) from text or source code.
Learning Opportunities
DrCatHicks/learning-opportunities
Facilitates deliberate skill development during AI-assisted coding.
More from jh941213/my-cc-harness
All 62 skills in this repoAPI Design Principles
jh941213/my-cc-harness
REST 및 GraphQL API 설계 원칙 가이드. An agent skill from jh941213/my-cc-harness.
Tailwind 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.
Related
Categories
Questions about Client Docs
What does Client Docs do?
A skill your agent uses when asked for client-submission SI/AO deliverables (architecture design doc, interface spec, DB design doc, requirements traceability matrix, test result reports, manuals…. Client Docs is an agent skill from jh941213/my-cc-harness. Use when asked for client-submission SI/AO deliverables (architecture design doc, interface spec, DB design doc, requirements traceability matrix, test result reports, manuals, operations reports).
When should I use Client Docs?
Client Docs fits situations like: asked for client-submission SI/AO deliverables (architecture design doc; requirements traceability matrix; test result reports; operations reports).
How do I install Client Docs in Claude Code?
Run `npx skills add jh941213/my-cc-harness --skill client-docs -a claude-code`. Or copy the skill folder (skills_en/client-docs in jh941213/my-cc-harness) into .claude/skills/client-docs in your project. Claude Code loads it when a task matches its description.
How do I install Client Docs in Codex?
Run `npx skills add jh941213/my-cc-harness --skill client-docs -a codex`. Or copy the skill folder (skills_en/client-docs in jh941213/my-cc-harness) into .agents/skills/client-docs in your project. Codex loads it when a task matches its description.
Can I use Client Docs 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 client-docs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/client-docs, .gemini/skills/client-docs, .github/skills/client-docs and .opencode/skills/client-docs in your project.
What does Client Docs need to run?
SKILL.md names no scripts, command-line tools or credentials: Client Docs is instructions for the agent only.
Does Client Docs 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 Client Docs 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 Client Docs use?
No licence was found for Client Docs or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Client Docs use?
About 883 tokens (SKILL.md is roughly 3.5k 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 Client Docs?
Skills that share tags, products or a category with Client Docs: PR Design Doc (OpenHands/OpenHands, 90k stars), Cto Advisor (Ibrahim-3d/orchestrator-supaconductor, 380 stars), Improve Codebase Architecture (ywwynm/EverythingDone, 144 stars) and Domain Modeling (brim-borium/spotify_sdk, 166 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Client Docs?
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.