Total 52,250 skills, Documentation & Writing has 1491 skills
Showing 12 of 1491 skills
Use for deep requirements analysis, technical specifications, agile documentation, or architecture/design reviews.
Extract and document a writer's distinctive voice patterns for consistent reproduction. Use when you need to capture writing voice, analyze writing style, create a voice guide, or write in someone's established style. Keywords: voice, tone, style, writing analysis, fingerprint.
Use when documentation needs to be updated, clarified, or reorganized to better serve users' jobs-to-be-done with low cognitive load and high signal.
Generate or update a README.md in French, oriented Product Owner, with Mermaid diagrams. Reviews and improves technical documentation in docs/. Also generates CLAUDE.md and AGENT.md if missing. Triggers on: create readme, update readme, generate readme, générer le readme, mettre à jour le readme, /readme.
Read this skill before updating changelogs
Simulate peer review by constructing reviewer personas from Zotero sources. Identifies relevant perspectives, retrieves full texts, builds reviewer profiles, and generates focused reviews on theory/methods and findings.
기존 기능의 암묵지를 명세서로 변환하여 as-is Context Pack(주제별 문서 폴더)을 생성하는 스킬. "기능 문서화", "기존 기능 분석", "as-is 정리", "docs/기능별설명 생성" 키워드로 트리거. 신규 기능 Spec이 필요하면 peach-gen-spec을 사용한다.
Write a client proposal or quote for a service business. Covers project understanding, scope, timeline, pricing presentation, and terms. Works for web development, consulting, trades, professional services, and any B2B service engagement. Triggers: proposal, quote, project proposal, client proposal, scope of work, SOW, engagement letter.
Use when researching an unfamiliar domain or preparing a research article. Not for quick lookups or single-file reads.
Evaluate representation and flag potential harm concerns. Use when writing characters from marginalized groups, depicting sensitive subject matter, or wanting to check for stereotypes and harmful tropes.
Build a multi-page Markdown wiki directory for a large software repository after reading and analyzing the whole codebase. Use when the agent is asked to create repository wiki documentation, onboarding docs, architecture guides, codebase tours, maintainer handbooks, or deep explanations of modules, core code paths, algorithms, design decisions, tradeoffs, tests, tooling, and operations for code learners or new maintainers. Optimized for large repositories with hundreds of thousands of lines of code where maintainers need broad coverage and deep subsystem documentation. Also supports optional Rspress/static documentation site setup when the user explicitly asks to publish or deploy the generated wiki. Supports Markdown output with Mermaid, Graphviz, and KaTeX where useful.
Logic continuity check for short video scripts. Identify risk points where viewers might swipe away: logical coherence between paragraphs, information density within paragraphs, and fluency of spoken lines. After diagnosis, proactively ask if the user wants marked-up revisions by default. Trigger methods: /dbs-script-flow, /逻辑延续, "Check logic continuity", "Check if the logic is broken", "Help me check if this script flows smoothly", "Where will viewers swipe away"