2 226 document skills from 443 authors. They read and assemble documents, spreadsheets and slide decks. Half of them fit into 1 834 tokens or less — that is what one costs your context window when the agent loads it. 567 ship runnable scripts rather than instructions alone. 24 of them cannot work without an MCP server, most often rube. We also found 384 copies of these same skills sitting in other people's repositories — counted once here, not 384 times.
2 226 unique 443 authors 1 276 updated this month 156 from vendors
Converts a PRD markdown file into GitHub Issues (parent + sub-issues) for ralph-github-start-loop to execute. Use when user wants to push PRD stories to GitHub Issues.
Converts a PRD or plan markdown file into prd.json format for ralph-json-start-loop to execute autonomously. Use when user wants to convert a PRD or plan to JSON stories.
Author first-class wiki pages (ADRs, specs, file docs, notes) that live alongside Cortex memory. Use when the user says 'this is an ADR', 'document this decision', 'write an ADR', 'add a spec', 'spec this out', 'document this file', 'add a note about', 'link these pages', 'bookmark this as a spec', or when finalizing a design decision that should persist as a human-readable document.
Publish and manage LinkedIn content via the Hyper MCP — text posts, article / link previews, document and PDF posts, organization (company page) posts, and AI-generated text-to-carousel posts. Use when the user wants to post on LinkedIn, share an article on LinkedIn, post to a LinkedIn company page, upload a PDF / document to LinkedIn, or build a LinkedIn carousel from text.
Generate a blameless incident postmortem from the current or recent SRE Agent investigation. Use after an incident is resolved, when asked for a postmortem, RCA report, incident review, or lessons learned document.
Build, adapt, and document apps that run inside Sealos Desktop using the Sealos app SDK. Use when creating a new Sealos app, integrating an existing web app into Sealos Desktop, wiring Sealos session data into business features, preparing local iframe-based debugging, or producing beginner-friendly Sealos app tutorials and starter implementations. Also triggers on "/sealos-app-builder".
Reviewing legal documents for Terms of Service, Privacy Policy, and Tokushoho compliance. Detects clause gaps, flags risks, and aligns regulatory requirements. Don't use when legal advice is needed — consult a lawyer.
Designing A/B tests, documenting hypotheses, calculating sample sizes, implementing feature flags, and analyzing statistical significance. Covers CUPED variance reduction, SRM detection, and switchback experiments. Use when hypothesis validation is needed.
Converting document formats (Markdown/Word/Excel/PDF/HTML). Converts specs from Scribe and reports from Harvest into distributable formats; generates reusable conversion scripts. Use when converting documents, building accessibility-compliant PDFs, or creating Pandoc/LibreOffice pipelines.
Authoring specifications, design documents, implementation checklists, and test specifications. Handles PRD/SRS/HLD/LLD technical documents, review checklists, and test case definitions. Does not write code. Use when technical documentation is needed.
Channeling the documented thinking of named notable figures (an 'itako' medium) — applies their mental models, heuristics, and decision-style to your problem as advisory lenses. Don't use for decisions/verdicts (Magi), synthetic user personas (Cast), or fixed founder-mentor coaching (Sage).
Converting repository changes into detailed learning documents. Use when turning diffs into teaching materials, recording design decisions, or creating onboarding materials for new members.
Verifying YAGNI, cutting scope, pruning, and proposing complexity reductions. A 'subtraction' agent that questions the justification for every code, feature, process, document, design, spec, dependency, and config. Does not write code.
Design stable, versioned, self-documenting APIs. Easy to use correctly, hard to use incorrectly. Apply Hyrum's Law from day one.
Document decisions, not just implementations. ADRs for architectural choices, inline docs for non-obvious code, and runbooks for operational knowledge.
Incremental LLM-friendly wiki generator for Obsidian note vaults. Use when: (1) Building wiki from notes, (2) Ingesting notes to wiki, (3) Obsidian LLM wiki, (4) Incremental knowledge base management. Triggers: 'build wiki from notes', 'ingest notes to wiki', 'Obsidian LLM wiki', 'incremental knowledge base'.
Создание схем и диаграмм в Excalidraw для Obsidian. Use when user says 'сделай схему', 'нарисуй диаграмму', 'excalidraw', 'схема в obsidian', 'визуализация'.
Методолог агента - знает архитектуру агента, создаёт инструкции для платной группы premium community (Agent Starter Kit, AI-OPS серия). Используй при создании ЛЮБОГО учебного контента: PDF, MD, инструкций, гайдов для подписчиков. Триггеры: 'AI-OPS', 'starter kit', 'инструкция', 'контент для группы', 'материал для операционки', 'учебный документ'.
> Review and improve an existing BP outline, PPTX, PDF, or rendered slide set across investment logic, evidence, copy, charts, and visual quality. Produces a scored report, page-level revisions, and targeted regeneration instructions while keeping facts separate from assumptions. Trigger on "润色 BP", "审稿商业计划书", "PPT 不专业", "逐页检查", "改图表", "BP review", "polish pitch deck", or "audit investor deck".
> Convert Markdown documents to professionally styled DOCX (Word) files with python-docx. Handles CJK/Latin mixed text, fenced code blocks, tables, blockquotes, cover pages, TOC field, watermarks, and page numbers. Supports multiple color themes matching any2pdf (Warm Academic, Nord, GitHub Light, etc.) and is battle-tested for Chinese technical reports. Use this skill whenever the user wants to turn a .md file into a styled Word document, generate an editable report from markdown, or create a DOCX from markdown content — especially if CJK characters, code blocks, or tables are involved. Also trigger when the user mentions "markdown to docx", "md2docx", "any2docx", "md转word", "md转docx", "生成word", or asks for an "editable document" from markdown source.
> source-backed outline, PPTX/PDF production, or evidence/content/visual polishing. Use when the user wants to create a business plan end to end, combine BP stages, continue from an existing BP workspace, or is unsure which BP skill to use. Trigger on "做 BP", "完整商业计划书", "融资 PPT 全流程", "BP skill kit", "business plan workflow", "pitch deck pipeline", or "continue my BP".
> Turn an approved investor BP outline into a clean, professional slide deck with deliberate style selection, real product evidence, charts, branding, PPTX/PDF, and a full-deck preview. Use when the narrative already exists and the user wants PPT production, visual style exploration, slide regeneration, or export. Trigger on "把 BP 大纲做成 PPT", "选择 BP 风格", "生成融资 PPT", "重做第几页", "BP deck", "pitch deck design", "render investor slides", or "export BP PDF".
> pandoc + XeLaTeX (better table handling, LaTeX-quality typesetting). Handles CJK/Latin mixed text, fenced code blocks, tables, blockquotes, Obsidian callouts, inline images, emoji fallback, LaTeX-style formulas, clickable TOC, watermarks, headers/footers, and page numbers. Supports multiple color themes and is battle-tested for Chinese technical reports. Trigger when user mentions "markdown to PDF", "md2pdf", "any2pdf", "md转pdf", "报告生成", "导出pdf", or wants a professionally formatted PDF from markdown.
> Generate professional slide deck images from content (Markdown, text, URLs). Creates outlines with style instructions, then generates individual slide images. Supports 16 visual styles, CJK/Latin mixed text, branding overlays, and PPTX/PDF export. Use when the user asks to "create slides", "make a presentation", "generate deck", "slide deck", "PPT", "做PPT", "生成幻灯片", "制作演示文稿", or wants to turn content into a visual slide deck.
> 为文档原地插入 AI 配图。读取文档后全局规划插入点,并行生成所有图片, 异步插回原文。支持封面图、自定义比例和三种风格。 generate images、document images、为文章加图。
> Fill in Word document form templates (.docx) with user-provided data. Reads a template containing tables with label→value cell pairs, detects all fillable fields, and outputs a completed document. Handles CJK/Latin mixed text with proper font switching. Use this skill when the user wants to fill in a form template, complete an application form, populate a Word table form, or automate document filling. Also trigger when the user mentions "填表", "填写表格", "fill form", "fill template", "表格填写", "申请表", "登记表", or has a .docx template with blank fields to fill.
> Fill web forms by fetching form fields from a URL, deep-searching the user's local knowledge base for relevant info, and generating a markdown document with all answers pre-filled. Use when the user provides a URL to a web form (conference application, speaker submission, event registration, profile form) and wants help filling it out from their existing materials. Also trigger when the user mentions "填网页表", "fill web form", "网页填表", "表单填写", "申请表填写", "conference application", "speaker submission", "讲师申请", "报名表", or provides a URL with "form", "feedback", "apply", "register", "submit" in the path.
> Convert PDF files to a single vertically concatenated PNG image using macOS native CoreGraphics. Each page is rendered at 2x scale and stitched top-to-bottom. ~20x faster than pdftoppm+ImageMagick, zero external dependencies on macOS. Trigger when the user mentions "pdf to png", "pdf转png", "PDF转图片", "pdf拼接", "pdf截图", "convert pdf to image", or wants to turn a multi-page PDF into one long PNG.
Generate complete business proposals for client projects. Takes client requirement documents (docx/pdf/md) or verbal descriptions as input, outputs a professionally formatted proposal with technical architecture, budget, timeline, risk analysis, and team introduction. Automatically calls illustrate for images and any2pdf for final PDF delivery. Trigger when user mentions "商务方案", "合作评估", "项目评估", "报价方案", "proposal", "需求评估", "给客户出方案", or wants to generate a client-facing project proposal from requirements.
> 专业合同分析、审阅、批注与红线修订。用于用户要求审查合同、协议、条款、NDA、采购或服务合同、SaaS 或数据协议、劳动或顾问协议、知识产权许可、投融资文件,或要求风险分析、逐条批注、修订模式、谈判建议、审阅报告时;支持 DOCX 原位批注和修订,以及 PDF、图片或纯文本的定位审阅。
Adaptive conversion of LaTeX, PDF, or Markdown sources into a complete Word .docx that follows a user-supplied .docx template. Use when pandoc --reference-doc alone is not enough — for thesis, dissertation, report, or institutional Word formatting that needs cover pages, declarations, TOC, heading numbering, captions, three-line tables, equations, citations, and visual verification.
> MSA, Service Order, SOW, SLA, NDA, waiver, DPA, or BAA; triaging a contract a client or vendor sends; assessing legal risk on a deal; or answering "what document do we need for this client". negotiation playbook and document map, the organization-specific positions those skills ask for. Also trigger on "is this enforceable", "what should our contract say", "the client wants to change a clause", or any mention of liability caps, indemnification, non-solicits, or contract terms for an IT services business. Apply alongside msp-brand (naming and voice), msp-pricing (any term or number a client could see), and msp-sales (how legal terms land in the sales conversation).
> Use this skill whenever generating ANY document, marketing material, email, proposal, slide deck, or other customer- or internal-facing content for your MSP, so that naming, visual style, and voice stay consistent. Triggers include any request to create, write, design, or format content "for us", "for my MSP", "on brand", "branded", or anything that will carry the company's name, decks, social posts, letterhead, email signatures, or web copy (content and voice only; site build and hosting is msp-website-setup). Always load this skill before producing branded output, and apply it alongside content skills like msp-sales, msp-marketing, msp-pricing, docx, and pptx.
URL content extraction. Use for fetching any URL - webpages, articles, PDFs, JavaScript-heavy sites. Token-efficient: runs in forked context. Prefer over built-in WebFetch.
Manage RSS/Atom feed subscriptions and refresh them into the Tapestry knowledge base. Use when the user wants to list, add, remove, or refresh subscribed feed sources by name rather than by URL.
Expose the organized knowledge base through a readable frontend experience. Use when a user wants to browse the knowledge base visually as a lightweight site instead of reading raw Markdown files directly. Supports building viewers for specific data paths (e.g., individual books) or the entire knowledge base.
Export knowledge base content to PDF, Markdown, or HTML files saved under _data/exports/. Use when a user wants to save or share KB content as downloadable files. Supports exporting a single document file, a single feed entry, a single note, or the entire knowledge base.
AI-native web intelligence workflow for crawling, organizing, and synthesizing web content from multiple platforms (Zhihu, Reddit, HN, X/Twitter, Xiaohongshu, Weibo). Use when users share URLs, want to archive web content, build knowledge bases, or analyze online discussions.
Generate professional visual note cards (视觉笔记卡片/信息图) from knowledge base content as single-page HTML infographics with PNG export. Use when users want to create visual summaries, knowledge cards, infographics, or poster-style visualizations of topics from the knowledge base.
Create, improve, or audit README.md documents for GitHub projects. Use only when the user explicitly asks for a README, README quality/readability, README accuracy, or README examples. Do not use for full docs sites, API-reference-only work, general repo launch/readiness audits, topics/homepage metadata, or broad repository review.
Use when starting a new feature, gathering requirements for an unfamiliar domain, refining a vague idea into actionable scope, or when a user request is ambiguous or underspecified. Conducts SAM Stage 1 discovery — structured requirements gathering through user discussion, asking WHO/WHAT/WHEN/WHY and never HOW. Produces the ARTIFACT:DISCOVERY document containing feature requirements, NFRs, goals, anti-goals, references, and resolved questions. Supports backlog item self-initialization via a #N argument.
Autonomous feature research and gap analysis. Use when starting /add-new-feature or analyzing existing architecture documents. Explores codebase patterns, identifies ambiguities, and produces feature-context-{slug}.md for orchestrator RT-ICA phase. Does NOT make technical decisions.
Comprehensive guide for creating and managing MkDocs documentation projects with Material theme. Includes official CLI command reference with complete parameters and arguments, and mkdocs.yml configuration reference with all available settings and valid values. Use when working with MkDocs projects including site initialization, mkdocs.yml configuration, Material theme customization, plugin integration, or building static documentation sites from Markdown files.
Converts user-facing documentation (how-to guides, tutorials, API references, examples) in any format — Markdown, PDF, DOCX, PPTX, XLSX, AsciiDoc, RST, HTML, Jupyter notebooks, man pages, TOML/YAML/JSON configs, and plain text — into Claude Code skill directories with SKILL.md plus thematically grouped references/*.md files. Use when given a docs directory or mixed-format documentation to transform into an AI skill. Uses MCP file-reader server for binary formats.
Builds end-to-end document processing pipelines using LandingAI ADE. Covers batch and async processing, classify-then-extract workflows for mixed document types, RAG pipelines with vector DB ingestion, database integration (Snowflake, CSV, DataFrames), visualization (bounding box overlays, cropped chunk images, word-level annotation), and Streamlit UIs. Use when composing ADE parse/extract/split operations into multi-step pipelines, processing document batches in parallel, loading extraction results into databases, or visualizing/annotating extracted content. Complements the document-extraction skill (which covers single ADE SDK operations); use when those operations need to be chained into workflows or when word-level grounding, bounding box visualization, or annotation is required.
Parses, extracts, and classifies documents using LandingAI's Agentic Document Extraction (ADE). Covers the v2 APIs powered by DPT-3 (Parse and Extract, sync and async jobs with service tiers, hierarchical block structure, Markdown ranges, normalized bounding boxes) and the v1 APIs (page classification with Classify, table of contents generation with Section, schema generation with Build Extract Schema, document splitting with Split, plus v1 Parse and Extract for Office formats and password-protected files). Use when parsing documents into structured Markdown, extracting fields with a JSON Schema or Pydantic model, classifying pages or splitting mixed document batches, generating a table of contents, processing large files asynchronously, migrating from ADE v1 to v2, or when the user mentions blocks, chunks, grounding, bounding boxes, ranges, spans, or highlighting where data appears in a document.
> here.now lets agents publish websites and store private files in cloud Drives. Use Sites to publish HTML, documents, images, PDFs, videos, and static files to live URLs at {slug}.here.now or custom domains. Use Drives as private cloud folders where agents can store files (documents, context, memory, plans, assets, media, research, code, etc), share them with other agents, and continue across sessions and tools. Use when asked to "publish this", "host this", "deploy this", "share this on the web", "make a website", "put this online", "create a webpage", "generate a URL", "build a chatbot", "save this to my Drive", "store this for later", "write this to cloud storage", "share a folder with another agent", or "use my here.now Drive".
Draft a goal+rider document pair to brief the next agentic turn on a project. Two documents — a ≤4000-char goal (the spine) and an unbounded rider (the prescriptive detail with eleven phases and depth-tests-first discipline). Run when user says "draft a goal", "new goal", "write a goal+rider", "goal+rider for the next agentic turn", "rider for X", or anything in the shape of "brief the next agent on Y".