Total 30,646 skills, Documentation & Writing has 1022 skills
Showing 12 of 1022 skills
Quickly generates 3-4 article topic directions with titles, outlines, and pros/cons analysis. Use when user saves a brief, requests topic suggestions, or needs article direction options. Provides evaluation of workload, testing needs, and target audience for each option.
Professional technical writing and documentation skill for creating and maintaining comprehensive, accurate, and user-friendly documentation for codebases, APIs, deployment processes, and end-user guides.
Check all READMEs for accuracy and consistency across the meta-repo
GitBook documentation platform - creating docs, publishing sites, Git sync, API references, and collaboration
OpenAPI/Swagger specification standards and API documentation best practices
Detect and fix AI writing patterns including overused phrases (testament to, pivotal, landscape, delve), structural tells (rule of three, em dash overuse, negative parallelisms, copula avoidance), promotional language, and vague attributions. Use when user asks to "make text sound human", "remove AI tells", "humanize writing", mentions patterns like "too many dashes" or "sounds like ChatGPT", or requests natural/conversational tone. Triggers: AI-generated, humanize, writing style, natural writing, human voice, ChatGPT sound, remove AI patterns, conversational tone, writing voice. Credits: Based on Wikipedia's Signs of AI writing guide by @blader
Create a comprehensive inventory of a codebase. Map structure, entry points, services, infrastructure, domain models, and data flows. Pure documentation—no opinions or recommendations. Use when onboarding to an unfamiliar codebase, documenting existing architecture before changes, preparing for architecture reviews or migration planning, or creating a reference for the team. Triggers on requests like "map this codebase", "document the architecture", "create an inventory", or "what does this codebase contain".
Generate clear, professional, and polished Japanese technical articles suitable for corporate blogs, official documentation, and technical publications. Use this skill when the user wants to create enterprise-level content with consistent polite tone (です/ます), logical structure, and authoritative voice. Triggers include requests like "polished article", "professional tone", "enterprise blog", "公式ドキュメント", "プロフェッショナルな記事", or when content needs formal technical writing.
Transform technical article drafts or source materials into human-like, high-quality Japanese technical articles. Use this skill when the user wants to generate, rewrite, or humanize technical articles (especially about TypeScript, JavaScript, React, or frontend topics) following specific human-writing patterns and style guidelines. Triggers include requests like "記事を人間風に", "tech article を生成", "humanize this article", or providing article source materials.
Comprehensive editing checklist and procedures covering grammar and style rules, fact-checking, consistency verification, and readability metrics. Use when reviewing drafts, ensuring quality, or preparing content for publication.
This skill should be used when the user asks to "rewrite my resume", "fix my resume", "humanize my resume", "make my resume sound human", "clean up my resume bullets", "reword my resume", or wants AI-sounding text in their resume rewritten with annotations explaining each change. Works for all resume and CV types: standard US, federal, academic, legal, medical, consulting, tech, executive, military transition, education, nonprofit, trades, creative, investment banking, and EU/Europass formats. Entry-level through executive.
Transform source material into authentic, human-written content. Use for ANY writing task - newsletters, articles, social posts, emails. Combines voice transformation, AI pattern detection, and Charlie Deist's signature moves. Replaces the old ai-tells and human-writing skills.