Comms Technical Writing

Layered technical-writing standard covering document modes, sentence style, instruction rules, and unambiguous syntax. Use when writing or reviewing skills, docs, READMEs, RFCs, PR descriptions, or commit messages.

23 stars 1 forksWriting & Content

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add jpoehnelt/skills --skill comms-technical-writing
Manual install
git clone --depth 1 https://github.com/jpoehnelt/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/comms-technical-writing ~/.claude/skills/comms-technical-writing

Personal 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

Write so a tired engineer understands on the first read. Apply all layers.

Repo facts: where the repo keeps durable docs, design records, and change notes or changesets, and any style guides for user-facing copy (`AGENTS.md` or `CLAUDE.md`).

Three rules sit above them:

- **Cut every word that does no work.** "In order to" is "to".
- **Use the short, everyday word.** "Use", not "utilize". A long word must buy its length with precision.
- **When a rule makes a sentence worse, fix the sentence another way.** A sentence that obeys every rule and sounds machine-written has failed.

The codebase is the word list. Write the real symbol, file, flag, or command name. Do not invent jargon. Use words a developer says out loud: "move", "delete", "a budget that only decreases". Preserve the author's meaning and uncertainty when editing.

## Vary the rhythm

- Mix sentence lengths. Short sentences land a point. Longer ones carry a fact with its condition.
- Have a view where the mode allows it. Explanation weighs trade-offs. Reference stays dry.
- Be specific. Not "schema changes can cause issues" but "a column rename fails the build".

## Pick one mode per document

Ask whether the content serves action or understanding, and learning or work.

- **Tutorial** (action, learning). Say what the learner will build. Every step shows a visible result and the expected output. Explanation is one clause and a link.
Read the full skill on GitHub

Details

Skill name
comms-technical-writing
Path
comms-technical-writing/SKILL.md
License
MIT
Repo updated
12 November 2026

FAQ

What does the Comms Technical Writing skill do?

Layered technical-writing standard covering document modes, sentence style, instruction rules, and unambiguous syntax. Use when writing or reviewing skills, docs, READMEs, RFCs, PR descriptions, or commit messages.

How do I install the Comms Technical Writing skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add jpoehnelt/skills --skill comms-technical-writing. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Comms Technical Writing popular?

It lives in jpoehnelt/skills, which has 23 GitHub stars and 1 forks.

Related skills

Agents Correct

23

jpoehnelt/skills

Find the mistakes agents keep repeating in a repo and make each one impossible, trying architecture first, then types, lint, tests, and docs last. Use when the operator keeps correcting the same mistake, or for /agents-correct.

AI, LLMs & Agents

Agents Create Verification Skill

23

jpoehnelt/skills

Generate a project-local verify skill that drives the app like a user through a browser with Playwright, a CLI, or HTTP. Use for /agents-create-verification-skill, "make a verify skill for this repo", or when a project has no scripted way to prove UI, CLI, or service behavior.

AI, LLMs & Agents

Agents Reflect

23

jpoehnelt/skills

After a work session, review what went wrong and right and turn each lesson into a concrete edit to an existing skill or AGENTS.md line. Use when the user says "reflect" or /agents-reflect.

AI, LLMs & Agents

Eng State Machine

23

jpoehnelt/skills

Model an entity's lifecycle (status, state, phase) as an explicit state machine with a pure decide function, one guarded write path, and events from a durable record. Use when adding or changing a status field, a transition, or a reaction to one, when several writers set the same status, or when moving ad hoc status writes onto a machine.

Writing & Content

Alterlab Vcd Layout Designer

21

AlterLab-IEU/AlterLab-FC-Skills

This skill should be used when the user asks about "layout design", "editorial design", "grid system", "magazine layout", "book design", "publication design", "page layout", "spread design", "Swiss grid", "modular grid", "column grid", "act as a layout designer", "layout designer mode", "print design", "editorial layout", "page composition", "white space", "bleed and margins", "InDesign layout", "multi-page document", "annual report design", "catalog design", "zine design", or needs expertise in publication design, grid system construction, editorial layouts, and multi-page document architectu

Writing & ContentIn 1 list

Htmx

9

piyiotisk/htmx-skills

Build interactive web UIs with htmx by adding hypermedia attributes to HTML and returning HTML fragments from the server. Use when writing or reviewing htmx code, working with hx-* attributes (hx-get, hx-post, hx-trigger, hx-target, hx-swap, hx-boost), wiring AJAX/SSE/WebSocket-driven HTML, or designing server endpoints that respond with HTML partials.

Writing & Content

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.