# writing-skills — Writing Skill Collection **Author:** Simon-Pierre Boucher **Contact:** contact@spboucher.ai Ten ultra-sharp stylistic writing skills following the method in [../RESEARCH-SYNTHESIS.md](../RESEARCH-SYNTHESIS.md). As stylistic skills, every one carries ✅/❌ (do/never) example pairs, boundary conditions, and a self-review workflow. User-facing release notes remain in [../skill-2-writing-release-notes/](../skill-2-writing-release-notes/). All pass `python3 ../tools/validate_skills.py`. ## The collection and its boundaries **Technical writing** | Skill | Handles | Explicitly does NOT handle | |---|---|---| | `writing-technical-documentation` | READMEs, architecture docs, runbooks, ADRs | API reference → `writing-api-documentation`; tutorials; release notes | | `writing-api-documentation` | endpoint/SDK reference, runnable examples, error tables | conceptual guides; designing the API itself | | `writing-tutorials` | step-by-step learning content with checkpoints | reference docs; conceptual overviews | | `writing-blog-posts` | technical posts: one idea, hook, specifics, skimmable | documentation; tutorials; marketing copy | | `writing-agent-skills` | authoring SKILL.md files per the Sharp Skill method | prompts/system prompts; CLAUDE.md; MCP tool definitions | **Business writing** | Skill | Handles | Explicitly does NOT handle | |---|---|---| | `writing-professional-emails` | subject-line asks, BLUF body, next steps | marketing campaigns; chat; formal letters | | `writing-executive-summaries` | BLUF, one page, numbers over adjectives, recommendation | full reports; blog posts; meeting notes | | `writing-proposals` | their-problem-first, scope + exclusions, options, next step | internal exec summaries; contracts; grants | | `writing-meeting-notes` | decisions/actions first, owner+deadline, 24h distribution | exec summaries; status reports; transcription | | `editing-and-proofreading` | fixed four-pass revision: structure → paragraphs → sentences → mechanics | writing from scratch; translation; code review | ## Shared conventions - Description = WHAT + "Use when …" (literal phrases) + "Do not use for …" - House rules are numbered, each with a ✅/❌ pair - Every workflow ends with a self-review pass against the rules - `SKILL.md` <150 lines; extended before/after examples in `references/examples.md` (with TOC)