Total 52,836 skills, Documentation & Writing has 1498 skills
Showing 12 of 1498 skills
Guide to Excellent Chinese Writing: Enhance Chinese writing quality and rewrite existing articles. Based on the writing wisdom of Paul Graham, Yu Guangzhong, and Wang Dingjun. Usage Scenarios: - When users say "polish", "rewrite", "rewrite", "make the text flow better" - When users request "improve writing style", "write better", "high-quality Chinese" - When users provide articles and ask for revision or polishing - When high-quality Chinese content needs to be produced Trigger Words: /good-writing, /polish, good writing, polish, rewrite, rewrite, writing style, make the text flow better
Reviews and proofreads blog posts, articles, documentation, communications, emails, and any other write-ups to improve conciseness, legibility, clarity, and tone. Fixes typos, grammar issues, redundancies, run-on sentences, and punctuation errors. Use when the user asks to proofread, review, edit, or improve a piece of writing, or when they share text and ask for feedback, corrections, or a revised version.
Elite technical writer for product documentation, guides, and internal content. Use for writing new docs, reviewing drafts, restructuring content, creating templates, or improving clarity. Triggers on doc requests, MDX files, content structure questions, or writing style discussions.
Use when explaining code, concepts, or system behavior to a specific audience level - provides a structured explanation workflow with depth control and validation steps.
Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content, checking writing quality, or reviewing a draft.
When the user wants to create, optimize, or structure Terms of Service page. Also use when the user mentions "terms of service," "terms and conditions," "terms of use," "user agreement," "ToS," "legal terms," "service agreement," or "terms page."
Write point-by-point rebuttals to reviewer comments. Extract concerns from reviews, generate evidence-based responses, and format as a structured rebuttal document. Use after receiving peer review feedback.
Guides self-review of YOUR OWN academic paper before submission with adversarial stress-testing. Core method: 5-aspect checklist (contribution sufficiency, writing clarity, results quality, testing completeness, method design), counterintuitive protocol (reject-first simulation, delete unsupported claims, score trust, promote limitations, attack novelty), reverse-outlining, and figure/table quality checks. Use when: user wants to self-review or self-check their own paper draft before submission, stress-test their claims, prepare for reviewer criticism, or mentions 'self-review', 'check my draft', 'is my paper ready'. Do NOT use for writing a peer review of someone else's paper, and do NOT use after receiving actual reviews (use paper-rebuttal instead).
Documentation generation workflow covering API docs, architecture docs, README files, code comments, and technical writing.
Technical documentation specialist and knowledge curator. Use when the user asks to talk to Paige or requests the tech writer.
Cognitive Atom: Plain (Bai). Rewrites any content to be fully understandable by a smart 12-year-old. It is structure-free — form follows content. Activate this function when the user uses phrases like "put it in plain language", "speak human", "explain this", "plain", or "grok".
Write and maintain an implementation diary capturing what changed, why, what worked, what failed (with exact errors and commands), what was tricky, and how to review and validate. Activates proactively during non-trivial implementation work (new features, bug fixes, refactors, research spikes). Does not activate for trivial tasks like one-line fixes, config tweaks, or quick questions.