Category
documents Agent Skills
21 open documents skills for AI agents. Each package is a portableSKILL.md folder with trigger guidance, instructions, and a benchmark suite — installable into Claude Code, Codex, Cursor, and OpenCode.
- meeting-notesCore
Turn raw meeting transcripts, chat logs, or rough notes into clean, structured meeting notes with decisions and action items. Use whenever the user shares a transcript or messy notes, asks for meeting minutes, wants action items extracted, or says things like "clean up my notes from the standup" — even if they don't say the word "minutes".
- Category
- documents
- Context
- 536
- Updated
- 2026-07-11
- architecture-decision-recordsCommunity
Write concise Architecture Decision Records that capture context, decision, and consequences. Use whenever the user asks for an ADR, architecture decision log entry, decision record, or why we chose technology X over Y in a durable doc — even for small stack choices.
- Category
- documents
- Context
- 332
- Updated
- 2026-07-26
- contract-redlinesCommunity
Redline commercial paper — MSAs, vendor agreements, order forms, and DPA-adjacent commercial terms — as a business and risk pass, not legal advice. Use whenever the user says redline this MSA, mark up the contract, review a vendor agreement, check order form terms, flags auto-renew, liability cap, or indemnity, asks "is this clause bad", or wants fallback language before signing.
- Category
- documents
- Context
- 905
- Updated
- 2026-08-16
- disaster-recoveryCommunity
Write and review disaster recovery and backup restore playbooks. Use whenever the user asks for a DR plan, RPO/RTO targets with restore evidence, a failover drill, ransomware restore steps, or "can we restore" — not a single-alert runbook, live incident command, or SLA wording alone.
- Category
- documents
- Context
- 879
- Updated
- 2026-08-16
- golden-path-docsCommunity
Write internal developer-portal and golden-path docs — the blessed, supported way to create a service, ship, and observe it. Use whenever the user asks for a golden path, paved road, developer portal, internal platform docs, IDP Backstage docs, or "how do we start a new service here" — even if they call it a handbook page or TechDocs template.
- Category
- documents
- Context
- 944
- Updated
- 2026-08-25
- incident-commandCommunity
Run a live incident as commander — roles, timeline, decisions, and page cadence — distinct from postmortems and customer comms. Use whenever the user is in an active outage, asks who should do what on the bridge, wants an IC checklist, severity call, or war-room notes while the incident is still open.
- Category
- documents
- Context
- 716
- Updated
- 2026-08-16
- incident-postmortemsCommunity
Write blameless incident postmortems with timeline, impact, root cause, and action items. Use whenever the user asks for a postmortem, RCA, incident write-up, outage report, or lessons learned after a production failure — even from rough Slack notes or pager logs. For a live outage still in progress, use incident-command.
- Category
- documents
- Context
- 556
- Updated
- 2026-08-16
- onboarding-guidesCommunity
Write new-hire and contributor onboarding guides that get people productive fast. Use whenever the user asks for an onboarding doc, starter guide for engineers, contributor getting-started, first-week plan, or "how do we onboard" handbook section.
- Category
- documents
- Context
- 292
- Updated
- 2026-07-26
- policy-writingCommunity
Write clear internal policies people can follow under time pressure. Use whenever the user asks for a company policy, acceptable use policy, security policy draft, travel policy, or HR/process policy that needs plain language.
- Category
- documents
- Context
- 208
- Updated
- 2026-07-26
- product-requirementsCommunity
Write decision-ready product requirements (PRDs) with problem, users, success metrics, non-goals, and scoped requirements. Use whenever the user asks for a PRD, product spec, requirements doc, feature brief, or to turn a vague idea into shippable product requirements.
- Category
- documents
- Context
- 599
- Updated
- 2026-08-16
- project-proposalsCommunity
Turn a rough initiative into a decision-ready project proposal with outcomes, scope, plan, costs, risks, and a clear approval request. Use whenever the user needs a business case, internal proposal, project charter, funding request, or stakeholder pitch, even if they only provide scattered notes or an idea.
- Category
- documents
- Context
- 477
- Updated
- 2026-07-11
- release-notesCommunity
Write clear user-facing and developer release notes from commits, PRs, and changelogs. Use whenever the user asks for release notes, a changelog entry, what's new for a version, ship notes for customers or engineers, or a summary of changes between tags — even if they only paste commit subjects or merged PR titles.
- Category
- documents
- Context
- 724
- Updated
- 2026-07-26
- resume-builderCommunity
Build or rewrite resumes and tailor them to a specific job description, with achievement-focused bullets that pass ATS screening. Use whenever the user shares a resume or CV, asks to improve or tailor one, wants bullets rewritten, or says "help me apply for this job" with a job posting — even if they only paste their work history as rough notes.
- Category
- documents
- Context
- 526
- Updated
- 2026-07-11
- rfc-design-docsCommunity
Write RFCs and technical design docs that force clear decisions. Use whenever the user asks for an RFC, design doc, architecture proposal, tech design, or "how should we build X" write-up for a feature or system change — even from a rough bullet list.
- Category
- documents
- Context
- 588
- Updated
- 2026-07-26
- rfp-responseCommunity
Structure RFP and RFI responses that map requirements to evidence. Use whenever the user answers a vendor questionnaire, RFP, RFI, security questionnaire, or procurement response with claim-and-evidence rows.
- Category
- documents
- Context
- 279
- Updated
- 2026-07-26
- runbook-writingCommunity
Write operational runbooks that on-call engineers can follow under stress. Use whenever the user asks for a runbook, playbook, ops procedure, alert response guide, or how to document incident response steps for a system.
- Category
- documents
- Context
- 356
- Updated
- 2026-07-26
- security-questionnaireCommunity
Answer vendor and enterprise security questionnaires — SIG, CAIQ, SOC 2, ISO, and custom sales security packs — with evidence, not slogans. Use whenever the user pastes a security questionnaire, vendor assessment, SIG/CAIQ, "sales needs this by Friday", or a customer asking how you encrypt, auth, or subprocess.
- Category
- documents
- Context
- 574
- Updated
- 2026-08-16
- sla-slo-writingCommunity
Write SLAs and SLOs that operations can measure and support can explain. Use whenever the user drafts service levels, uptime commitments, error budgets, customer-facing availability language, or internal reliability targets.
- Category
- documents
- Context
- 255
- Updated
- 2026-07-26
- status-reportsCommunity
Write clear project and program status reports for stakeholders. Use whenever the user asks for a weekly status, program update, executive status, RAG status, or progress report on a project or initiative.
- Category
- documents
- Context
- 245
- Updated
- 2026-07-26
- technical-documentationCommunity
Write and improve technical documentation, tutorials, runbooks, and reference pages that users can follow successfully. Use whenever the user asks for docs, a README, setup instructions, an operational runbook, API usage guidance, or an explanation of how a system works, including requests to document code.
- Category
- documents
- Context
- 504
- Updated
- 2026-07-11
- vendor-evaluationCommunity
Run structured vendor evaluations and scorecards for build-vs-buy decisions. Use whenever the user compares vendors, shortlists tools, runs a bake-off, or needs a fair scorecard across products for a purchase decision.
- Category
- documents
- Context
- 252
- Updated
- 2026-07-26