Documentation Strategy
rampstackco/claude-skills
Design and run a documentation system for a team or product.
A skill your agent uses when writing documentation, READMEs, technical specs, runbooks, or any text that explains a system or process to other engineers.
Install Technical Writing Clarity
$ npx skills add aiming-lab/MetaClaw --skill technical-writing-clarity -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aiming-lab/MetaClaw technical-writing-clarity --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/aiming-lab/MetaClaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/memory_data/skills/technical-writing-clarity .claude/skills/technical-writing-clarity && 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 "technical-writing-clarity" agent skill from https://github.com/aiming-lab/MetaClaw/tree/main/memory_data/skills/technical-writing-clarity into .claude/skills/technical-writing-clarity/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writing-clarity", 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/aiming-lab/MetaClaw/tree/main/memory_data/skills/technical-writing-clarityType 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 aiming-lab/MetaClaw --skill technical-writing-clarity -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aiming-lab/MetaClaw technical-writing-clarity --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aiming-lab/MetaClaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/memory_data/skills/technical-writing-clarity .agents/skills/technical-writing-clarity && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "technical-writing-clarity" agent skill from https://github.com/aiming-lab/MetaClaw/tree/main/memory_data/skills/technical-writing-clarity into .agents/skills/technical-writing-clarity/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writing-clarity", 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 aiming-lab/MetaClaw --skill technical-writing-clarity -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aiming-lab/MetaClaw technical-writing-clarity --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aiming-lab/MetaClaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/memory_data/skills/technical-writing-clarity .cursor/skills/technical-writing-clarity && 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 "technical-writing-clarity" agent skill from https://github.com/aiming-lab/MetaClaw/tree/main/memory_data/skills/technical-writing-clarity into .cursor/skills/technical-writing-clarity/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writing-clarity", 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/aiming-lab/MetaClaw.git --path memory_data/skills/technical-writing-clarity--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 aiming-lab/MetaClaw --skill technical-writing-clarity -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aiming-lab/MetaClaw technical-writing-clarity --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aiming-lab/MetaClaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/memory_data/skills/technical-writing-clarity .gemini/skills/technical-writing-clarity && 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 "technical-writing-clarity" agent skill from https://github.com/aiming-lab/MetaClaw/tree/main/memory_data/skills/technical-writing-clarity into .gemini/skills/technical-writing-clarity/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writing-clarity", 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 aiming-lab/MetaClaw technical-writing-clarityInstalls 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 aiming-lab/MetaClaw --skill technical-writing-clarity -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aiming-lab/MetaClaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/memory_data/skills/technical-writing-clarity .github/skills/technical-writing-clarity && 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 "technical-writing-clarity" agent skill from https://github.com/aiming-lab/MetaClaw/tree/main/memory_data/skills/technical-writing-clarity into .github/skills/technical-writing-clarity/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writing-clarity", 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 aiming-lab/MetaClaw --skill technical-writing-clarity -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aiming-lab/MetaClaw technical-writing-clarity --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aiming-lab/MetaClaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/memory_data/skills/technical-writing-clarity .opencode/skills/technical-writing-clarity && 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 "technical-writing-clarity" agent skill from https://github.com/aiming-lab/MetaClaw/tree/main/memory_data/skills/technical-writing-clarity into .opencode/skills/technical-writing-clarity/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writing-clarity", 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
technical-writing-clarity- GitHub stars
- 3.5k
- Token cost
- ~244 tokens
- SKILL.md length
- 94 words
- Files
- 1
- Skills in repo
- 36
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when writing documentation, READMEs, technical specs, runbooks, or any text that explains a system or process to other engineers.
- Works in 5 steps: Overview (1–2 sentences) → Prerequisites → Steps (numbered, imperative) → …
- Writing documentation
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Technical specs
What it does
Technical Writing Clarity is an agent skill from aiming-lab/MetaClaw. Use this skill when writing documentation, READMEs, technical specs, runbooks, or any text that explains a system or process to other engineers. Apply before writing any developer-facing document.
Its SKILL.md is about 240 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 Writing & Content, covering Technical writing, Runbooks and postmortems and Technical documentation. The repository describes itself as: 🦞 Just talk to your agent — it learns and EVOLVES 🧬. The licence is MIT.
When your agent uses it
- Writing documentation
- Technical specs
- Any text that explains a system
- Process to other engineers
Example prompts
- “/technical-writing-clarity”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Overview (1–2 sentences)
- Prerequisites
- Steps (numbered, imperative)
- Verification / expected output
- Troubleshooting
What it can do on your machine
Read from SKILL.md and the folder at commit 922caf3. 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
Technical Writing Clarity loads about 244 tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 94 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
The full file from aiming-lab/MetaClaw at commit 922caf3, republished under its MIT licence (© aiming-lab). 94 words, ~244 tokens.
Download SKILL.mdSave it as
.claude/skills/technical-writing-clarity/SKILL.md (or your agent's skills folder).- name
- technical-writing-clarity
- description
- Use this skill when writing documentation, READMEs, technical specs, runbooks, or any text that explains a system or process to other engineers. Apply before writing any developer-facing document.
- category
- communication
Technical Writing for Clarity
Principles:
- Lead with the purpose: What is this document for and who is it for?
- One idea per paragraph. Long paragraphs hide key information.
- Use active voice:
Run the scriptnotThe script should be run. - Concrete over abstract: Show an example rather than describing it abstractly.
- Avoid jargon you have not defined unless the audience definitely knows it.
Structure for runbooks/how-tos:
- Overview (1–2 sentences)
- Prerequisites
- Steps (numbered, imperative)
- Verification / expected output
- Troubleshooting
Anti-patterns: Documenting what without why, outdated examples, walls of text without headers.
© aiming-lab, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in memory_data/skills/technical-writing-clarity of aiming-lab/MetaClaw.
Open the folder on GitHubat commit 922caf3
Compare with similar skills
Technical Writing Clarity 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 |
|---|---|---|---|---|---|---|
| Technical Writing Clarity this skillaiming-lab/MetaClaw | 3.5k | — | ~244 | Automated safety check: Pass | MIT | |
| Documentation Strategyrampstackco/claude-skills | 945 | — | ~3.3k | Automated safety check: Pass | MIT | |
| Persuasive Technical Writingmtarcure/claude-vibe-squad | 165 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Technical Writercuriositech/some_claude_skills | 244 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Technical Writingrsmdt/the-startup | 560 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Beads Documentation Style Guidegastownhall/beads | 28k | — | ~3.2k | Automated safety check: Pass | MIT |
Similar skills
Persuasive Technical Writing
mtarcure/claude-vibe-squad
A skill your agent uses when drafting or revising long-form persuasive technical prose (an essay, post-mortem, launch narrative, or public technical release for X or the web) where the writing must…
Technical Writer
curiositech/some_claude_skills
Expert technical documentation specialist for developer docs, API references, and runbooks.
Technical Writing
rsmdt/the-startup
Create architectural decision records (ADRs), system documentation, API documentation, and operational runbooks.
Beads Documentation Style Guide
gastownhall/beads
Sets the house style for the beads user docs: the canonical concept model, required terminology, prose and diagram conventions, and checks before docs work is done.
JavaScript Concept Page Workflow
leonardomso/33-js-concepts
Orchestrates five skills to produce a complete JavaScript concept documentation page, from resource curation through writing, tests, fact-checking and SEO.
More from aiming-lab/MetaClaw
All 36 skills in this repoData Validation First
aiming-lab/MetaClaw
Use this skill before any data analysis, transformation, or modeling.
Input Validation And Sanitization
aiming-lab/MetaClaw
A skill your agent uses when implementing any endpoint, form handler, CLI tool, or function that accepts external input.
Robust Error Handling In Scripts
aiming-lab/MetaClaw
A skill your agent uses when writing shell scripts, Python automation, or any unattended batch job.
Structured Logging And Observability
aiming-lab/MetaClaw
A skill your agent uses when building production services, pipelines, or automation that needs to be debugged, monitored, or audited.
Agent Task Handoff
aiming-lab/MetaClaw
A skill your agent uses when delegating a subtask to a sub-agent, spawning a parallel worker, or handing off work across sessions.
Async Communication Etiquette
aiming-lab/MetaClaw
A skill your agent uses when writing messages in async channels (Slack, GitHub issues, email threads) where the reader may not have context and cannot ask follow-up questions immediately.
Related
Categories
Questions about Technical Writing Clarity
What does Technical Writing Clarity do?
A skill your agent uses when writing documentation, READMEs, technical specs, runbooks, or any text that explains a system or process to other engineers. Technical Writing Clarity is an agent skill from aiming-lab/MetaClaw. Use this skill when writing documentation, READMEs, technical specs, runbooks, or any text that explains a system or process to other engineers.
When should I use Technical Writing Clarity?
Technical Writing Clarity fits situations like: writing documentation; technical specs; any text that explains a system; process to other engineers.
How do I install Technical Writing Clarity in Claude Code?
Run `npx skills add aiming-lab/MetaClaw --skill technical-writing-clarity -a claude-code`. Or copy the skill folder (memory_data/skills/technical-writing-clarity in aiming-lab/MetaClaw) into .claude/skills/technical-writing-clarity in your project. Claude Code loads it when a task matches its description.
How do I install Technical Writing Clarity in Codex?
Run `npx skills add aiming-lab/MetaClaw --skill technical-writing-clarity -a codex`. Or copy the skill folder (memory_data/skills/technical-writing-clarity in aiming-lab/MetaClaw) into .agents/skills/technical-writing-clarity in your project. Codex loads it when a task matches its description.
Can I use Technical Writing Clarity 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 aiming-lab/MetaClaw --skill technical-writing-clarity -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/technical-writing-clarity, .gemini/skills/technical-writing-clarity, .github/skills/technical-writing-clarity and .opencode/skills/technical-writing-clarity in your project.
What does Technical Writing Clarity need to run?
SKILL.md names no scripts, command-line tools or credentials: Technical Writing Clarity is instructions for the agent only.
Does Technical Writing Clarity 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 Technical Writing Clarity 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 Technical Writing Clarity use?
Technical Writing Clarity is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Technical Writing Clarity use?
About 244 tokens (SKILL.md is roughly 976 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 Technical Writing Clarity?
Skills that share tags, products or a category with Technical Writing Clarity: Documentation Strategy (rampstackco/claude-skills, 945 stars), Persuasive Technical Writing (mtarcure/claude-vibe-squad, 165 stars), Technical Writer (curiositech/some_claude_skills, 244 stars) and Technical Writing (rsmdt/the-startup, 560 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Technical Writing Clarity?
aiming-lab (a GitHub organization) maintains it in aiming-lab/MetaClaw, which has 3,459 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on June 7, 2026.
Source: aiming-lab/MetaClaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.