Tech Doc Skill En

tech-doc-skill-en

A Claude Code skill for writing, editing, and reviewing English technical documentation. It applies the [Google developer documentation style guide](https://developers.google.com/style) first, and the [Microsoft Writing Style Guide](https://learn.microsoft.com/style-guide) only where Google is silent. Google wins every conflict, and the conflicts that actually change output are listed in one table.

A target project's own conventions outrank both. Locale is the usual case: Google requires US English, and a project that has chosen otherwise keeps its choice.

Every rule was checked against the text of both guides rather than recalled. Rules that belong to neither guide are confined to a labeled section and marked as such.

Install

git clone https://github.com/lilhorse/tech-doc-skill-en.git \
  ~/.claude/skills/tech-doc-style-english
cd ~/.claude/skills/tech-doc-style-english
scripts/refresh_sources.sh

The skill loads in the next session. The second command fetches the style guide text that the skill greps to settle a rule; see [Sources](#sources) for why it isn't bundled.

Other agent runtimes read `SKILL.md` the same way. Codex and Gemini CLI look in `~/.codex/skills/` and `~/.agents/skills/`.

Layout

The entry point is `SKILL.md`; everything else is loaded on demand or run by hand:

Path	Contents
SKILL.md	Entry point: authority, scope, rule priority, conflict table, routing
references/	Voice, mechanics, word list, procedures, and a project override template
scripts/lint_en_docs.py	Style checker; --min-level warning reports only sourced rules
scripts/refresh_sources.sh	Fetches both guides as plain text
tests/	61 unit tests for the checker
eval/	Held-out evaluation harness, scored against Google's own counter-examples

Check a document

python3 scripts/lint_en_docs.py --min-level warning FILE

Findings are candidates, not verdicts. Several rules