PRP is a collection of prompts and workflows for AI-assisted software development with Claude Code. Its Product Requirement Prompts combine product requirements, selected codebase context, and an execution runbook so a coding agent can implement a vertical slice of software. The catalogue entries are the project’s own skills, agents, instructions, hook, and plugin workflows.
Borrowing it
Nothing to install: this file belongs to Wirasm/prp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Wirasm/prp/development/.agents/skills/prp-technical-writing/SKILL.mdgit clone --depth 1 https://github.com/Wirasm/prpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/wirasm/prp/prp-technical-writing)<a href="https://agentmods.dev/skills/wirasm/prp/prp-technical-writing"><img src="https://agentmods.dev/badge/skills/wirasm/prp/prp-technical-writing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/wirasm/prp/prp-technical-writing"><img src="https://agentmods.dev/badge/skills/wirasm/prp/prp-technical-writing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00075 | $0.00693 |
| Opus 5.5 | $0.00030 | $0.00277 |
| Sonnet 5.5 | $0.00015 | $0.00139 |
| Haiku 4.5 | $0.00007 | $0.00069 |
Grade A, and why
prp-technical-writing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
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.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 74 lines · 75 tokens per session scan A 27b1625bc120
prp-technical-writing is a skill published in the GitHub repository Wirasm/prp (2,264 stars, last pushed 18d ago), licensed MIT. It adds 75 tokens to every session and 693 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…