Total 50,359 skills, Documentation & Writing has 1451 skills
Showing 12 of 1451 skills
Behavior Guidelines for Information Visualization Presentation. Automatically activated when the model's response contains structured information such as comparisons, steps, configurations, architectures, etc., ensuring priority use of visual formats like tables, code blocks, lists, tree structures, instead of pure text accumulation. Trigger words: "Use a table", "Draw a diagram", "Make a list", "Structure it", "Don't just use text", "Visualize", "Compare". Even without trigger words, the rules of this Skill should take effect as long as the response contains structured information suitable for visualization. It also applies to scenarios such as "Too much text to read", "Can it be more intuitive?", "Organize into a table".
Generates a step-by-step tutorial aligned with the Digital Speed brand voice. Use when asked to write a tutorial, how-to guide, setup guide, or walkthrough.
Enforce IPPF/UNFPA/UNAIDS publication-standard citations on MEL/SRHR output. Use whenever Ane produces a theory of change, evaluation design, indicator set, donor report, or SRHR programme analysis. Injects current authoritative framework versions with author and year, flags outdated versions, and applies the data-gap protocol. Do not use for non-MEL work.
Prose drafting technique for narrative fiction. Use when writing new scenes, chapters, or dialogue — whether in conversation with an author or producing a draft autonomously from a brief. Covers craft fundamentals; project-specific voice comes from style files passed alongside this skill.
Use this skill for "write a literature review", "synthesize papers", "review the literature", "summarize research findings", "identify research trends", "gap analysis", "thematic review", "systematic review", "scoping review", "narrative review", "compare studies", "research synthesis", or when the user wants to synthesize multiple papers into a cohesive literature review.
McKinsey-style storyline framework for building presentation decks. Use when users need to structure presentations, pitch decks, or strategic communications. Creates logical flow where each storyline becomes a slide title, progressing from problem to solution.
[Hyper] Create or refactor a project README.md by carefully reading the codebase. Detects project shape (CLI, library, web app, monorepo, plugin, framework, docs site, service), entry points, scripts, configuration, license, and existing docs, then produces a structured README in the project's primary documentation language. Use when the user wants a new README, a refactor of a stale README, or a section update grounded in the actual code.
Polish, restructure, or translate academic prose into Nature-leaning English using the paper-architecture and writing-strategy principles from Scientific English Writing & Communication, with phrase-level support from Academic Phrasebank. Use whenever the user asks to polish a manuscript paragraph, abstract, introduction, results, discussion, conclusion, title, methods section, or Chinese academic draft for publication-quality English.
Generate API documentation from source code with JSDoc and OpenAPI support
Add strict Nature/CNS citations to manuscript text by splitting long passages into citable segments, searching only accepted flagship and subjournal titles from Nature Portfolio, the AAAS Science family, and Cell Press, filtering by publication time range, and exporting one reference-manager-ready output by default. Use this skill whenever the user asks to input text and automatically get references, add citations to a paragraph/manuscript, find Nature-series or CNS support for statements, create text-to-reference correspondence, "分段引用", "自动给出引用", "Nature系列引用", "CNS及子刊", "支撑文献", "补引用", "找引用", or export EndNote/RIS/ENW/Zotero RDF.
Draft, audit, or revise point-by-point reviewer response letters for Nature-family manuscript revisions. Use when the user provides reviewer comments, editor decision letters, revision notes, response drafts, or asks how to respond to major/minor revision requests, rebuttal letters, response to reviewers, peer-review reports, 审稿意见回复, 逐点回复, 修回信, 大修回复, 小修回复, or 如何回复 reviewer.
Create an Architecture Decision Record (ADR) in canonical MADR v4 format capturing the why behind a significant technical choice. Use when user says 'document this decision', 'create an ADR', 'record architecture decision', 'why did we choose X', 'document the rationale', or when adding major dependencies, new frameworks, or changing fundamental patterns. Do NOT use for user-facing feature docs (use document-feature) or syncing existing docs (use update-doc).