Total 50,365 skills, Documentation & Writing has 1451 skills
Showing 12 of 1451 skills
Structured, reproducible analysis documentation. Use when documenting analysis findings, creating analysis notebooks, ensuring reproducibility, or building analysis archives for future reference.
Use when you want to discover content series across your existing work — finds clusters by theme rather than topic, identifies repeated points from different angles, flags incomplete arcs, and suggests series framing that makes relationships explicit.
Convert user copy into Zhihu-style content, include 2-3 characteristic keywords (such as guide, tutorial, cheat sheet, etc.), rewrite it according to 10 writing skills, and append Tags at the end; use this when users need to rewrite product introductions, strategy shares, etc. into viral Zhihu copy
Systematic literature review workflow: scope, search (arXiv, Semantic Scholar, Google Scholar), screen, extract, synthesize, and identify gaps. Triggers on: "literature review", "survey the literature", "related work", "systematic review", "synthesize the research", "find papers about", "research gap analysis".
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.
Write and research technical documentation. Cover information architecture, style guides, API documentation, user research, content strategy, and documentation operations. Triggers on "write technical documentation", "create API docs", "developer tutorial", "information architecture", "style guide", "content strategy", "documentation audit", "user research", or "technical writing". Developer learning programs and curriculum: developer-education-lead.
Use when planning, running, auditing, or documenting systematic reviews, scoping reviews, PRISMA-style flows, screening decisions, inclusion criteria, exclusion criteria, or reproducible literature searches.
Rewrite and edit existing text to sound natural and human, removing common AI writing tells while preserving meaning and facts. Use when asked to humanize, de-AI-ify, un-AI, make it sound less robotic, polish an AI draft, or remove AI-writing signs in any prose (emails, docs, posts, essays, scripts).
Create runbooks, playbooks, and technical documentation for engineering teams. Use when the user wants to document a process, create a runbook, build operational docs, or formalize any repeatable technical procedure. Triggers on requests like "create a runbook for...", "document this process", "write a playbook", or any technical documentation request.
README style guide for concise, direct documentation. Use when writing or editing README files.
Novel writing assistant supporting creating novels from scratch, continuing chapters, character design, and worldbuilding. Works with all genres (sci-fi, fantasy, mystery, romance, wuxia, etc.). Triggers: (1) User requests to write a novel, e.g., "help me write a sci-fi novel", "create a mystery story"; (2) Continue or modify existing content, e.g., "write the next chapter", "modify this character"; (3) Character-related tasks, e.g., "design a villain", "create a love interest for the protagonist"; (4) Worldbuilding, e.g., "design a magic system", "build a cyberpunk world".
Creates an Architecture Decision Record (ADR) documenting a significant technical decision, its context, alternatives considered, and consequences. Every major technical choice should have an ADR.