Total 50,328 skills, Documentation & Writing has 1450 skills
Showing 12 of 1450 skills
Use when writing or revising scientific manuscripts, abstracts, figures, or references for journal submission and you need full-paragraph prose, scientific structure, citation-style guidance, or reporting-guideline support.
Use when choosing, comparing, or preparing for computer science venues, conferences, workshops, journals, tracks, deadlines, reviewer expectations, paper fit, or publication positioning.
Maintain the NeMo Gym Fern docs site — add, update, move, or remove pages under fern/. Use for any documentation change. Triggered by: "edit docs", "add doc page", "update docs", "rename page", "fix broken link", "add redirect", "preview docs", "publish docs", any request that touches `fern/`.
Draft a structured investment committee memo for PE deal approval. Synthesizes due diligence findings, financial analysis, and deal terms into a professional IC-ready document. Use when preparing for investment committee, writing up a deal, or creating a formal recommendation. Triggers on "write IC memo", "investment committee memo", "deal write-up", "prepare IC materials", or "recommendation memo".
Write Substack articles in Michael Hanko's exact voice. Enforces strict styling rules (no em dashes, no markdown tables) and captures his irreverent, self-deprecating, recovery-infused tone.
Creates comprehensive Technical Design Documents (TDD) with mandatory and optional sections through interactive discovery. Use when user asks to "write a design doc", "create a TDD", "technical spec", "architecture document", "RFC", "design proposal", or needs to document a technical decision before implementation. Do NOT use for README files, API docs, or general documentation (use docs-writer instead).
How to build scenes: entry, dialogue, pacing, transitions. Use when writing or evaluating how scenes work on the page.
How to analyze prose style and produce style reference files. Use when creating, updating, or evaluating style files: the reference documents that capture a project's voice patterns for writer and critic agents.
Write, rewrite, or edit user-facing text in the repo's preferred plain human style. Use for any prose task: docs, README sections, comments, release notes, PRDs, posts, emails, explanations, and requests to humanize or tighten text. Default to general prose rules; read references/documentation.md only for README, technical docs, usage guides, CLI/API docs, or documentation audits.
Rewrite Rust documentation comments to ensure all documentation and comments are in English, following rustdoc guidelines. Use when the user wants to clean up Rust documentation, translate Chinese comments to English, fix missing documentation, or ensure rustdoc compliance in a Rust codebase.
Drafts or revises a publication-ready research paper from RESEARCH.md, producing paper.md and refs.bib. Builds a clear claim-evidence narrative, writes in professional academic style, marks ungrounded claims [UNGROUNDED] and unverified citations [UNVERIFIED] inline, then auto-invokes review. Trigger phrases: "write paper", "draft paper", "revise paper", "start writing".
Cut AI tells from any writing. Must always apply.