From amazon-doc-writer
Shared style and quality-bar skill for Amazon-style internal docs. Use this whenever drafting a PR/FAQ, technical design, mini design, analysis report, or any other Amazon narrative document. It defines tone, structure, narrative-prose rules, the "so what" test, weasel-word bans, and the self-review checklist.
How this skill is triggered — by the user, by Claude, or both
Slash command
/amazon-doc-writer:amazon-writing-styleThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Amazon's internal docs are **written narratives**, not slide decks. They are
Amazon's internal docs are written narratives, not slide decks. They are read silently at the start of a meeting and then discussed. This skill captures the conventions every Amazon-style doc must follow.
amazon-doc-writer agent.PRFAQ: <Product Name> or Technical Design: <Capability>)."P99 latency is 180 ms (measured 2025-04-12, n=10k)" over
"latency is low".2025-05-18), not relative ones (last quarter).120 ms, 3.2 GB/s).Replace these with concrete claims:
Hedging is acceptable when honest (e.g. "We estimate, with ±20% uncertainty, that…"). Hedging to dodge a hard question is not.
For every paragraph, ask: if a reader skips this paragraph, what decision or understanding do they lose? If the answer is "nothing", cut it.
writing-* sibling skill for the section template that doc type
requires on top of these style rules.npx claudepluginhub louleowk/awesome-plugins --plugin amazon-doc-writerCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.