Technical Writing
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
Install
npx skills add adriannoes/awesome-agentic-ai --skill technical-writinggit clone --depth 1 https://github.com/adriannoes/awesome-agentic-ai.git /tmp/awesome-agentic-ai
mkdir -p ~/.claude/skills
cp -r /tmp/awesome-agentic-ai/cursor-claude-codex/skills/pstack/technical-writing ~/.claude/skills/technical-writingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Technical writing The goal is writing a tired engineer understands on the first read. Four layers get you there, one question each: what kind of document is this, how do sentences address the reader, how much does each sentence carry, and can any sentence be read two ways. Apply all four. Three rules sit above the layers: - **Cut every word that does no work.** If the sentence survives without a word, the word goes. "In order to" is "to". "It is important to note that" is nothing. - **Use the short, everyday word.** "Use", not "utilize". "Help", not "facilitate". "Do", not "perform". A long word has to buy its length with precision. - **When a rule makes a sentence worse, fix the sentence another way or leave it alone.** The rules serve the reader. A sentence that follows every rule and sounds like a machine wrote it has failed. The codebase is the word list. Write the real symbol, file, flag, or command name, not a synonym or a description of it. Don't invent jargon. Use the words a developer would say out loud: "move", "delete", "a budget that only decreases", not "evacuate", "ratchet", or "endgame". A named pattern is fine when the doc says what it means the first time. Propose a new offender and its replacement as an addition to `unslop`'s abstract-metaphor rule in your reply, with the diff. Don't edit that skill. ## Vary the rhythm
Details
- Skill name
technical-writing- Repository
- adriannoes/awesome-agentic-ai
- Path
cursor-claude-codex/skills/pstack/technical-writing/SKILL.md- License
- MIT
- Repo updated
- 2 November 2026
FAQ
What does the Technical Writing skill do?
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
How do I install the Technical Writing skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add adriannoes/awesome-agentic-ai --skill technical-writing. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Technical Writing popular?
It lives in adriannoes/awesome-agentic-ai, which has 100 GitHub stars and 27 forks, and is included in 2 curated skill lists.
Related skills
Browserstack
100adriannoes/awesome-agentic-ai
Run tests on BrowserStack. Use when user mentions "browserstack", "cross-browser", "cloud testing", "browser matrix", "test on safari", "test on firefox", or "browser compatibility".
Coverage
100adriannoes/awesome-agentic-ai
Analyze test coverage gaps. Use when user says "test coverage", "what's not tested", "coverage gaps", "missing tests", "coverage report", or "what needs testing".
Fix
100adriannoes/awesome-agentic-ai
Fix failing or flaky Playwright tests. Use when user says "fix test", "flaky test", "test failing", "debug test", "test broken", "test passes sometimes", or "intermittent failure".
Triage Validation
100adriannoes/awesome-agentic-ai
Finding validation before writing any report — 7-Question Gate (all 7 questions), 4 pre-submission gates, always-rejected list, conditionally valid with chain table, CVSS 3.1 quick reference, severity decision guide, report title formula, 60-second pre-submit checklist. Use BEFORE writing any report. One wrong answer = kill the finding and move on. Saves N/A ratio.
Short
100adriannoes/awesome-agentic-ai
Manually-invoked skill that forces the agent to compress its current answer — strip filler, simplify wording, and cut length while keeping the substance. Use when David says "short", "shorter", "simpler", "too long", "tl;dr", or wants a more concise version of the previous response.
Wiki
46natsu1211/deepwiki-skill
Generating comprehensive wiki-style documentation for any codebase. This skill can be used when 1. Generating documentation for a new project, 2. Update existing documentation after code changes, 3. Create or refine a wiki TOC for a codebase, 4. Obtain a comprehensive overview of an unfamiliar project.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.