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...
claude-plugin-structure-check
by dEitY719Audit a claude-plugin marketplace repo (e.g. `claude-plugin-visuals`) against the standard directory layout and report PASS/WARN/FAIL/N/A. Supports both `mono` (`plugins/<p>/skills/`) and `single` (repo-root `skills/`) layouts — auto-detected, or forced with `--single` / `--mono`. Read-only — never edits. Discovers plugins/skills dynamically by directory scan, then evaluates mandatory items M1-M6 (FAIL) and recommended items R1-R5 (WARN). Use when the user says "check my claude-plugin repo structure", "is this marketplace repo standard?", "audit plugin layout", "/claude-plugin:structure-check". Sister skills: `claude-plugin:structure-refactor` (fixes what this finds), `claude-plugin:rename-repo` (renames the repo to the team convention). Do NOT use for SKILL.md content quality (use `skill:check`) or shell scripts (use `sh:check`).
claude-plugin-structure-refactor
by dEitY719Fix a claude-plugin marketplace repo's directory structure toward the standard layout. Dry-run by default (plan only, no writes); `--apply` performs changes. Scope `--mp`/`--mandatory` fixes mandatory items M1-M6 only (create dirs, `git mv`, minimal marketplace.json/plugin.json skeletons); `--op`/`--recommended` adds recommended R1-R5 fixes (empty placeholder stubs + naming correction + README link backfill). Idempotent. Supports both `mono` (`plugins/<p>/skills/`) and `single` (repo-root `skills/`) layouts — auto-detected, or forced with `--single` / `--mono`; it fixes toward the detected mode's golden layout and never converts single↔mono (that is an out-of-scope, guarded no-op). Use when the user says "fix my claude-plugin repo structure", "make this marketplace repo standard", "/claude-plugin:structure-refactor". Sister skills: `claude-plugin:structure-check` (finds what this fixes), `claude-plugin:rename-repo` (renames the repo to the team convention). Under `--op`, R1 guides are generated by delegating
devx-exception-merge-checklist
by dEitY719Run a 10-point read-only sanity check on a GitHub PR right before a merge on the "exception track" (CI green but hand-merged with extra scrutiny). Detects hidden regressions that ordinary CI gates miss: mid-rebase broken commits, OpenAPI lock drift, YAML indent breakage, over-scoped prettier writes, and missing test mocks for new framework calls (`cookies()` / `headers()` / `new NextRequest(`). Use when the user runs /devx:exception-merge-checklist, /devx-exception-merge-checklist, or asks "예외 트랙 머지 전 점검", "PR 머지 직전 회귀 체크", "exception PR pre-merge audit". Read-only by default; `--auto-fix` only stages C8 / C9 fixes (no commit). Accepts `[<PR#>] [--skip-bisect] [--auto-fix] [--build-cmd <cmd>]` and `-h`/`--help`/`help`.
devx-ai-context
by dEitY719Single entry point for AI context-injection files (CLAUDE.md, AGENTS.md, GEMINI.md). Replaces five deprecated skills: agents-md:check / agents-md:create / agents-md:refactor / claude-md-check / claude-md-create. Use when the user says "check my AGENTS.md", "audit CLAUDE.md", "create AI context file", "refactor my context doc", "/devx:ai-context", "/devx-ai-context", or any request that touches a CLAUDE.md / AGENTS.md / GEMINI.md file. First positional arg is the action: check (default) | create | refactor | help. Use --file PATH for a non-standard target and --type TYPE to force the adapter (agents / claude / gemini). Do NOT use for SKILL.md (use skill:check) or for shell scripts (use sh:check).
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.