Total 53,555 skills, Documentation & Writing has 1511 skills
Showing 12 of 1511 skills
Sync skills documentation to match recent source changes. On load, immediately finds commits newer than the skills-sync tag, identifies doc-relevant changes, and implements updates.
Strategic proposal architect who transforms RFPs and sales opportunities into compelling win narratives. Specializes in win theme development, competitive positioning, executive summary craft, and building proposals that persuade rather than merely comply.
Create comprehensive technical specs for SDK gaps, feature modules, or system centralization efforts. Use when writing specs, PRDs, gap analysis documents, or planning centralization of scattered functionality into a single module. Triggers on "create spec", "write spec", "gap spec", "centralize", "fill the gap".
Colloquial Review for Video Scripts, remove formal tone to make the script suitable for speaking. Use this when users mention "colloquial", "too formal", "sound like natural speech", "script review".
Gamma API for creating presentations, documents, and websites from text. Use when user mentions "Gamma", "create presentation", "generate slides", "make a deck", "create a document with Gamma", or "generate a webpage".
Generate API documentation from source code with JSDoc and OpenAPI support
Adversarial reading methodology for narrative fiction — find what doesn't work, not confirm what does. Focus-area driven with dedicated resources per area. Use when reviewing drafts, evaluating prose quality, or assessing changes at any stage.
A skill with a body that exceeds the word limit.
Monochrome — Ivory ledger paper with all-black type; Lora serif headlines, Jost body, no color at all. Anything that should feel like a hand-typeset ledger: user research synthesis, white papers, longform reports, academic and policy briefs, advisory deliverables, bilingual EN/CN reports.
Apply or draft TOGAF-aligned enterprise architecture artifacts using ADM phases, four architecture domains, baseline-to-target analysis, governance, and migration planning.
Review content files against a project's voice and style guidelines. Use when reviewing written content (MDX, markdown, copy) for tone, sentence structure, word choice, and bilingual policy compliance before committing. Triggers on "review voice", "check tone", "voice review", "content review", "does this match our voice", or after writing loop/ritual/article content.
Add a linked resource (external file reference) to a ***plain spec. Use when the user wants to reference a JSON schema, API spec, data file, or other external file from within a functional spec, definition, or implementation requirement.