Borrowing it
Nothing to install: this file belongs to christopher-buss/bedrock. 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/christopher-buss/bedrock/main/.agents/skills/technical-writer/SKILL.mdgit clone --depth 1 https://github.com/christopher-buss/bedrockWrote 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/christopher-buss/bedrock/technical-writer)<a href="https://agentmods.dev/skills/christopher-buss/bedrock/technical-writer"><img src="https://agentmods.dev/badge/skills/christopher-buss/bedrock/technical-writer/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/christopher-buss/bedrock/technical-writer"><img src="https://agentmods.dev/badge/skills/christopher-buss/bedrock/technical-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.01381 |
| Opus 5.5 | $0.00000 | $0.00552 |
| Sonnet 5.5 | $0.00000 | $0.00276 |
| Haiku 4.5 | $0.00000 | $0.00138 |
Grade A, and why
technical-writer 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical writing craft rules
Apply these rules when producing or editing developer documentation prose. Follows the spirit of the Google Developer Documentation Style Guide without being tied to any one brand guide. Complements the Diátaxis framework: Diátaxis tells you which quadrant (tutorial, how-to, reference, explanation) a page belongs to; these rules tell you how to write each sentence once the quadrant is fixed.
When to apply
Trigger when the user is:
- Writing a new docs page (tutorial, how-to, reference entry, explanation, getting-started, README, migration guide).
- Reviewing or revising an existing docs page for quality.
- Diagnosing why a docs page feels flat, bloated, or confusing.
Skip for: commit messages, PR descriptions, ADRs, internal design docs, code comments. Those have their own registers.
Structure rules
- Open with a one-sentence summary. The first line must tell the reader what they will learn or accomplish. If removing the opening sentence leaves the page's purpose unclear, it was doing work.
- H2 sections as scannable signposts. Each heading is a promise: the reader should know what they'll get from the section without reading it. Prefer verb-led headings for task pages, noun phrases for reference.
- Order by frequency, not logic. Most common use case first, edge cases last. A reader who stops reading halfway should still have hit the 80% path.
- Inverted pyramid within each section. Lead with the most important sentence. Supporting detail follows. Caveats and edge cases end the section.
- One topic per H2. If a section covers two things, split it. Skim readers rely on the heading matching the content.
Voice and register
- Active voice, present tense. "Bedrock reads the config" beats "The config is read by bedrock." Passive is acceptable only when the agent genuinely doesn't matter.
- Second person for instructions ("you configure"), third person for concepts ("bedrock configures"). Do not mix within a section.
- Sentence case headings. Proper nouns keep their capitals.
- Concrete over abstract. Name the file, the function, the command. "Run
pnpm build" beats "build the project." - No filler openers. Cut "In order to", "It is important to note that", "Please note that", "Basically".
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 · 90 lines · 0 tokens per session scan A 5c4ed5126775
technical-writer is a skill published in the GitHub repository christopher-buss/bedrock (19 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,381 tokens. 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-09-01.
Other skills, from other repositories
x-demand-radar
A radar for spotting fast-rising topics, tools, and projects on X, the social network formerly known as Twitter.
null-axiom-twitter
A writing tool that creates Twitter/X posts and threads in the Null Axiom persona, with a style aimed at indie developers and data-focused investigators. It can also draft replies to Twitter/X posts and send drafts to Feishu for review on a schedule.
roblox-site-architect
Orchestrate an evidence-backed seven-stage Roblox site growth pipeline from opportunity assessment through keyword research, source collection, site planning, SEO QA, freshness, and growth. Use when work needs staged artifacts and explicit handoffs rather than a one-click site generator.
site-keyword-research
A website keyword-research workflow that studies what people search for, expands related terms, and analyses competition in search results.
roblox-homepage-ranking-auditor
Audit a Roblox or game-site homepage against the RB Auto Golden Homepage model. Use when Codex must inspect a live homepage or repository, identify the primary player job and main engine, score structural ranking potential across eight dimensions, detect empty query modules, weak information gain, root/child intent…
roblox-hit-evaluator
Evaluate a Roblox game's 30-day breakout potential from public evidence with auditable scores, missing-data bounds, frozen forecasts, and outcome reviews.