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.
Writes and edits developer documentation that is easy to act on and hard to misread.
Install Prp Technical Writing
$ npx skills add Wirasm/prp --skill prp-technical-writing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Wirasm/prp prp-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/Wirasm/prp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/prp-technical-writing .claude/skills/prp-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 "prp-technical-writing" agent skill from https://github.com/Wirasm/prp/tree/development/.agents/skills/prp-technical-writing into .claude/skills/prp-technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prp-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/Wirasm/prp/tree/development/.agents/skills/prp-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 Wirasm/prp --skill prp-technical-writing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Wirasm/prp prp-technical-writing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Wirasm/prp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/prp-technical-writing .agents/skills/prp-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 "prp-technical-writing" agent skill from https://github.com/Wirasm/prp/tree/development/.agents/skills/prp-technical-writing into .agents/skills/prp-technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prp-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 Wirasm/prp --skill prp-technical-writing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Wirasm/prp prp-technical-writing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Wirasm/prp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/prp-technical-writing .cursor/skills/prp-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 "prp-technical-writing" agent skill from https://github.com/Wirasm/prp/tree/development/.agents/skills/prp-technical-writing into .cursor/skills/prp-technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prp-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/Wirasm/prp.git --path .agents/skills/prp-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 Wirasm/prp --skill prp-technical-writing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Wirasm/prp prp-technical-writing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Wirasm/prp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/prp-technical-writing .gemini/skills/prp-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 "prp-technical-writing" agent skill from https://github.com/Wirasm/prp/tree/development/.agents/skills/prp-technical-writing into .gemini/skills/prp-technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prp-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 Wirasm/prp prp-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 Wirasm/prp --skill prp-technical-writing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Wirasm/prp.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/prp-technical-writing .github/skills/prp-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 "prp-technical-writing" agent skill from https://github.com/Wirasm/prp/tree/development/.agents/skills/prp-technical-writing into .github/skills/prp-technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prp-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 Wirasm/prp --skill prp-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 Wirasm/prp prp-technical-writing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Wirasm/prp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/prp-technical-writing .opencode/skills/prp-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 "prp-technical-writing" agent skill from https://github.com/Wirasm/prp/tree/development/.agents/skills/prp-technical-writing into .opencode/skills/prp-technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prp-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
prp-technical-writing- GitHub stars
- 2.3k
- Token cost
- ~830 tokens
- SKILL.md length
- 421 words
- Files
- 3 (incl. references)
- Skills in repo
- 37
- Repo updated
- First seen
- Licence
- MIT
At a glance
Writes and edits developer documentation that is easy to act on and hard to misread.
- Works in 5 steps: Establish the source of truth → Choose the document mode → Write for the first read → …
- Reviewing a README
- SKILL.md covers Scope, 1. Establish the source of truth, 2. Choose the document mode and 3. Write for the first read, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Prp Technical Writing is an agent skill from Wirasm/prp. Writes and edits developer documentation that is easy to act on and hard to misread. Use when writing or reviewing a README, RFC, tutorial, how-to guide, reference document, or technical explanation, when the operator says "write the docs", "improve this README", "edit this RFC", or invokes $prp-technical-writing.
Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/document-modes.md` and `references/sentence-style.md`).
It sits in Writing & Content, covering Technical writing and Technical documentation. The repository describes itself as: Prompts, workflows and more for agentic engineering. The licence is MIT.
When your agent uses it
- Reviewing a README
- Reference document
- Technical explanation
- The operator says write the docs
Example prompts
- “write the docs”
- “improve this README”
- “edit this RFC”
- “/prp-technical-writing”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 4352925. 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
Prp Technical Writing loads about 830 tokens when it runs, and up to ~2.6k if it reads all its reference files. Until then it costs about 84 tokens; SKILL.md has 421 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 Wirasm/prp at commit 4352925, republished under its MIT licence (© Wirasm). 421 words, ~830 tokens.
Download SKILL.mdSave it as
.claude/skills/prp-technical-writing/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- prp-technical-writing
- description
- Writes and edits developer documentation that is easy to act on and hard to misread. Use when writing or reviewing a README, RFC, tutorial, how-to guide, reference document, or technical explanation, when the operator says "write the docs", "improve this README", "edit this RFC", or invokes $prp-technical-writing.
Arguments:
$ARGUMENTS(and$1,$2, ...) refer to the arguments given when this skill was invoked. Take them from the user's request; if absent, infer them from the conversation.
Write technical documentation
Write or edit substantial developer documentation for the intended reader and task.
Input: $ARGUMENTS
Scope
Treat requests to review, critique, or answer a question as read-only. Edit files only when the operator asks for a change.
Leave product UI copy to the product's copy rules. Leave ordinary commit messages and pull request
descriptions to $prp-commit and $prp-pr unless the operator explicitly invokes this skill for an
editorial pass.
1. Establish the source of truth
Read the repository guidance, requested draft, relevant source, and existing documentation before writing. Identify the reader, the action or understanding they need, and the authoritative sources for the document's claims.
Use the repository's real symbols, paths, flags, commands, and product terms. Do not invent behavior, results, measurements, or terminology to make the prose sound complete.
2. Choose the document mode
Before drafting, read references/document-modes.md. Choose the dominant mode for the unit the
operator asked to write: the whole document, or one focused section within a mixed document. Split
and link when a competing mode becomes substantial; do not split a useful example or small reference
table merely for structural purity.
3. Write for the first read
Before writing or editing, read references/sentence-style.md. Use direct, concrete language and a
natural rhythm. Preserve precise domain terms, but remove filler, invented metaphors, vague claims,
and formulaic AI phrasing.
Organize the document around the reader's task or question. Keep background only when it changes what the reader understands or does.
Show full SKILL.md (150 more words)Show less
4. Prove the document
Check every named symbol, path, flag, link, count, command, and expected result against the real source. Run examples and commands when doing so is safe and relevant. Otherwise state what remains unverified instead of presenting it as fact.
Confirm that procedures follow the actual user path and that reference material matches the authoritative implementation or schema.
5. Edit once more
Remove words that do no work. Resolve ambiguous pronouns, modifiers, and overloaded names. Split any sentence that makes the reader backtrack.
Ask, "What makes this sound generated?" Rewrite the remaining tells without making the prose sterile or changing its meaning.
Handoff
Report the documents reviewed or changed and the evidence used to verify them. Do not commit or open a pull request unless the operator asks.
Resources
references/document-modes.md— choose and shape tutorials, how-to guides, reference, and explanationreferences/sentence-style.md— write plain, precise sentences and remove generated-sounding prose
© Wirasm, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in .agents/skills/prp-technical-writing of Wirasm/prp.
- SKILL.md
- references/document-modes.md
- references/sentence-style.md
Open the folder on GitHubat commit 4352925
Compare with similar skills
Prp 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 |
|---|---|---|---|---|---|---|
| Prp Technical Writing this skillWirasm/prp | 2.3k | — | ~830 | 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 Wirasm/prp
All 37 skills in this repoPRP Loop
Wirasm/prp
Runs the plan, implement and review pipeline detached in fresh headless sessions, looping review and fix until the pull request is clean.
PRP Loop: Autonomous Pipeline
Wirasm/prp
Runs a detached, resumable loop that plans, implements, opens a PR, reviews and fixes a feature across headless CLI sessions until the review is clean.
PRP Workstream Orchestrator
Wirasm/prp
Coordinates several PRP workstreams in isolated Git worktrees from one session, verifying proof, holding merge gates and sequencing the merges.
PRP Implementation Planner
Wirasm/prp
Turns a PRD, issue or description into an implementation-ready plan grounded in codebase evidence, adding root-cause analysis for bugs and publishing issue plans back to the issue.
PRP Plan
Wirasm/prp
Writes an implementation-ready plan for a feature, bug fix, refactor or chore from a PRD, issue or description, grounded in codebase evidence, and can post it back to the source issue.
PRP Spike
Wirasm/prp
Settles a feasibility question with the smallest throwaway build that could disprove it, in an isolated worktree, ending in a verdict backed by evidence instead of a PR.
Related
Categories
Questions about Prp Technical Writing
What does Prp Technical Writing do?
Writes and edits developer documentation that is easy to act on and hard to misread. Prp Technical Writing is an agent skill from Wirasm/prp. Writes and edits developer documentation that is easy to act on and hard to misread.
When should I use Prp Technical Writing?
Prp Technical Writing fits situations like: reviewing a README; reference document; technical explanation; the operator says write the docs.
How do I install Prp Technical Writing in Claude Code?
Run `npx skills add Wirasm/prp --skill prp-technical-writing -a claude-code`. Or copy the skill folder (.agents/skills/prp-technical-writing in Wirasm/prp) into .claude/skills/prp-technical-writing in your project. Claude Code loads it when a task matches its description.
How do I install Prp Technical Writing in Codex?
Run `npx skills add Wirasm/prp --skill prp-technical-writing -a codex`. Or copy the skill folder (.agents/skills/prp-technical-writing in Wirasm/prp) into .agents/skills/prp-technical-writing in your project. Codex loads it when a task matches its description.
Can I use Prp 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 Wirasm/prp --skill prp-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/prp-technical-writing, .gemini/skills/prp-technical-writing, .github/skills/prp-technical-writing and .opencode/skills/prp-technical-writing in your project.
What does Prp Technical Writing need to run?
SKILL.md names no scripts, command-line tools or credentials: Prp Technical Writing is instructions for the agent only.
Does Prp 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 Prp 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 Prp Technical Writing use?
Prp 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 Prp Technical Writing use?
About 830 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.8k tokens, read only when the agent opens those files.
What are the alternatives to Prp Technical Writing?
Skills that share tags, products or a category with Prp 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 Prp Technical Writing?
Wirasm (a GitHub user) maintains it in Wirasm/prp, which has 2,258 GitHub stars. The repository holds 37 skills in this directory. The repository was last updated on October 2, 2026.
Source: Wirasm/prp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.