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...
raven-research-looped-reasoning-eval
by daemon-blockint-techScaffold a research-grade experiment that tests whether a Looped / Recurrent-Depth Transformer (RDT) is better than a parameter-matched vanilla transformer at vulnerability discovery, when both are continued-pretrained on a security corpus. Use when the user says "test the looped-transformer hypothesis", "run the OpenMythos RDT experiment", "compare loop count to trial budget", "does inference-time loops help security reasoning", or asks for a reproducible research pipeline around the Mythos architecture hypothesis. The skill scaffolds the experiment — it does NOT make claims about Mythos itself, and it explicitly bins OpenMythos as a community speculative reconstruction, not Anthropic's actual model.
talent-acquisition
by daemon-blockint-techExpert talent acquisition for end-to-end recruiting operations—workforce planning tie-in, requisition intake, job descriptions and leveling, interview process coordination, candidate experience, offer process coordination, ATS/CRM workflow, hiring manager partnership, recruiting metrics (time-to-fill, pass-through, diversity funnel), agency/RPO management, EVP in hiring, onboarding handoff, and hiring compliance awareness (not legal advice). Use when the user mentions talent acquisition, TA strategy, recruiting process, hiring process, requisition, job description, time to fill, interview loop, candidate experience, ATS workflow, hiring manager, offer process, recruiting metrics, RPO, or full-cycle recruiting—not passive sourcing only (talent-sourcer), interview question banks alone (interview-prep, interview-system-designer), comp modeling (comp-analysis), offer letter legal text (draft-offer), org-wide people strategy (chro-advisor), or employee HR onboarding (people-operations-specialist).
senior-data-center-capacity-delivery-manager
by daemon-blockint-techGuides delivery of data center capacity increments—MW/kW and rack-ready halls on schedule: capacity delivery plans, critical path (power, cooling, construction, network), vendor and contractor coordination, readiness gates, handoff to operations and compute install, and program RAID across concurrent capacity projects. Use when executing an approved capacity build or expansion, tracking MW/rack delivery milestones, unblocking construction or MEP dependencies, or reporting capacity-at-risk to steering—not for portfolio prioritization (data-center-portfolio-planning-execution-lead), single-hall MEP design (data-center-design-execution-lead), utilization or GPU supply (data-center-compute-supply-efficiency), or generic software programs (technical-program-manager). On-site rack-and-stack and smart-hands: field-services-engineer.
network-pentester
by daemon-blockint-techGuides authorized network and infrastructure penetration testing—scoping and rules of engagement, external and internal network assessments, host and service enumeration, vulnerability validation on network services, Active Directory attack paths within scope, lateral movement documentation, segmentation testing, wireless assessment methodology (high level), evidence and remediation reporting, and retest. Emphasizes written authorization and safe boundaries. Use for network pentest, internal pentest, external pentest, AD assessment, lateral movement testing, port scan methodology when authorized—not OWASP web/API testing (web-pentester), cross-domain pentest orchestration when network is one workstream (penetration-tester), LLM/agent adversarial testing (ai-redteam), enterprise adversary simulation or purple-team campaigns (red-team-specialist), SOC triage (soc-analyst), incident command (incident-responder), or cloud guardrail implementation (cloud-security-engineer).
web-pentester
by daemon-blockint-techGuides authorized web application and API security testing—scoping and rules of engagement, OWASP-oriented testing (injection, auth/session, access control, SSRF, XSS, CSRF, business logic), REST and GraphQL API security, Burp/ZAP-style manual methodology without requiring commercial tools, evidence and remediation reporting, and retest validation. Emphasizes written authorization and safe boundaries. Use for web pentest, OWASP web assessment, web app security test, API pentest, Burp-style testing, XSS or SQL injection testing when authorized—not network/AD/infra pentest (network-pentester), general multi-domain pentest orchestration (penetration-tester), LLM or agent adversarial testing (ai-redteam), enterprise adversary simulation or purple-team campaigns (red-team-specialist), SOC alert triage (soc-analyst), incident command (incident-responder), or CI/CD security gates and SBOM programs (devsecops).
product-infrastructure-security-engineer
by daemon-blockint-techGuides product infrastructure security—securing the runtime, data plane, and control plane that ships with the product: multi-tenant isolation, service-to-service auth, customer data boundaries, secure defaults in APIs and workers, abuse-resistant rate limits, product-scoped secrets and encryption, and security design reviews for product infra changes. Use when threat-modeling product features, designing tenant isolation, hardening service mesh or internal APIs, reviewing product IaC/modules for data leaks, defining secure baselines for microservices the product team owns, or partnering on incidents affecting customer workloads—not for corporate IdP/SIEM (information-security-engineer), CI pipeline gates only (devsecops), SOC operations (defensive-security-analyst), authorized pentest execution (offensive-security-analyst), general IDP golden paths (platform-engineer), company-wide GRC (cybersecurity), or applied AI solution architecture for LLM features (applied-ai-architect-commercial-enterprise).
deal-operations-administrator
by daemon-blockint-techGuides deal operations administration—quote-to-cash coordination, deal desk intake and routing, CRM opportunity hygiene, order form and SOW assembly, approval workflows, signature tracking, and handoffs to legal, finance, and provisioning after customer signature. Use when processing a sales deal, preparing order paperwork, running deal desk checklist, fixing CRM stage/fields, coordinating signatures, or closing the loop post-signature—not for contract legal redlines (commercial-counsel), board or equity approvals (corporate-counsel), ASC 606 accounting (senior-revenue-accountant), support tickets after go-live (customer-ops-specialist), or M&A/financing closing (transaction-manager).
communication-lead
by daemon-blockint-techGuides communications leadership—messaging strategy, narrative and key-message development, stakeholder and executive comms cadence, internal announcements (all-hands, change, crisis), external customer and partner messaging, launch and incident communication plans, channel selection, approval workflows, and spokesperson/Q&A prep. Use when planning org-wide comms, drafting executive or company-wide messages, aligning narratives across teams, designing change or crisis communications, or preparing launch announcements—not for management consulting deliverables (business-consultant), API/docs/runbooks (tech-writer-researcher), on-call/paging/SEV program design (incident-management-engineer), single-ticket customer replies (support-engineer), exec/community escalation program (community-executive-escalations-program-manager), developer training programs (developer-education-lead), or legal contract language (commercial-counsel).
actuarial-analyst
by daemon-blockint-techGuides hands-on actuarial analyst work for insurance, reinsurance, and pension—reserving and loss development (IBNR, triangles, chain-ladder diagnostics), pricing and rate indication support (experience, trend, credibility, basic GLM at spec level), data validation and model I/O review, reporting packs and workpapers, assumption application under actuary direction, and statutory tie-outs at analyst depth. Use when the user mentions actuarial analyst, loss development, IBNR, reserve analysis, rate indication, pricing support, actuarial workpaper, triangle analysis, credibility, experience study, actuarial reporting, or reserve roll-forward—not actuary sign-off (actuary), consulting engagements (actuarial-consulting), assumption governance (assumption-setting), ALM strategy (asset-liability-management), P&C legal depth (property-casualty-insurance), charts only (data-visualization), or ETL-only pipelines (data-scrubbing).
actuarial-consulting
by daemon-blockint-techGuides actuarial consulting engagements—client scoping and SOW design, stakeholder communication (CFO, risk, boards, regulators at overview level), due diligence and M&A actuarial support, reserving/pricing/capital review programs, model validation and opinion support, regulatory interaction prep, and deliverable governance (memos, exhibits, management presentations). Use when the user mentions actuarial consulting, actuarial engagement, reserve opinion, due diligence actuarial, model validation engagement, actuarial memo, SOW actuarial, regulatory actuarial, M&A reserves, or actuarial review—not deep technical modeling execution (actuary), P&C line education only (property-casualty-insurance), legal advice (commercial-counsel), or generic management consulting without actuarial lens (business-consultant).
actuary
by daemon-blockint-techGuides actuarial work for insurance and reinsurance—pricing and rate adequacy, reserving and IBNR, loss development and triangles, mortality/morbidity and lapse assumptions, experience studies and credibility, capital and risk metrics at overview level, product design tradeoffs (life, health, P&C, annuity), and regulatory reporting concepts (NAIC, IFRS 17, Solvency II overview—not legal advice). Use when the user mentions actuary, actuarial, IBNR, loss development, reserve analysis, mortality table, pricing insurance, experience study, IFRS 17, loss ratio, combined ratio, credibility, or asks for assumption documentation and model governance for insurance products—not generic FP&A (financial-analyst), investment banking valuation (comps-analysis, dcf-model), legal policy interpretation (commercial-counsel), clinical trials, software-only implementation (senior-software-engineer), or broad GRC without actuarial models (compliance-engineer).
advanced-long-term-actuarial-mathematics
by daemon-blockint-techGuides advanced long-term actuarial mathematics (SOA ALTAM)—survival models, life insurance and annuity APVs, premiums and reserves (equivalence principle, Thiele), multiple decrement and Markov states, yield-curve discounting, mortality improvement, longevity risk, profit testing, and mortality graduation. Tool-agnostic, concept-first. Use when the user mentions advanced long-term actuarial mathematics, ALTAM, survival model, life insurance reserve, annuity valuation, equivalence principle, Thiele equation, multiple decrement, force of mortality, longevity risk, mortality improvement, actuarial present value, or net premium reserve—not ASTAM/P&C (advanced-short-term-actuarial-mathematics), workpapers only (actuarial-analyst), appointed actuary (appointed-chief-actuary), assumption governance (assumption-setting), ALM detail (asset-liability-management), or exam-only deliverables.
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.