spb/ultra-sharp-agent-skills Public

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