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.
Guide for writing effective technical documentation, specs, and markdown files.
Install Technical Writing
$ npx skills add cashew-labs/libretto --skill technical-writing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cashew-labs/libretto technical-writing --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/cashew-labs/libretto.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/technical-writing .claude/skills/technical-writing && 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" agent skill from https://github.com/cashew-labs/libretto/tree/main/.agents/skills/technical-writing into .claude/skills/technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writing", 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/cashew-labs/libretto/tree/main/.agents/skills/technical-writingType 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 cashew-labs/libretto --skill technical-writing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cashew-labs/libretto technical-writing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cashew-labs/libretto.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/technical-writing .agents/skills/technical-writing && 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" agent skill from https://github.com/cashew-labs/libretto/tree/main/.agents/skills/technical-writing into .agents/skills/technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writing", 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 cashew-labs/libretto --skill technical-writing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cashew-labs/libretto technical-writing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cashew-labs/libretto.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/technical-writing .cursor/skills/technical-writing && 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" agent skill from https://github.com/cashew-labs/libretto/tree/main/.agents/skills/technical-writing into .cursor/skills/technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writing", 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/cashew-labs/libretto.git --path .agents/skills/technical-writing--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 cashew-labs/libretto --skill technical-writing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cashew-labs/libretto technical-writing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cashew-labs/libretto.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/technical-writing .gemini/skills/technical-writing && 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" agent skill from https://github.com/cashew-labs/libretto/tree/main/.agents/skills/technical-writing into .gemini/skills/technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writing", 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 cashew-labs/libretto technical-writingInstalls 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 cashew-labs/libretto --skill technical-writing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cashew-labs/libretto.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/technical-writing .github/skills/technical-writing && 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" agent skill from https://github.com/cashew-labs/libretto/tree/main/.agents/skills/technical-writing into .github/skills/technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writing", 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 cashew-labs/libretto --skill technical-writing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cashew-labs/libretto technical-writing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cashew-labs/libretto.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/technical-writing .opencode/skills/technical-writing && 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" agent skill from https://github.com/cashew-labs/libretto/tree/main/.agents/skills/technical-writing into .opencode/skills/technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writing", 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- GitHub stars
- 904
- Token cost
- ~245 tokens
- SKILL.md length
- 103 words
- Files
- 1
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- MIT
At a glance
Guide for writing effective technical documentation, specs, and markdown files.
- AGENTS.md files
- SKILL.md covers Audience, Style, Formatting and Paths, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Any markdown content in the codebase
What it does
Technical Writing is an agent skill from cashew-labs/libretto. Guide for writing effective technical documentation, specs, and markdown files. Use when creating or editing specs, documentation, READMEs, AGENTS.md files, or any markdown content in the codebase.
Its SKILL.md is about 250 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 documentation and Technical writing. The repository describes itself as: The AI toolkit for building reliable browser automations. The licence is MIT.
When your agent uses it
- AGENTS.md files
- Any markdown content in the codebase
Example prompts
- “/technical-writing”
What it can do on your machine
Read from SKILL.md and the folder at commit 41ab782. 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 loads about 245 tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 103 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 cashew-labs/libretto at commit 41ab782, republished under its MIT licence (© cashew-labs). 103 words, ~245 tokens.
Download SKILL.mdSave it as
.claude/skills/technical-writing/SKILL.md (or your agent's skills folder).- name
- technical-writing
- description
- Guide for writing effective technical documentation, specs, and markdown files. Use when creating or editing specs, documentation, READMEs, AGENTS.md files, or any markdown content in the codebase.
Technical Writing
Audience
Assume readers are at least as smart as you, so do not over-explain. State information once and move on.
Style
Write concise, complete sentences using active voice and present tense. Each paragraph or bullet should express a single idea.
Formatting
- Do not use emojis.
- Do not use bold or italics.
- Use headings, lists, and code blocks only when they add clarity.
- Use fenced code blocks with language identifiers.
Paths
Always use relative file paths: docs/testing.md, not /Users/name/project/docs/testing.md.
Do Not Repeat
Link to existing resources instead of duplicating content. Reference other docs, web pages, or files rather than restating their information.
© cashew-labs, 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 .agents/skills/technical-writing of cashew-labs/libretto.
Open the folder on GitHubat commit 41ab782
Compare with similar skills
Technical Writing 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 this skillcashew-labs/libretto | 904 | — | ~245 | Automated safety check: Pass | MIT | |
| Beads Documentation Style Guidegastownhall/beads | 28k | — | ~3.2k | Automated safety check: Pass | MIT | |
| JavaScript Concept Page Workflowleonardomso/33-js-concepts | 67k | — | ~3.9k | Automated safety check: Pass | MIT | |
| Technical Writing Standardcursor/plugins | 10k | 10 repos | ~2.4k | Automated safety check: Pass | None | |
| Heym Documentation Articlesheymrun/heym | 1.4k | — | ~780 | Automated safety check: Pass | Custom licence | |
| JavaScript Concept Page Writerleonardomso/33-js-concepts | 67k | — | ~14k | Automated safety check: Pass | MIT |
Similar skills
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.
- Official
Technical Writing Standard
cursor/plugins
Applies four layers of technical-writing rules to docs, RFCs, readmes, PR descriptions and commit messages so a tired engineer follows them on the first read.
Heym Documentation Articles
heymrun/heym
Creates and updates documentation articles for the Heym platform: category choice, manifest entry, markdown file and cross-links from existing pages.
JavaScript Concept Page Writer
leonardomso/33-js-concepts
Writes or reviews documentation pages for the 33 JavaScript Concepts project, following its structure, a beginner-friendly voice and rules against AI-sounding language.
Technical Writing Workflow
tokenbender/agent-guides
A skill your agent uses for planning, researching, drafting, revising, or auditing technical write-ups, textbooks, papers, reports, READMEs, research notes, PR narratives, and public technical prose.
More from cashew-labs/libretto
All 21 skills in this repoSystem Prompt Writing Guide
cashew-labs/libretto
Lays out a minimal, iteration-first approach to writing system prompts for LLM agents, with model-specific notes for Claude, GPT, Gemini, and Codex.
Address PR Review Comments
cashew-labs/libretto
Works through the review comments on a pull request one by one: fetches the threads, makes the fixes, runs type-check, build and lint, pushes, and resolves the threads.
CLI Development
cashew-labs/libretto
Design rules for command-line tools: subcommand-scoped help, actionable success output, debuggable failures, stable output, meaningful exit codes and a --json mode.
External Electron App Automation
cashew-labs/libretto
Drives desktop Electron apps already installed on your machine, such as Slack, Discord or VS Code, by relaunching them with a debugging port and using the Libretto CLI.
Merge Conflict Resolver
cashew-labs/libretto
Resolves Git merge, rebase and cherry-pick conflicts by reading the PRs behind each side, keeping both intents and asking you when they truly clash.
Feature Spec Generator
cashew-labs/libretto
Researches the codebase and relevant docs, asks clarifying questions, then writes a spec sheet in specs/ for a significant feature or complex fix.
Related
Categories
Questions about Technical Writing
What does Technical Writing do?
Guide for writing effective technical documentation, specs, and markdown files. Technical Writing is an agent skill from cashew-labs/libretto. Guide for writing effective technical documentation, specs, and markdown files.
When should I use Technical Writing?
Technical Writing fits situations like: AGENTS.md files; any markdown content in the codebase.
How do I install Technical Writing in Claude Code?
Run `npx skills add cashew-labs/libretto --skill technical-writing -a claude-code`. Or copy the skill folder (.agents/skills/technical-writing in cashew-labs/libretto) into .claude/skills/technical-writing in your project. Claude Code loads it when a task matches its description.
How do I install Technical Writing in Codex?
Run `npx skills add cashew-labs/libretto --skill technical-writing -a codex`. Or copy the skill folder (.agents/skills/technical-writing in cashew-labs/libretto) into .agents/skills/technical-writing in your project. Codex loads it when a task matches its description.
Can I use Technical Writing 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 cashew-labs/libretto --skill technical-writing -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, .gemini/skills/technical-writing, .github/skills/technical-writing and .opencode/skills/technical-writing in your project.
What does Technical Writing need to run?
SKILL.md names no scripts, command-line tools or credentials: Technical Writing is instructions for the agent only.
Does Technical Writing 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 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 use?
Technical Writing 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 use?
About 245 tokens (SKILL.md is roughly 980 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?
Skills that share tags, products or a category with Technical Writing: Beads Documentation Style Guide (gastownhall/beads, 28k stars), JavaScript Concept Page Workflow (leonardomso/33-js-concepts, 67k stars), Technical Writing Standard (cursor/plugins, 10k stars) and Heym Documentation Articles (heymrun/heym, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Technical Writing?
cashew-labs (a GitHub organization) maintains it in cashew-labs/libretto, which has 904 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on August 21, 2026.
Source: cashew-labs/libretto on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.