Technical Writing
Layered technical-writing standard: Di\u00e1taxis 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. Observe required inputs first; HOLD when they are missing rather than guessing.
Install
npx skills add jeremybrasher/grokbot-skills --skill technical-writinggit clone --depth 1 https://github.com/jeremybrasher/grokbot-skills.git /tmp/grokbot-skills
mkdir -p ~/.claude/skills
cp -r /tmp/grokbot-skills/collections/pstack/skills/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 ## When to use 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. **Do not use when:** - The description trigger is not met - Required inputs are unavailable and cannot be obtained - A narrower skill better fits ## Intake — before you proceed You need all of the following. If any is missing, stop. 1. A named object of work matching this skill 2. Inputs the domain recipe needs to start 3. Authority for any writes the recipe performs If any is missing, stop. Say what is missing and what you need. Do not invent inputs to keep moving. ## HOLD — stop and return this, not a polished guess When you cannot proceed, return the gap. | Condition | What is missing | What it needs | Return instead | |---|---|---|---| | Object missing | Named object of work | One sentence from the user | I need the object. Holding. | | Required input missing | That input | Obtain or ask | Name the gap. Do not guess. | | Write authority missing | Explicit go-ahead | Ask | Read-only response or HOLD. | | Trigger mismatch | Correct skill | Route away | Wrong skill. Holding. | A HOLD is a return value, not a delay before you guess. ## Defaults: cut first This operation defaults to less, not more. - Prefer reuse and deletion over new surface area
Details
- Skill name
technical-writing- Repository
- jeremybrasher/grokbot-skills
- Path
collections/pstack/skills/technical-writing/SKILL.md- Repo updated
- 15 September 2026
FAQ
What does the Technical Writing skill do?
Layered technical-writing standard: Di\u00e1taxis 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. Observe required inputs first; HOLD when they are missing rather than guessing.
How do I install the Technical Writing skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jeremybrasher/grokbot-skills --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 jeremybrasher/grokbot-skills, which has 38 GitHub stars and 11 forks.
Related skills
Anti Patterns
38jeremybrasher/grokbot-skills
Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
Anydesign
38jeremybrasher/grokbot-skills
Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does t
Archetype Review Base
38jeremybrasher/grokbot-skills
Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts.
Unslop
38jeremybrasher/grokbot-skills
Cut AI tells from any writing. Must always apply. Observe required inputs first; HOLD when they are missing rather than guessing.
Content Planner
38jeremybrasher/grokbot-skills
GSC-driven content calendar. Pulls real Search Console data, finds the highest click-potential opportunities (striking-distance queries at positions 5-20, unanswered query intent, related-keyword expansions), and produces a dated, prioritized content calendar — ready to hand to /content-writer. Use when the user asks "plan my content", "what should I write next", "content calendar", "content plan", "content roadmap", "editorial calendar", "what topics will rank", "find quick-win SEO topics", "click-potential analysis", or "schedule my SEO content".
Vertical Creator
38jeremybrasher/grokbot-skills
Domain-knowledge primer for the marketing & creator vertical (creators, newsletter writers, podcasters, course sellers) so architect/pm don't spec naively against incumbents (Substack ~10%, Patreon 8–12%, Kajabi $149+, beehiiv, Buffer/Hootsuite/Later). Supplies the vocabulary, the non-obvious take-rate/red-ocean rules, the entities a real scheduler/analytics/monetization/sponsorship product must model, and the per-product wedge — with sponsorship-crm flagged as the white-space wedge. Applied by architect/pm during spec authoring for any of the four products in this vertical — content-scheduler
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.