Explore AI Agent Skills & Claude Prompts
Discover open-source agent skills for Claude Code, Codex, ChatGPT, and any tool that uses SKILL.md.
Enter through keywords, occupations, creators, and GitHub sources to see what kinds of skills are emerging across domains.
Use the same catalog through the API
Connect 381,784 public skills to your own search, analytics, or agent workflow with the REST API.
Querying local SQLite index...
dl-databook-charts
by jaminatorRestores the standardized chart inventory (nine charts on HistFin Charts / NWC / Seasonality) on an Overland deal Databook (.xlsx) whose charts were gutted into empty shells by an openpyxl save. Use when the user asks to "restore the Databook charts" or "fix the charts" after dl-databook-financials populates the workbook — and again after every dl-databook-kpi call. Extracts a deterministic chart-spec manifest from the bundled blank template (the live OOXML, never guessed), then transplants the template's own chart/drawing/style parts into the populated vS workbook at the zip level, leaving the sheet-name-qualified source ranges to drive Excel's recomputation on open — gated by a machine-verified preservation gate (exactly the standardized inventory restored; every other part identical to the input; idempotent). Not for borrower-specific operational pie charts (out of scope), not for chart data population, not for other workbooks.
dl-memo-prescreen
by jaminatorBuilds the multi-slide IC Pre-Screen Memo (.pptx) for Pre-Screen IC (P7) by populating the bundled deck template from the deal's upstream artifacts — the populated Databook, Overland Model, databook narrative, DD-list returns, posting memo, and posting-IC debrief. Use when a deal is heading to Pre-Screen IC and the user asks to "build the pre-screen memo," "populate the IC deck," "draft the IC memo," or to build or update a specific memo section or slide range. Two-turn workflow: scans the deck and confirms scope with the user (Turn 1), then executes a preservation-gated build (Turn 2). Runs in the Claude PowerPoint Add-in (active deck) and Claude Desktop (uploaded or cloned template). Internal-only RESTRICTED deliverable.
dl-databook-narrative
by jaminatorSynthesizes a structured MD&A-style narrative (markdown + JSON) from the populated P6 analytical workbooks (Databook vS + Overland Model vS) plus optional management commentary. Use at P6 after dl-databook-financials / -charts / -kpi / -model when the user asks to "write the databook narrative," "synthesize the MD&A," or "summarize what the workbooks say." Eight catalog categories; every item carries a verifiable workbook-cell, manifest-field, or commentary-excerpt basis (anti-fabrication); unions every upstream escalation, [INSUFFICIENT DATA] marker, tie miss, and validation-cross-check escalation into one severity-classified data-gap list. Feeds dl-ddq-initial and dl-memo-prescreen. Internal-only CONFIDENTIAL; reads no RESTRICTED input; the draft banner is the literal first line of the markdown.
dl-ddq-initial
by jaminatorPopulates the Wells & Overland DD List one-pager (.docx) in [Initial] mode: a ruthlessly prioritized, exactly-one-page Initial DD list of diligence questions and data requests, reconciled against the deal folder AND the upstream P6 analytical workbooks. Use after a posting-IC decision when the user asks to prepare or build the Initial DD list / P6 data-request list. Unions the posting memo, IC debrief punchlist, any kick-off list, AND the dl-databook-narrative output (severity-filtered); applies the IC dispositions (rejected→kill, added→new, qualified→amend); reconciles received vs. outstanding via the M365 connector (degrading to document index); orders to the Overland credit framework; drafts gap-aware evidence-backed questions whose basis stays internal; edits the bundled template in place via populate_dd_list.py with the two-stage one-page discipline. Outbound co-lender-shared (CONFIDENTIAL); reads RESTRICTED debrief + CONFIDENTIAL narrative; emits internal data of neither.
dl-databook-model
by jaminatorPopulates the Overland Model template's three case blocks (Sponsor Base / Overland Flat / Overland Downside) atomically in one call from the populated Databook anchors plus per-case forecast drivers extracted via the defensively-degrading project / chat / MSFT 365 cascade with deterministic basis-detection (CA-EBITDA vs Reported vs escalate) and bridge-apply translation. Use at P6 Initial DD after dl-databook-financials. Writes only the contracted driver cells (Sponsor Base dollars at rows 10/21/33/36/39/42/45/48/51/56 cols V-AB; Flat % drivers row 11 cols AJ-AN; Downside template-preset by default) plus static-state anchors; the model's formula machinery stays value-identical. The machine-verified preservation check runs in memory before any file write. Internal-only CONFIDENTIAL; never outbound.
dl-databook-financials
by jaminatorPopulates the SUCAP and FinInputs tabs of the Overland deal Databook (.xlsx) from a deal's financial source set (QoE, audited/management financials, reporting packages, compliance certificates, Posting Memo Backup, posting memo, IC debrief) under a strict openpyxl formula-protection write-gate: resolves the period grid from the SUCAP anchors, applies backwards-from-most-recent restatement precedence, classifies reclass/diligence/pro-forma, and ties CA EBITDA to the QoE control total via a plan-validate-execute workflow. Off by default behind one self-verified structure pre-pass: per-business-unit scaffold tabs rolling up to FinInputs, off-quarter marketed LTM, and in-workbook QoE staging (a bridge-shaped QoEInputs scaffold derived from the single QoE). Template bundled in assets/. Activate to build/populate the Databook SUCAP/FinInputs tabs for P6 diligence; not for the Posting Memo Backup (use dl-memo-posting-backup), general Excel tasks, or the other eight Databook sheets.
dl-utility-project-context
by jaminatorPopulates the deal-context slot of any Direct Lending Underwriting Library phase project instruction for a specific company and emits the fully-populated PI as a clean markdown block the teammate can paste into Claude Desktop's project instructions field. Three modes — Fresh-start for a new project; Refresh when deal state has moved within the same phase (new VDR wave, QoE roll-forward, posting-IC outcome, structure update); Roll-forward when the deal advances to the next phase (Stage 1→2, 2→3-P5, 3-P5→3-P6, 3-P6→3-P7, 3-P7→3-P8). Auto-detects current phase + company by scanning the project's already-attached PI before asking the teammate to confirm mode. Runs a reverse defensively-degrading cascade (Microsoft 365 connector SharePoint scan first → chat attachments → project attachments → user) to source every field; preserves teammate-supplied carryover values across refreshes and roll-forwards; emits a field-level diff in the cascade-trace footer; never fabricates a value the cascade cannot resolve.
dl-databook-comps
by jaminatorBuilds the PublicComps and TnxComps tabs of the Overland deal Databook from a connector cascade. Public comps via FMP then Pitchbook then S&P CIQ then web (MSCI/LSEG, Yahoo, SEC/Edgar) - US-listed, mcap >$100M, in borrower GICS sub-industry, 10-20 names target 15 SMID-weighted, filtered for negative-EBITDA / TEV-Revenue>10x / TEV-EBITDA>35x with relaxation clause for the 10-name floor. Precedents via Pitchbook then web, web-enriched, AND-filtered for TEV-Revenue>10x AND TEV-EBITDA>35x, 10-20 names. Builds a 5-year historical TEV/EBITDA chart with four series (equal-weighted time series + flat average + flat plus/minus sigma bands) per Nathan-Yau viz discipline. Writes into the Databook with formatting consistent with the workbook and layout from the PortCo Coverage Template. Optimized for Excel add-in, Claude Desktop, claude.ai. Emits modified Databook + JSON valuation_summary frozen contract consumed by dl-memo-prescreen. Activate at P6 to build Databook comps; not the legacy Comps workbook.
dl-termsheet
by jaminatorDrafts the Wells & Overland Term Sheet (Stage 3 / P8) — the joint co-lender offer externalized to the borrower — from the IC-approved term-sheet input captured at the Pre-Screen IC. Use when the user asks to draft or populate the Wells & Overland Term Sheet from a Pre-Screen IC debrief ("draft the term sheet", "P8 term sheet", "populate the term sheet from the IC debrief"). Populates the bundled .docx template in place: writes deal-specific text into the 17 term rows of the body table plus the leverage-basis footnote; every other paragraph and cell stays unchanged behind a cell-level preservation gate. Classifies each IC condition externalize or internal_only (only externalize entries enter the document body) and runs the outbound-redaction checklist per build. Draft output under a vS filename pending human review.
dl-sector-screen
by jaminatorDecomposes a sector, industry, or sub-industry into discrete sub-verticals, screens each against the Overland industry attractiveness framework, and produces a structured markdown handoff with cascade anchor companies, NAICS codes, trade orgs, and conference targets for downstream borrower identification. Use whenever the user wants to develop sourcing coverage on a sector or industry — trigger phrases include "research X sector", "screen the Y industry", "develop sourcing coverage on Z", "decompose W into sub-verticals", "what sub-verticals in Q are attractive", or any freeform sector-level sourcing question. Use this even when the user describes a sector thematically (e.g., "aging infrastructure plays", "outsourced facilities services") rather than naming it directly. Do NOT use when the user names a specific company or deal (route to borrower identification or posting memo workflows), or for sector-level work unrelated to Overland sourcing such as public equity research or general market analysis.
dl-databook-charts
by jaminatorRestores the standardized chart inventory (nine charts on HistFin Charts / NWC / Seasonality) on an Overland deal Databook (.xlsx) whose charts were gutted into empty shells by an openpyxl save. Use when the user asks to "restore the Databook charts" or "fix the charts" after dl-databook-financials populates the workbook — and again after every dl-databook-kpi call. Extracts a deterministic chart-spec manifest from the bundled blank template (the live OOXML, never guessed), then transplants the template's own chart/drawing/style parts into the populated vS workbook at the zip level, leaving the sheet-name-qualified source ranges to drive Excel's recomputation on open — gated by a machine-verified preservation gate (exactly the standardized inventory restored; every other part identical to the input; idempotent). Not for borrower-specific operational pie charts (out of scope), not for chart data population, not for other workbooks.
dl-memo-prescreen
by jaminatorBuilds the multi-slide IC Pre-Screen Memo (.pptx) for Pre-Screen IC (P7) by populating the bundled deck template from the deal's upstream artifacts — the populated Databook, Overland Model, databook narrative, DD-list returns, posting memo, and posting-IC debrief. Use when a deal is heading to Pre-Screen IC and the user asks to "build the pre-screen memo," "populate the IC deck," "draft the IC memo," or to build or update a specific memo section or slide range. Two-turn workflow: scans the deck and confirms scope with the user (Turn 1), then executes a preservation-gated build (Turn 2). Runs in the Claude PowerPoint Add-in (active deck) and Claude Desktop (uploaded or cloned template). Internal-only RESTRICTED deliverable.
Browse Agent Skills by Occupation
23 major groups · 867 SOC occupations
Browse by Category
Explore agent skills organized by their primary use case
Explore the agent skills ecosystem by occupation and creator
SkillMD is not just a keyword search box. It is an open map that organizes public skills by occupation, creator, and repository, helping you see which workflows, judgment criteria, and domain habits people are writing for AI agents.
Then follow creators and GitHub repositories back to the source: compare the skills a team maintains, whether the repo is active, and how the README frames the work before you open, install, or reuse anything.
Use it three ways: learn an unfamiliar field by occupation, study how creators organize skills, then use source context to decide what is worth opening or reusing.
01 Map a field
Browse 23 occupation groups and 867 SOC roles to learn what skills exist in adjacent domains and how they break down real work.
02 Follow creators
Use creator and repository pages to inspect maintained skill collections, recent updates, and source context before trusting a result.
03 Search with sources
Search 1.7M+ collected skills, then use occupation tags, creators, and GitHub source context to decide what is worth opening.
Start with the occupation map, then follow creators and repositories back to real code. SkillMD helps explain why a skill is worth opening, not only what it is named.
Standardizing Agent Capabilities with SKILL.md and Model Context Protocol (MCP)
In the rapidly evolving landscape of artificial intelligence, LLM agents (Large Language Model agents) have transitioned from simple text predictors to autonomous problem solvers. To orchestrate complex, multi-step agentic workflows, developers require a standardized format to specify agent capabilities, prompt instructions, system rules, and database bindings. This is where SKILL.md and the Model Context Protocol (MCP) have emerged as standard developer paradigms. SkillMD serves as the central directory for indexing, exploring, and sharing these critical agent configurations.
Our open-source registry currently tracks over 1.7 million collected SKILL.md configurations and system prompts. By compiling agent configurations from active developers on GitHub, we bridge the gap between prompt engineering research and production execution. Whether you are building agents with Anthropic's Claude Code, OpenAI's GPT-4, Google's Gemini, or local models using Ollama and LlamaIndex, standardized skill definitions ensure your agents behave predictably across different runtime environments.
What is the Model Context Protocol (MCP)?
The Model Context Protocol (MCP) is an open-source standard designed to connect LLMs to data sources, developer tools, and external environments. MCP establishes a bidirectional communication channel between client applications (like Cursor, Claude Desktop, or custom agent systems) and servers hosting data or capabilities. Standardizing instructions via SKILL.md enables LLMs to query databases, read local files, execute terminal commands, and integrate third-party APIs. SkillMD allows you to find ready-to-run MCP servers and prompt instructions for various occupations and technical tasks.
The Structure of a Professional SKILL.md File
A valid SKILL.md configuration is designed to be easily read by humans and parsed by LLMs. It contains precise system instructions, trigger conditions, required parameters, and execution examples. Below is the typical architectural blueprint of a professional agent skill:
- Metadata & Core Scope: Declares the name of the skill, author details, target models, and a description of the capability.
- Triggers & Intent Detection: Details semantic triggers that help the agent decide when to invoke this skill.
- System Prompts: Explicit system-level instructions that direct the agent's behavior, personality, safety guardrails, and formatting preferences.
- Capabilities & Tools: Lists the files, databases, or APIs the agent must access to complete the tasks.
- Few-Shot Examples: Demonstrates real inputs and outputs, helping the model generalize behavior through in-context learning.
Optimizing Agent Workflows for Modern LLMs
Writing effective agent skills requires deep knowledge of prompt engineering. With the release of advanced reasoning models like Claude 3.5 Sonnet, ChatGPT o1, and DeepSeek-V3, prompt templates must focus on structured thinking. Developers are encouraged to use XML tags (e.g., <thought>, <context>, and <rules>) to isolate execution boundaries. Standardized prompts prevent agents from suffering from context drift, ensuring that long-running tasks remain aligned with the initial system parameters.
Exploring by SOC Occupations and Creator Profiles
What makes SkillMD unique is its taxonomy. Instead of simple text search, we parse and organize files according to the Standard Occupational Classification (SOC) system. This means you can discover skills written for Computer and Mathematical roles, Business and Financial operations, Legal, Design, and and Educational Instruction fields. By tracking creator profiles, developers can study how different teams organize their custom instructions, compare version updates, and fork public configs for specialized enterprise use cases.
SkillMD operates as a high-performance index running on a fast Go backend and a highly responsive Astro SSR frontend. All search queries execute in milliseconds, featuring smart debouncing to prevent multiple API requests while keeping user data secure. Join our community of developers to standardize your AI agent instructions and optimize your LLM prompting workflows today.
Frequently Asked Questions
A practical guide to agent skills: what they are, how to inspect them, and how SkillMD helps you explore the ecosystem.