381,784 Collected SKILL.md files

Explore AI Agent Skills & Claude Prompts

Discover open-source agent skills for Claude Code, Codex, ChatGPT, and any tool that uses SKILL.md.

search
expand_more
Active:
AlexYedi
Showing 12 of 19 skills
AlexYedi

eventual-consistency-mechanics

by AlexYedi
star 1

Apply eventually consistent storage correctly - reason about the inconsistency window, implement read your own writes (RYOWs), tune consistency via N/W/R quorums, use sloppy quorums + hinted handoff, reconcile via anti-entropy / Merkle trees, and resolve conflicts with last-writer-wins (and its data-loss caveat), version vectors / siblings, or CRDTs. Use when designing on Cassandra / DynamoDB / Riak / Voldemort / Cosmos DB, diagnosing stale reads or lost updates, or choosing a conflict-resolution strategy. Triggers - "stale reads", "tunable consistency", "N W R quorum", "RYOWs", "version vector", "CRDT", "last writer wins", "sloppy quorum", "hinted handoff", "Merkle tree anti-entropy", "siblings". Produces a consistency design with explicit N/W/R, conflict-resolution strategy, and operational guarantees.

navigation main article SKILL.md
schedule Updated 1 month ago
AlexYedi

data-storage-and-modeling-patterns

by AlexYedi
star 1

Apply data storage and modeling patterns: cache hierarchy, consistency paradigms (strong vs eventual), file/object/block storage, warehouse vs lake vs lakehouse, ingestion patterns (batch, streaming, CDC, snapshot vs differential), schema-on-write vs schema-on-read, dimensional modeling (Kimball star schema, Inmon 3NF, Data Vault), Slowly Changing Dimensions (SCD types 1/2/3), and distributed-query patterns (broadcast vs shuffle hash join, MapReduce). Use when designing storage layers, modeling a warehouse, choosing ingestion frequency, or evaluating a transformation approach. Triggers: "warehouse vs lake", "Kimball vs Inmon vs Data Vault", "SCD type 2", "schema on read", "CDC vs scheduled extract", "broadcast join", "data lakehouse", "Iceberg / Delta / Hudi". Produces a chosen storage architecture + data model with rationale.

navigation main article SKILL.md
schedule Updated 1 month ago
AlexYedi

consensus-and-strong-consistency

by AlexYedi
star 1

Apply strong consistency mechanisms in distributed systems - ACID transactions, two-phase commit (2PC) for cross-partition transactions and its blocking pathology, consensus algorithms (Paxos, Multi-Paxos, Raft) with terms / AppendEntries / heartbeats / quorum-based commit, linearizability vs serializability, TrueTime + commit-wait (Spanner), single-threaded per-partition execution (VoltDB), and deterministic transaction execution (Calvin / FaunaDB). Use when designing on Spanner / CockroachDB / VoltDB / etcd, picking a consensus algorithm, or diagnosing transactional behavior in a distributed DB. Triggers - "2PC", "Paxos vs Raft", "linearizability vs serializability", "TrueTime", "Spanner", "CockroachDB", "VoltDB", "etcd Raft", "ACID across partitions", "compensating action", "XA transaction". Produces a strong-consistency design with explicit algorithm choice and trade-offs.

navigation main article SKILL.md
schedule Updated 1 month ago
AlexYedi

mdm-and-federated-data-governance

by AlexYedi
star 1

Apply Master Data Management (MDM) styles (Consolidation, Registry, Centralized, Coexistence), federated governance via data contracts and policy automation, data catalog + metalake architecture, knowledge graphs for metadata, semantic layers, and access control models (ACL, RBAC, ABAC + PEP/PDP/PIP/PAP). Use when scoping MDM, choosing an MDM style, designing a data catalog, building governance automation, defining data contracts, or implementing fine-grained access control on data products. Triggers: "MDM strategy", "consolidation vs registry vs centralized vs coexistence", "data contract", "data catalog", "knowledge graph for metadata", "ABAC for data", "semantic layer for governance", "metalake". Produces a chosen MDM style + governance architecture with policy automation.

navigation main article SKILL.md
schedule Updated 1 month ago
AlexYedi

winning-by-design-sales-excellence-framework

by AlexYedi
star 1

Design GTM playbooks, customer journeys, and messaging using the Winning by Design framework. Use this skill when Alex says "WbD this", "design the playbook for [segment]", "map the customer journey for [product]", "SPICED the discovery call", "bowtie model for [motion]", or "messaging house for [offering]". Triggers on GTM design work — net-new motions, stalled playbooks, segmentation redesigns, or messaging refreshes. Applies WbD primitives (SPICED, bowtie, impact/effort, moments-that-matter) consistently across deliverables.

navigation main article SKILL.md
schedule Updated 1 month ago
AlexYedi

embedding-models-and-domain-adaptation

by AlexYedi
star 1

Choose, train, and adapt text embedding models for production. Covers SBERT vs cross-encoder tradeoffs, contrastive learning, domain adaptation via continued pretraining, few-shot classification with SetFit, and hard-negative mining. Use when building semantic search, RAG retrieval, classification with limited labels, when generic embeddings underperform on your domain, or when picking between cross-encoder and bi-encoder architectures. Triggers: "choose an embedding model", "domain-adapt our embeddings", "few-shot classification", "SetFit for X", "cross-encoder vs bi-encoder", "embedding fine-tuning", "hard negatives". Produces concrete embedding strategy.

navigation main article SKILL.md
schedule Updated 1 month ago
AlexYedi

