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...
ae-g2-business-scenarios
by jiangqiang1996填补 G1(约束)与 G4(数据模型)之间的功能需求缺口,提取业务场景、定义操作序列、发现字段、标注跨场景依赖。当 G1 产物就绪且需要系统化梳理业务场景时使用。
ae-g3-architecture
by jiangqiang1996覆盖系统架构设计和安全设计,为下游 G4/A1/L2 提供技术决策上下文。当 G1+G2 产物就绪且需要确定架构风格、技术栈、通信模式、认证授权、数据保护和威胁建模时使用。
ae-g4-data-model
by jiangqiang1996从不变量和业务场景推导实体、字段、关系、约束和状态机,确保每条不变量在数据模型中有对应约束。当 G1+G2+G3 产物就绪且需要定义数据模型时使用。DDL 禁止 FOREIGN KEY,引用用逻辑软约束替代。
ae-g1-invariants
by jiangqiang1996从目标描述中提取业务不变量、划定系统边界、识别模块拆分点、记录待澄清项。当用户说"提取不变量""划定边界""G1""不变量分析"时使用。本技能是流程首步,没有上游产物,输入为用户直接提供的目标或场景描述而非需求文档。
ae-a2-assoc-trace
by jiangqiang1996用具体数据走通跨模块数据流,验证契约自洽、数据流可达、冲突解决有效。适用于 G5 单模块推演已完成、需要验证跨模块数据一致性的场景。
ae-a1-contracts
by jiangqiang1996定义模块间的数据契约、数据流、共享状态和冲突解决策略,确保跨模块协作有据可依。当上游 G1/G2/G3/G4/G5 产物就绪后,需要梳理跨模块依赖并建立契约体系时使用。
ae-g5-global-trace
by jiangqiang1996全局数据推演:用测试数据代入数据模型和状态机,走通核心业务流程,验证不变量在全局范围内成立。依赖 G1、G2、G3、G4 产物(只读),输出推演场景、测试数据、推演记录和覆盖率报告。
ae-save-experience
by jiangqiang1996统一经验沉淀入口:先保存 solution,再按需提炼 rules
ae-l1-ui-spec
by jiangqiang1996基于上游产物生成结构化界面文档描述,定义视图、布局、数据绑定、交互行为、状态显示与校验规则,并执行可还原性验证。仅当系统有图形界面时执行;纯后端/CLI/嵌入式系统跳过本步。
ae-v2-completeness
by jiangqiang1996V2 完整性回溯:逐条不变量追踪从声明到实现的证据链,识别断裂、遗漏和未覆盖项,确保每条不变量有完整闭环
ae-l3-module-verify
by jiangqiang1996验证指定模块内部设计的数据推演通过、DDL 可落地、文档可还原性达标。必须通过 module=<模块名> 指定目标模块,每次调用只处理一个模块。
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.