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...
upgrade-v1-35-0
by microbus-ioCalled by upgrade-microbus. Upgrades the project from v1.34.x to v1.35.0. Removes the Microbus clock-shift mechanism (svc.Now, frame.ClockShift family, Microbus-Clock-Shift header), introduces the workflow.FlowOutcome return shape for Snapshot/Await/Run and the OnFlowStopped event payload, moves the flow status constants from foremanapi to the workflow package (foremanapi.StatusCompleted -> workflow.StatusCompleted, etc.), adds a reason argument to foremanapi.Cancel, adds a trailing *workflow.FlowOptions argument to foremanapi.Fork and foremanapi.Continue, captures the new nextCursor return from foremanapi.List, renames the foreman's Prometheus metrics under microbus_flows_* / microbus_steps_* / microbus_task_* prefixes with shorter attribute labels, and migrates every sequel microservice from the old sequel.Open/OpenTesting (now renamed OpenSingleton/OpenSingletonTesting) to the explicit two-step pattern: CreateTestingDatabase resolves the per-test DSN in TESTING, then OpenSingleton opens the pool.
upgrade-v1-36-0
by microbus-ioCalled by upgrade-microbus. Upgrades the project from v1.35.x to v1.36.0. Removes graph.DeclareInputs / graph.DeclareOutputs and workflow.FilterState (subgraph boundaries are now pass-through). Workflow authors who need narrower contracts at a subgraph boundary bracket the subgraph with Before<NodeName> / After<NodeName> adapter tasks using the new flow.Delete / flow.Clear / flow.Keep / flow.Transform primitives (see .claude/rules/workflows.txt for the convention).
upgrade-v1-32-0
by microbus-ioCalled by upgrade-microbus. Upgrades the project from v1.31.x to v1.32.0. Deletes the removed workflow.Graph.SetTimeBudget (per-task time budgets are now declared on the task endpoint via the new sub.TimeBudget option), renames the foreman DefaultTimeBudget config to TimeBudget, adds a trailing *workflow.FlowOptions argument to foreman Create and Run (priority/fairness), and regenerates manifests and mocks (which now carry a "DO NOT EDIT" marker).
add-config
by microbus-ioTRIGGER when user asks to add or modify a configuration property or setting, or to make a value configurable. Affects intermediate.go, manifest.yaml. Do NOT manually define configs - this skill wires up getter, setter, and validation.
add-function
by microbus-ioTRIGGER when user asks to add, create, or modify an API endpoint, function, or RPC. Also when adding a route that accepts typed arguments and returns typed results. Affects intermediate.go, *api/client.go, mock.go, manifest.yaml.
add-inbound-event
by microbus-ioTRIGGER when user asks to listen for, subscribe to, or handle an event from another microservice. Wires up the event sink handler. Affects intermediate.go, mock.go, manifest.yaml.
add-metric
by microbus-ioTRIGGER when user asks to add or modify a metric, counter, gauge, or histogram, or to track/measure an operation. Affects intermediate.go, manifest.yaml. Do NOT manually define metrics - this skill wires up recorders and OpenTelemetry names.
add-microservice
by microbus-ioTRIGGER when user asks to create, scaffold, or initialize a new microservice. Creates the full directory structure including service.go, intermediate.go, client.go, mock.go, manifest.yaml, and test scaffolding.
add-outbound-event
by microbus-ioTRIGGER when user asks to fire, emit, or publish an event that other services can subscribe to. Creates event trigger and hook in *api/client.go. Affects intermediate.go, manifest.yaml.
add-task
by microbus-ioTRIGGER when user asks to add a workflow step, agent step, agentic task, task endpoint, or workflow phase. "Agent step" and "workflow step" are interchangeable - a task is a single step of a workflow / agent / agentic workflow, regardless of whether the surrounding workflow calls an LLM. Tasks are handlers that read/write shared state via workflow.Flow. Affects intermediate.go, *api/client.go, mock.go, manifest.yaml.
add-ticker
by microbus-ioTRIGGER when user asks to add a recurring job, periodic task, scheduled operation, or ticker. Affects intermediate.go, mock.go, manifest.yaml. Do NOT manually wire up tickers.
add-web
by microbus-ioTRIGGER when user asks to add or modify a web handler, HTML page, file download, or raw HTTP endpoint. Use for endpoints that work with http.ResponseWriter/http.Request. Affects intermediate.go, *api/client.go, mock.go, manifest.yaml.
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.