ai-build-vs-buy-and-model-adaptation

by AlexYedi
star 1

Make strategic AI decisions: build vs buy vs hybrid, fine-tuning vs RAG vs grounding, synthetic vs real-world data. Use when scoping a new AI capability and deciding whether to develop in-house or use a third-party model, when choosing how to adapt a foundation model to your domain, when planning a data strategy where labeled real-world data is scarce, or when evaluating whether AI is even the right tool for a given problem. Triggers: "should we build or buy this?", "fine-tune or use RAG?", "do we need fine-tuning here?", "should we use synthetic data?", "is AI actually the right tool here?", "is this an Innovator's Dilemma situation?". Produces a structured decision rationale covering core-competency assessment, resource check, model adaptation choice, and data strategy.

navigation main article SKILL.md
schedule Updated 1 month ago
AlexYedi

content-correspondent

by AlexYedi
star 1

Post-event content and outreach sequencing for NYC AI/tech events. Use this skill any time Alex mentions attending an event, returning from an event, or wants to follow up after one — even casually ("just got back from a founder session", "I'm at PMF x AI tonight", "need to write something about last night"). Also triggers for: drafting LinkedIn posts from event observations, classifying contacts from an event, writing follow-up DMs after meeting someone, building a content sequence from field notes, or converting Wispr/Granola notes into outreach and posts. Also use when Alex asks about post-event strategy or how to turn room conversations into content. For reviewing how posts or outreach performed after the fact, use the event-signal-tracker skill instead.

navigation main article SKILL.md
schedule Updated 17 days ago
AlexYedi

content-correspondent

by AlexYedi
star 1

Post-event content and outreach sequencing for NYC AI/tech events. Use this skill any time Alex mentions attending an event, returning from an event, or wants to follow up after one — even casually ("just got back from a founder session", "I'm at PMF x AI tonight", "need to write something about last night"). Also triggers for: drafting LinkedIn posts from event observations, classifying contacts from an event, writing follow-up DMs after meeting someone, building a content sequence from field notes, or converting Wispr/Granola notes into outreach and posts. Also use when Alex asks about post-event strategy or how to turn room conversations into content. For reviewing how posts or outreach performed after the fact, use the event-signal-tracker skill instead.

navigation main article SKILL.md
schedule Updated 2 months ago
AlexYedi

content-correspondent

by AlexYedi
star 1

Post-event content and outreach sequencing for NYC AI/tech events. Use this skill any time Alex mentions attending an event, returning from an event, or wants to follow up after one — even casually ("just got back from a founder session", "I'm at PMF x AI tonight", "need to write something about last night"). Also triggers for: drafting LinkedIn posts from event observations, classifying contacts from an event, writing follow-up DMs after meeting someone, building a content sequence from field notes, or converting Wispr/Granola notes into outreach and posts. Also use when Alex asks about post-event strategy or how to turn room conversations into content. For reviewing how posts or outreach performed after the fact, use the event-signal-tracker skill instead.

navigation main article SKILL.md
schedule Updated 2 months ago
AlexYedi

jtbd-fundamentals-and-interviewing

by AlexYedi
star 1

Apply Jobs-to-be-Done (JTBD) theory and the canonical interview techniques: Jobs Interviews, Switch Interviews (Bob Moesta), Inverted Switch (cancellation), Customer Case Research (CCR), the Four Forces of Progress (Push, Pull, Anxiety, Habit), the Switch Timeline (six phases), the Milkshake Marketing reframe. Use when scoping customer research, designing interview protocols, understanding why customers switch (or don't), uncovering unarticulated needs, separating jobs from solutions. Triggers: "JTBD interviews", "Switch technique", "Bob Moesta", "why did they switch", "cancellation interview", "Four Forces of Progress", "milkshake reframe", "jobs vs solutions", "uncover unarticulated needs". Produces an interview protocol + analysis approach.

navigation main article SKILL.md
schedule Updated 1 month ago
AlexYedi

the-challenger-sale

by AlexYedi
star 1

Run deals, pipeline, and messaging through The Challenger Sale framework — Teach, Tailor, Take Control; Commercial Teaching 6-step pitch; the 4 Rules; SAFE-BOLD audit; Mobilizer identification; Take Control scripts. Use this skill when Alex says "Challenger this", "Challenger pitch for [account]", "reframe the [problem] for [persona]", "commercial insight for [vertical]", "who's the Mobilizer on [account]", "Mobilizer check on [contact]", "am I talking to a Talker", "teach-tailor-take-control on [deal]", "build the reframe slide", "rational drowning on [buyer]", "I'm getting along too well with [contact]", "I need to challenge this buyer's thinking", "is my pitch BOLD or SAFE", "SAFE-BOLD audit", "what's the insight that leads to us", "foil check", "my champion is a Talker", "how do I take control of [deal]", "teaching pitch for [exec]", "score my reframe", or "rebuild the pitch". Triggers when deals are pleasant but not progressing, when the buyer is comfortable in status quo, when category education is requ

navigation main article SKILL.md
schedule Updated 1 month ago
Page 1 of 2

Browse Agent Skills by Occupation

23 major groups · 867 SOC occupations

Browse by Category

Explore agent skills organized by their primary use case

SKILLMD / CREATORS AND OCCUPATION CATEGORIES

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.

SEO KNOWLEDGE HUB & TECHNICAL OVERVIEW

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.

8 QUESTIONS

Frequently Asked Questions

A practical guide to agent skills: what they are, how to inspect them, and how SkillMD helps you explore the ecosystem.