Total 52,846 skills, Documentation & Writing has 1498 skills
Showing 12 of 1498 skills
Edits, rewrites, or improves text for clarity, tone, grammar, or style.
Write newsletter articles for The Hybrid Builder (chatwithgpt.substack.com) with intelligent cross-referencing of the full article archive. Includes sitemap-based article cache with theme indexing, reference suggestions, session transcript export, and cover image generation. Use when asked to write a blog post, article, or newsletter about a collaboration or technical topic.
Summarize the objectives, structure, constraints, naming and collaboration rules of the entire project to form reusable project-level specification documents
Professional essay writing pipeline — from scattered notes to polished prose in six guided steps (brief → outline → draft → revise → review → polish)
Create well-structured RFCs and technical proposals for software projects. Use this skill whenever the user wants to write an RFC, technical proposal, design doc, architecture doc, or system design overview. Also trigger when the user says things like "write an RFC", "I need to propose a new system", "create a technical proposal", "document the architecture", "write up the design", "I need a design doc", or "explain the system architecture in a doc". Even if they just say "RFC", "design doc", or "arch doc", use this skill. Covers both RFCs (proposing what to build) and architecture docs (documenting an existing codebase).
Copywriting and content creation standards for website pages, blog posts, and all written copy. Covers headlines, ledes, readability, niche vocabulary, scannable formatting, and persuasive structure. Cross-cutting skill — apply whenever...
Document the pitfalls encountered or good practices discovered during this work into searchable learning documents, so that both AI and humans can look them up when similar tasks arise in the future. Two tracks: The pitfall track records experiences where "things should have worked but didn't" — bugs, configuration traps, environment issues, integration failures; The knowledge track records findings that "should be the default approach going forward" — best practices, workflow improvements, reusable patterns. Trigger scenarios: Proactively prompt for input when wrapping up feature-acceptance or issue-fix, or when the user says phrases like "document knowledge", "learning", "document learnings", "record this experience". Spec documents record what was done and how it was done, while learning documents record what pitfalls were encountered / what was learned — the two complement each other and are not interchangeable.
Draft patent claims for an invention. Use when user says "撰写权利要求", "draft claims", "写权利要求书", "claim drafting", or wants to create patent claims. The core skill of the patent pipeline.
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.
Synthesize a PRD (Product Requirements Document) for a big new feature. Synthesis (not interview) — uses existing project context and explicit ADRs. Asks before gh issue create. Use when scoping a substantial new feature in PRD shape (e.g., before a sprint).
Use when rewriting AI-generated text to match a specific person's or brand's authentic voice. Use when AI output sounds generic, corporate, or detectable. Unlike generic "humanizers," this skill requires voice analysis input and produces voice-consistent output, not fake imperfections.
Generate player-facing patch notes from git history, sprint data, and internal changelogs. Translates developer language into clear, engaging player communication.