0xa3b/writing
Writing skills for prose, technical writing, and agent instructions.
Use when creating, editing, tightening, or reviewing files that instruct agents — AGENTS.md, CLAUDE.md, SKILL.md and its bundled scripts, agent definitions, or system-prompt fragments — including a supplied diff to one, and when handing any task to a sub-agent or background agent, however small, before writing its prompt. Do not use as the entry point for reviewing the session's own changes, which a review workflow owns; for READMEs or other docs (technical-writing); for a terminology section's entries; for conceptual questions about instruction files; or for other code the session writes itself, even when the program is an agent.
Use when asked to write, rewrite, tighten, shorten, or review general prose for a human reader — a chat reply, explanation, summary, announcement, email, newsletter, or blog post — or to make text sound less AI-generated, robotic, or stilted, or to cut filler and slop from text. This is the base style for all prose; skills for specific artifact classes override it for their artifacts. Do not use when the target is a technical artifact or a technical comment or reply in an issue or review thread, even if the user asks to rewrite, tighten, or improve its prose. Technical-writing owns that composition after the substance and disposition are settled; verifying, triaging, or deciding how to handle existing feedback belongs to the feedback-handling workflow. Also do not use for files that instruct agents (agent-instructions); for commit messages; for program code; or for conceptual questions about writing style.
Use when writing, editing, or reviewing technical artifacts — READMEs, CONTRIBUTING and setup guides, knowledge-base pages, runbooks, migration and upgrade guides, API reference prose, architecture and design documents, release notes, long-form docstrings, pull request descriptions, or issue and ticket descriptions — including making text clearer for non-native English readers. Do not use to review README or documentation files the user changed in this checkout; engineering:review-changes owns that review and applies this skill inside. Do not use to assess, triage, or decide changes from unresolved review feedback. Once another workflow settles the feedback, use for drafting or rewriting technical comments in issue trackers, pull or merge request comments, and reviewer replies. Do not use for decision records (engineering:decision-records); for agent-instruction files such as AGENTS.md or SKILL.md; for chat responses, commit messages, or code comments; or for conceptual questions about writing standards.