Skip to content
Development
Skill

/technical-writing

Write or revise technical documentation, procedures, comments, commits, releases, and incident reports.

BOOST
From plugin
khanelinix
34750 skills10 agents6 commands
Install
$ npx -y skills add khaneliman/khanelinix --skill technical-writing --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/technical-writing

Context preview

The summary Claude sees to decide when to auto-load this skill.

Write or revise technical documentation, procedures, comments, commits, releases, and incident reports.

SKILL.md

technical-writing.SKILL.md
name: technical-writing
description: Write or revise technical documentation, procedures, comments, commits, releases, and incident reports.

Technical Writing

Make text easier to understand without deleting technical content. Treat source facts and structure as invariants, not optional detail. Claim full ASD-STE100 conformance only with the official current standard and controlled dictionary.

Select Workflow

  • **Write new text:** read [rules.md](references/rules.md), then draft for the

intended reader and text type.

  • **Rewrite existing text:** read [rules.md](references/rules.md), inventory

protected content, rewrite, then score source against candidate.

  • **Comments or commits:** read the matching sections in

[rules.md](references/rules.md) and obey repository contributor canon first.

  • **Incident reports or postmortems:** preserve chronology, evidence,

uncertainty, impact, response, and follow-up ownership while applying the same sentence rules.

Rewrite Contract

1. Identify audience, purpose, and procedural or descriptive mode. 2. Record facts, caveats, figures, identifiers, code, links, and tables that must remain. 3. Rewrite by clarifying sentences, naming actors, stabilizing terms, and removing filler. Never gain brevity by deleting protected content. 4. Run the bundled scorer:

   python3 scripts/style_guard.py score SOURCE CANDIDATE --mode descriptive

5. Treat lexical retention as a measurable rewrite gate, not proof of fact retention. Resolve every missing number, code span, URL, table, or required fact. 6. Compare source and candidate directly. Confirm that meaning, scope, uncertainty, and causal claims did not change.

Use `--required-facts FILE` for one exact required item per line. Use `--minimum-retention` only to tune the lexical warning threshold.

Deterministic Checks

`scripts/style_guard.py` provides three read-only checks:

  • `scan [PATH]`: report prohibited emoji and Unicode em dashes outside code.
  • `commit-message PATH`: validate repository commit-message limits.
  • `score SOURCE CANDIDATE`: report content retention and formatting violations.

The checks can reject measurable violations. Model judgment still owns factual equivalence, correct terminology, audience fit, and useful structure. Sentence length and ordinary word choice are contextual judgments, not rejection rules.

Read more
Ships withkhanelinix

Run packages directly with: Or install from the packages output. For example:

Get the whole plugin

Other skills on khanelinix.