Document Claude Skills
2 253 document skills from 443 authors. They read and assemble documents, spreadsheets and slide decks. Half of them fit into 1 829 tokens or less — that is what one costs your context window when the agent loads it. 571 ship runnable scripts rather than instructions alone. 24 of them cannot work without an MCP server, most often rube. We also found 422 copies of these same skills sitting in other people's repositories — counted once here, not 422 times.
2 253 unique 443 authors 2 updated this month 183 from vendors
Create a new specification through an adaptive interview process with proactive recommendations and optional research. Use when user says "create spec", "new spec", "generate spec", or wants to start a specification document.
Documentation management workflow for MkDocs sites and standalone markdown files — initialize, generate, update docs, and create change summaries.
Generate a markdown report documenting codebase changes from the current session — files added, modified, deleted, and a summary of what was done.
>- Documentation management workflow for MkDocs sites and standalone markdown files — initialize, generate, update docs, and create change summaries. Use when asked to "create docs", "write README", "update documentation", "generate docs site", "write CONTRIBUTING", "manage documentation", or "docs changelog".
>- Generate a markdown report documenting codebase changes from the current session — files added, modified, deleted, and a summary of what was done. Use when asked to "document changes", "generate change report", "save changes report", "what did I change", "session report", "summarize my changes", or "write a changes report".
>- Documentation management workflow for MkDocs sites and standalone markdown files -- initialize, generate, update docs, and create change summaries. Use when asked to "create docs", "write README", "update documentation", "generate docs site", "write CONTRIBUTING", "manage documentation", or "docs changelog".
>- Generate a markdown report documenting codebase changes from the current session -- files added, modified, deleted, and a summary of what was done. Use when asked to "document changes", "generate change report", "save changes report", "what did I change", "session report", "summarize my changes", or "write a changes report".
>- Documentation management workflow for MkDocs sites and standalone markdown files — initialize, generate, update docs, and create change summaries. Use when asked to "create docs", "write README", "update documentation", "generate docs site", "write CONTRIBUTING", "manage documentation", or "docs changelog".
>- Generate a markdown report documenting codebase changes from the current session — files added, modified, deleted, and a summary of what was done. Use when asked to "document changes", "generate change report", "save changes report", "what did I change", "session report", "summarize my changes", or "write a changes report".
>- Documentation management workflow for MkDocs sites and standalone markdown files — initialize, generate, update docs, and create change summaries. Use when asked to "create docs", "write README", "update documentation", "generate docs site", "write CONTRIBUTING", "manage documentation", or "docs changelog".
>- Generate a markdown report documenting codebase changes from the current session — files added, modified, deleted, and a summary of what was done. Use when asked to "document changes", "generate change report", "save changes report", "what did I change", "session report", "summarize my changes", or "write a changes report".
Use when designing a new feature or system, making architecture decisions, writing technical design docs, or structuring project documentation. Triggers on "design", "architecture", "technical design", "ADR", "system decomposition", "how should I structure this", "设计方案", "架构设计", "技术方案", "文档体系", "写 User Story", "写文档". Also use when reviewing existing architecture docs or asking "where should I put this doc?
Professional User Story and documentation system construction. Assists in writing high-quality User Story documents through guided interviews to uncover requirements context and acceptance criteria, and places documents precisely in the standardized docs directory structure. Triggers when the user requests writing User Stories, describing feature requirements, or initializing project documentation structure.
Hand-tune a project's `.claude/` directory by cherry-picking ECC (everything-claude-code) rules/skills/agents and generating project-specific rules based on the project's real intelligence layers (GitNexus, MemoryMaster, graphify, Obsidian wiki, existing CLAUDE.md). Run preflight intelligence builds for layers that don't exist yet. Run in any project to curate or re-curate its `.claude/` directory. Use when asked to "curate this project", "cherry-pick rules for this repo", "/project-curate", or when a project's `.claude/` is bloated with mass-installed noise or missing stack-specific rules.
Converts scattered meeting data (recordings, handwritten notes, diagrams, digital notes, supplementary documents) into a structured MS Word deliverable with summary, decisions, action items, open questions, and follow-up message. Use when the user mentions meeting notes, meeting summary, meeting minutes, action items from meeting, meeting documentation, or needs to consolidate meeting materials.
Publish HTML/Markdown design documents on GitLab Pages with selection-driven discussion. Reviewers select any text in the published doc; a floating 💬 bubble opens a prefilled GitLab Issue (title + anchor link + selection quote + label) in a new tab. GitLab handles auth via the user's existing session — no OAuth, no PAT, no API calls. Works on gitlab.com, self-hosted, and proxy-fronted GitLab.
Migrate Quip documents to GitLab Wiki with full content preservation. Use when converting Quip docs to wiki, migrating documentation, or setting up GitLab wiki from Quip sources.
> Use when adding or editing Auth0 guidance in this repo's single auth0 skill — a new framework, feature, tooling, or pattern reference — to get the file structure, router wiring, and validation right the first time. Use even if the request just says "add a reference" or "document X in the skill" without naming the router.
>- Generates a structured Project Brief — a comprehensive markdown document that extracts goals, architecture, knowledge file inventory, Custom Instructions summary, Memory contents, current state, ecosystem position, and key decisions from a Claude Project. Briefs serve as uploadable context source Project's purpose, architecture, and progress. Use when user says "create a brief," "brief this project," "extract project context," "generate a project summary for another project," "I need to share this project's context," "prepare this project for cross-project reference," or "document this project." Also use when the user is preparing to work across Projects and needs portable context. Do NOT use for session handoffs, project audits, or Memory optimization (use rootnode-session-handoff, rootnode-project-audit, or rootnode-memory-optimization respectively, if available).
Automate the grunt work of making research presentations — discovers experiments from git/output folders, collects images and metrics, and organizes them into slides. Creates a slide-by-slide script for user approval, then generates slide markdown and editable PPTX.
Extract the actual core loop from a game, feature set, or pitch based on repeated player actions, feedback, rewards, and renewed motivation. Use when a team can list mechanics but cannot clearly articulate the repeatable loop that drives engagement, when a pitch sounds like disconnected features, when a design document lacks loop clarity, or when you need to test whether the claimed loop is coherent, rewarding, and structurally complete.
Create a concise one-page game design document and export it as both markdown and PDF. Use when a user wants a one-page design doc, one-pager, pitchable design summary, or compact game concept sheet that captures identity, pillars, summary, features, interface, aesthetic direction, sound, audience, platform, and milestone plan on a single page.
Extract a structured list of rules from all markdown files at the top level of a skill directory. Use this skill whenever you need to parse rules out of a skill for conflict checking, merging, or diffing.
> Generalised autonomous optimisation loop — soft RLVR for any artifact a user can project-pack, none. Never assumes subprocess access or unrestricted local files. Use this skill whenever a user wants to iteratively improve an artifact — code, prompts, documents, configs, designs, content — by running structured experiments, evaluating results against a multi-dimensional rubric, and learning good", "run experiments on", "autoresearch", "iterate on this overnight", "try different approaches and pick the best", or any request implying repeated evaluate-and-improve cycles.
> Generalised autonomous optimisation loop — soft RLVR for any artifact a user can measure. Use this skill whenever a user wants to iteratively improve an artifact — code, prompts, documents, configs, designs, content — by running structured experiments, evaluating results against a multi-dimensional rubric, and learning good", "run experiments on", "autoresearch", "iterate on this overnight", "try different approaches and pick the best", or any request implying repeated evaluate-and-improve cycles. Also use when the user wants to improve a system prompt, a data pipeline, a writing style, or any artifact where quality can be decomposed into measurable tracks. For inference optimisation tasks (model latency, throughput, quantization, GPU deployment), a* delegates the low-level tuning to AITune while maintaining quality tracking and learning.
Apply Google Style documentation standards to Python, Go, TypeScript, and Terraform code. Use when writing or reviewing code that needs docstrings/comments/JSDoc, when asked to "document this code", "add docstrings", "follow Google Style", or when improving code documentation quality. Supports Python docstrings, Go comments, TypeScript JSDoc, and Terraform variable/output descriptions. Enforces consistent, professional documentation standards.
Generates a complete, polished HTML documentation page, a processing checklist, an AstroBin post JSON, a PixInsight process icon set (XPSM), AND a ready-to-paste PixInsight project Description field for a deep-sky object (DSO) astrophotography project. Use this skill whenever the user mentions astrophotography, a DSO name (NGC, IC, Messier, Sharpless, etc.), wants to document an imaging session, mentions PixInsight project documentation, wants to create an observation report, or asks to generate a page/document for a nebula, galaxy, cluster, or other deep-sky target. Triggers on phrases like "create doc for NGC XXXX", "generate DSO page", "document my session on", "make a PixInsight doc for", "astro documentation page", "pixinsight project description", "description field pixinsight", "processing checklist", "workflow checklist", "astrobin", "astrobin post", "astrobin upload", "process icons", "xpsm", "pixinsight icons". Always use this skill — not a generic HTML generator — when the subject is a deep-sky object.
Generate comprehensive, professional project documentation structures including README, ARCHITECTURE, USER_GUIDE, DEVELOPER_GUIDE, and CONTRIBUTING files. Use when the user requests project documentation creation, asks to "document a project", needs standard documentation files, or wants to set up docs for a new repository. Adapts to Python/Go projects and OpenSource/internal contexts.
Use this skill for any task involving Thai government letters, official correspondence, formal petitions, authorization letters, leave requests, or ราชการ forms. Trigger whenever the user asks to: write หนังสือราชการ, draft a คำร้อง, write an authorization (หนังสือมอบอำนาจ), submit a leave form (ใบลา), petition a government agency, or write a formal letter to a Thai official. Also trigger for requests like "เขียนหนังสือราชการ", "ยื่นเรื่อง", "คำร้อง", "หนังสือถึงราชการ", "ทำหนังสือถึง", "ใบลา", "หนังสือมอบอำนาจ", "official Thai letter", or any formal ราชการ document task.
Automates Microsoft PowerPoint via JXA with AppleScript dictionary discovery. Use when asked to "automate PowerPoint presentations", "create slides programmatically", "JXA PowerPoint scripting", or "export PowerPoint to PDF". Covers presentations, slides, shapes, text, tables, export enums, and interop with Excel.
Automates Apple Pages using JXA with AppleScript dictionary discovery. Use when asked to "automate Pages documents", "create documents programmatically", "JXA Pages scripting", or "export Pages to PDF". Covers documents, templates, text, styles, export, tables, images, and AppleScript bridge fallbacks.
Automates Microsoft Word via JXA with AppleScript dictionary discovery. Use when asked to "automate Word documents", "find and replace in Word", "JXA Word scripting", or "create Word documents programmatically". Covers documents, ranges, find/replace, tables, export, and ObjC bridge patterns.
将用户已授权账号中的抖音视频收藏或用户明确指定的喜欢列表配置并同步到本地 Markdown 或 Obsidian 知识库；默认收藏，只有用户明确说喜欢/点赞才切换来源。首次明确选择推荐的百炼转录、本地 Whisper 或不转录。不得绕过登录、访问他人账号或泄露 Cookie 与私密数据。
| Inspect, build, and verify Office documents (PPTX, DOCX, XLSX) using the oxen CLI. (3) Previewing slide/document/sheet content in terminal, (4) Extracting text or data, (5) Verifying build results, (6) User asks about ".pptx", ".docx", ".xlsx" inspection or generation.
| Create and modify PowerPoint presentations (PPTX) through direct XML manipulation. (3) Inserting images or custom shapes, (4) Applying POTX templates for consistent branding, (5) Editing existing PPTX files, (6) Working with slide layouts and placeholders, (7) User asks to make a "presentation", "slides", "deck", or mentions ".pptx". Supports all 11 standard Office slide layouts.
> Audit the reasoning of any document or argument — a memo, proposal, investment analysis, board paper, article, or the user's own draft — and fallacies, and what would falsify it, with every finding anchored to exact quoted text. Runs a commit-first coaching loop that asks for the user's own judgment before revealing the audit, tracks their recurring blind spots in a persistent reasoning profile, and turns every audit into a rep that sharpens the user's thinking instead of replacing it. Use this skill whenever the user wants reasoning examined — "audit this argument", "is this analysis sound", "poke holes in this proposal", "review the logic of my draft", "what's wrong with this reasoning" — in any language (e.g. Vietnamese "phản biện giúp tôi", "soi lập luận này", "tài liệu này có lỗ hổng gì", "đánh giá đề xuất này giúp tôi", "góp ý bản nháp của tôi"; Spanish "analiza los argumentos de esta propuesta"; Chinese "帮我审一下这份提案的论证"; Japanese "この提案の論理をチェックして"; French "analyse les failles de ce raisonnement"), even when they never say "critical thinking". Also trigger when the user drops a document and asks whether to trust or act on it, or asks to see their thinking progress / reasoning profile. (Company-level strategic bets with a full analysis belong to strategy-board; learning a new topic through dialogue belongs to socratic-questor — this skill leads when the question is whether a specific piece of reasoning holds up, and it is the daily-driver for document-level judgment calls.)
>- Deep-read long books and papers using Mortimer Adler's inspectional / analytical / syntopical method, the Recite step from SQ3R, and S. Keshav's three-pass method for papers, with page-anchored notes as external memory so the agent never has to load the whole text into one context window. Use this skill whenever the user asks to read, study, summarize, analyze, review, or answer questions about a long book, textbook, PDF, EPUB, thesis, dissertation, survey paper, or any document of roughly 50+ pages. Also use it when a `<slug>-notes/` workspace from a previous session already sits next to a source file and the user asks a follow-up question about that book — search the existing notes before re-reading anything. Trigger on these requests in whatever language the user writes them — for example Vietnamese "đọc sách", "tóm tắt sách", "phân tích luận án", or equivalent phrasing in any other language. Do not use this skill for short documents (under ~30 pages) that fit comfortably in context — read those directly instead; the pipeline is overhead they don't need.
>- Write, restructure, classify, and review documentation using the Diataxis framework. Use this skill whenever the user asks to create, improve, audit, or reorganize docs, documentation, knowledge bases, help centers, onboarding guides, internal process docs, manuals, runbooks, product docs, API/developer docs, tutorials, how-to guides, references, or explanations. Also use it when the user mentions Diataxis, tutorial, how-to, reference, explanation, docs taxonomy, documentation architecture, or asks why a document feels confusing. Do not use it for marketing copy, legal contracts, fiction, sales proposals, press releases, or persuasion-first writing unless the user explicitly wants a Diataxis-style documentation analysis.
>- Build interactive presentation websites — slide decks projected to a room, controlled by one presenter. Use this skill WHENEVER the user wants to create, build, or design a presentation, slide deck, talk, or "bài thuyết trình / slide / trình chiếu", and also when they ask to add/edit slides, restyle a deck, scaffold a new presentation project, reuse their presentation setup in another repo, or export slides to PDF — even if they don't say the word "slide" but clearly need projected talk visuals (e.g. "I'm giving a talk next week and need visuals", "dựng deck cho buổi chia sẻ", "làm mấy trang chiếu project. Do NOT use it for printable documents, normal web apps, or dashboards meant for individual users to interact with.
> Socratic questioning partner named Gadfly for deep learning through dialogue. Use this skill when the user wants to learn, understand, or explore a topic through questions rather than explanations. Trigger when the user says "teach me about...", "help me understand...", "I want to learn...", "ask me questions about...", "quiz me", "Socratic method", "Gadfly", or wants to deeply understand something through dialogue rather than passive reading. Also trigger when the user provides a text or document and wants to be questioned about it, or wants to check their own understanding of a concept.
> Ingest documents at scale into Amazon OpenSearch using OpenSearch Ingestion Service (OSIS) pipelines. Upload pre-generated JSONL chunks to S3 and OSIS indexes them — optionally using semantic_enrichment in the sink to create the index with ASE automatically. Cloud ingestion — uploading raw PDF/DOCX and letting document_extractor parse them in the cloud — is available via private beta. Use this skill when the user wants to ingest documents into a cloud OpenSearch domain or collection, process documents at full volume beyond local limits, or set up an OSIS pipeline. Activate even if the user says OSIS, ingestion pipeline, document extraction, S3 ingestion, managed ingestion, or cloud processing.
> Process unstructured documents into search-ready chunks. Use this skill when the user wants to process PDFs or unstructured documents into JSONL chunks using Docling. Activate even if the user says document processing, chunking, Docling, PDF processing, or chunk quality evaluation. For cloud-scale ingestion via OSIS pipelines, see cloud/managed-ingestion-service.
> Process unstructured documents (PDF, DOCX, PPTX, XLSX) into search-ready JSONL chunks using Docling. Runs locally — no AWS or cloud services needed. Use this skill when the user wants to prepare documents for indexing, chunk documents, evaluate chunk quality, or convert PDFs to searchable text. Activate even if the user says process documents, chunk my files, prepare for search, or Docling.
> Build search applications and query log analytics data with OpenSearch. Use this skill when the user mentions OpenSearch, search app, index setup, search architecture, semantic search, vector search, hybrid search, BM25, dense vector, sparse vector, agentic search, RAG, embeddings, KNN, PDF ingestion, document processing, or any related search topic. Also use for log analytics and observability — when the user wants to set up log ingestion, query logs with PPL, analyze error patterns, set up index lifecycle policies, investigate traces, or check stack health. Activate even if the user says log analysis, Fluent Bit, Fluentd, Logstash, syslog, traceId, OpenTelemetry, or log analytics without mentioning OpenSearch.
> Build search applications with OpenSearch. Use this skill when the user mentions search app, index setup, search architecture, semantic search, vector search, hybrid search, BM25, dense vector, sparse vector, agentic search, RAG, embeddings, KNN, PDF ingestion, document processing, search quality evaluation, or any related search topic.
> Build search applications with OpenSearch from scratch. Use this skill when the user mentions search app, index setup, search architecture, semantic search, vector search, hybrid search, BM25, dense vector, sparse vector, agentic search, RAG, embeddings, KNN, PDF ingestion, document processing, or any related search topic. Activate even if the user says search quality, evaluation, nDCG, precision, relevance tuning, or search builder without mentioning OpenSearch.
Cadrer un projet par questionnement structuré et produire ou étendre `docs/PRD.md` selon un template fixe en 8 sections (Problème, Solution, Utilisateur cible, User Stories, Critères de succès, Hors périmètre, Décisions d'implémentation, Notes complémentaires). Utilise sur /cadre, "cadre ce projet", "écris le PRD", "fais-moi un PRD", "crée le PRD", "produis le PRD", "étends le PRD", ou dès qu'il faut formaliser le cadrage d'un projet dans un document versionné. Pair naturel de /interroge (amont) et /planifie (aval).
Configure a repository for Atelier's development workflow. Use only when explicitly invoked; inspect existing guidance, issue-tracker and domain-document conventions, preview the proposed configuration, and write only after approval. It does not install Atelier or initialize external tooling.