Total 30,562 skills, Documentation & Writing has 1017 skills
Showing 12 of 1017 skills
Generate speculative fiction stories about systemic exploitation by collapsing comfortable moral distances. Use when exploring how privilege and harm are connected, when writing about systems that export consequences, or when you want stories where innocence becomes impossible.
Review and improve documentation with parallel evaluation and iterative improvement loop.
Draft and edit high-signal written artifacts and produce a Written Communication Pack (brief, outline, draft email/memo/doc, canonical doc option, quality gate). Use for writing, written communication, memo, email, doc, async update, rewrite for clarity. Category: Communication.
Produces a single-story walkthrough of AI-authored code changes from runtime trigger to final behavior, weaving changed and unchanged code into one narrative with annotated diffs, trade-offs, alternatives, and risk analysis. Use when asked to "explain what changed", "walk me through this diff", "summarize agent edits", "show how this feature works", or "explain this implementation step by step".
Expert-level academic research and LaTeX paper writing with IEEE/APA citation support. Creates peer-reviewed research papers, literature reviews, and theses with proper scholarly standards.
Expert in comedic roasts, witty insults, and self-deprecating humor that lands. Covers the craft of punching up vs down, timing, target selection, and knowing the line between funny and mean. Knows how to be savage while staying lovable. Use when "roast, burn, diss, self-deprecating, witty reply, comeback, shade, " mentioned.
Write, review, and improve blog posts for the Sentry engineering blog following Sentry's specific writing standards, voice, and quality bar. Use this skill whenever someone asks to write a blog post, draft a technical article, review blog content, improve a draft, write a product announcement, create an engineering deep-dive, or produce any written content destined for the Sentry blog or developer audience. Also trigger when the user mentions "blog post," "blog draft," "write-up," "announcement post," "engineering post," "deep dive," "postmortem," or asks for help with technical writing for Sentry. Even if the user just says "help me write about [feature/topic]" — if it sounds like it could become a Sentry blog post, use this skill.
Create compelling progress updates and release notes. Use when shipping a new feature or need to communicate progress to stakeholders.
Read and understand novel texts, and summarize them into smooth story outlines. Suitable for initial novel screening and generating 500-800 word story outlines
Generate technical design documents using a standard template and save them to a group Yuque knowledge base. For group use — stores designs in group repos with review workflow. Requires group Token.
Use when you need to produce a D2 decision document (RFC/Decision Doc) for a Spec Pack, and need to independently decide whether to execute D0 (bypass design via diversion) and D1 (optional research) even under pressure, avoiding guessing FEATURE_DIR, making up input details, writing design as implementation specifics, or leaving behind TODO/To-Confirm lists.
Create and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, and fundraising materials. Use when the user needs investor-facing documents, projections, use-of-funds tables, milestone plans, or materials that must stay internally consistent across multiple fundraising assets.