Total 43,917 skills, Documentation & Writing has 1297 skills
Showing 12 of 1297 skills
Use when drafting or revising human-facing prose such as docs, essays, prompts, UI copy, reports, commit messages, PR text, or polished long-form writing. Combines anti-AI-trope editing with clear and concise style rules for stronger, more natural prose.
Generate reference documentation entry by entry for the public surface of a library (components, functions, commands, etc.), with manifest tracking, supporting both single-entry and batch modes. Fundamental difference from guidedoc: guidedoc teaches you how to use something, while libdoc tells you what each part looks like; guidedoc's information sources are solution docs + user knowledge, while libdoc's information source is the source code itself. Trigger scenarios: When the user says "write API documentation", "component documentation", "libdoc", "write documentation for each component", or when new public library interfaces are discovered after feature-acceptance.
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".
Use when initializing, bootstrapping, creating, or scaffolding the minimum docs-driven workflow layout for a repository before roadmap planning, specs, or implementation tasks exist.
Creates an Architecture Decision Record following the Nygard format to document significant technical decisions, their context, and consequences. Use when making technical choices that affect system architecture, technology selection, or development patterns.
Chinese Technical Documentation Writing Guidelines: Master Formatting, Terminology, and Structure in One Go, Say Goodbye to Machine Translation Style
Generate LaTeX exam cheatsheets from course materials (PDF/PPTX/MD/images). Use when user says "generate cheatsheet", "make a cheat sheet", "create exam reference sheet", "condense notes", or has course materials to turn into a compact LaTeX review sheet for exams.
Prepare, audit, or revise Nature-ready Data Availability statements, data repository plans, dataset citations, and FAIR metadata checklists for manuscripts. Use when the user asks about Nature data availability, research data sharing, repository selection, accession numbers, restricted or sensitive data, source data, supplementary datasets, DataCite-style dataset references, FAIR metadata for academic publication, or Chinese-to-English data availability wording for Chinese-speaking authors preparing Nature-family submissions.
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 and maintain documentation with drift detection
Generate API documentation from source code with JSDoc and OpenAPI support
Turn research findings into a polished paper-style draft with sections, equations, and citations. Use when the user asks to write a paper, draft a report, write up findings, or produce a technical document from collected research.