ADR authoring + design review. Trade-offs, consequences, alternatives.
By use case
Top Communication & Docs Skills
Internal comms, doc co-authoring, technical writing, status reports, FAQs.
24 skills indexed · ranked by composite score
Top 6 Comms & Docs skills
- 1.architecture—ADR authoring + design review. Trade-offs, consequences, alternatives.
- 2.documentation—Technical writing that engineers will actually read and update.
- 3.incident-response—Incident triage + comms + blameless postmortem in one harness.
- 4.consolidate-memory—Memory hygiene. Merge, fix, prune.
- 5.ux-copy—Microcopy that respects the user. Errors, empty states, CTAs, onboarding.
- 6.init—Bootstrap a CLAUDE.md so future sessions start informed.
About Communication & Docs
The best agent skills for communication and documentation in 2026 generate the structured artifacts teams actually ship: standup updates from yesterday's commits, ADRs from proposed designs, blameless postmortems from incident timelines, and release notes from merged PR descriptions — each in the shape your team expects. Communication & docs Skills are how engineering and product teams stop dropping things between people — status updates, RFCs, ADRs, runbooks, incident postmortems, onboarding guides, Slack updates, internal newsletters. The Skills here encode the structure of each artifact so an agent can produce the right shape on the first pass.
Common workflows include drafting a standup update from yesterday's commits and tickets, writing an architecture decision record from a proposed design, producing a runbook for an on-call rotation, authoring a blameless postmortem after an incident, generating onboarding documentation for a new repo, writing customer-facing release notes, and assembling internal status reports. Several pair with productivity MCP servers — Linear, Monday, ClickUp, Notion, Slack, MS365 — for live data.
Engineering managers, technical writers, product managers, and anyone who has to translate work into shareable artifacts uses these Skills. Composite scoring weights install count, provenance, and how cleanly the Skill respects house style — generic doc Skills produce generic docs; the top ones load your style guide and follow it.
Ranked by score
Best Comms & Docs Skills
Skills that do comms & docs well — ranked transparently.
Technical writing that engineers will actually read and update.
Incident triage + comms + blameless postmortem in one harness.
Microcopy that respects the user. Errors, empty states, CTAs, onboarding.
Turn raw research into themes, segments, and a prioritized next-steps list.
Research-ops in a skill. Plan the study, run it, synthesize the findings.
Brand-voice QA before content ships. Severity-ranked findings with rewrites.
Workplace memory that actually understands your team's shorthand.
PowerPoint decks with layouts, charts, speaker notes — programmatic from prose.
Internal comms that read consistent. Newsletters, status reports, FAQs, updates.
Multi-author edits with suggestion mode and conflict resolution.
Strip the AI tells. Multi-pass editing for content that reads opinionated, not generated.
C4, deployment, sequence-of-events architecture diagrams generated from natural-language descriptions.
Full email sequences with branching, exit conditions, and copy that does not read like an AI wrote it.
Notion API: page/database CRUD, block hierarchies, rich text, schema sync.
Excalidraw JSON diagrams from prose, with rendering self-checks.
HTML slide decks from prose. Easy to embed, version, and edit later.
Standup updates from recent commits, PRs, and ticket moves. Yesterday/today/blockers.
Mermaid diagrams from prose with self-validating syntax. Sequence, flowchart, ER, state.
LinkedIn posts that read human. Hook patterns, voice modeling, carousel scripts.
FAQ
Frequently asked
What does the standup Skill do?
It reads yesterday's commits, PRs, and ticket movement, then structures a yesterday/today/blockers update in the format your team uses. It can post to Slack via MCP.
Are these Skills good for ADRs?
Yes — the architecture Skills here author ADRs with the standard sections (context, decision, consequences) and check the proposed decision for tradeoffs you may have missed.
How do incident-response Skills work?
They walk you through triage, status updates, severity assessment, and a blameless postmortem template. The PagerDuty MCP integration adds live alert context.
Can these Skills produce release notes?
Yes — from git log, ticket movement, or merged PR descriptions. The top Skills separate customer-facing notes from internal changelogs automatically.
Do they work with Notion or Confluence?
Several pair with Notion via the Notion MCP server for live page reads and writes. Confluence support depends on the MCP server you have configured.
Other categories