Building Custom AI Skills
Building custom AI skills is the practice of packaging reusable capabilities so that AI agents can perform specialized tasks reliably. A skill is a directory containing a SKILL.md file that contains organized folders of instructions, scripts, and resources that give agents additional capabilities[^c1] — more precisely, a folder whose YAML frontmatter carries a name and a description, followed by Markdown instructions, that an agent discovers at startup and loads only when a task matches[^c11]. The format is governed by a small, open specification with strict field constraints — the name is capped at 64 lowercase alphanumeric and hyphen characters[^c23], and the description at 1,024 characters — so a skill is defined as precisely as a package manifest. Skills are the application layer of a broader stack: models reason, tools act, and skills encode the procedure that decides which actions to take and in what order. Because capabilities can be added without retraining, skills have become an important mechanism for capability development and distribution[^c8], and the format has spread across vendors faster than almost any prior agent standard: in under nine months agent skills went from a single product feature to a cross-vendor standard with dozens of compatible platforms and millions of published skills[^c6].
The foundations of that stack are function calling and retrieval. Function calling lets a model request that an application execute a named operation, returning a structured result that the model incorporates into its response, while retrieval-augmented generation grounds outputs in external knowledge through embeddings and vector search. The Model Context Protocol standardizes tool access across hosts, so that an agent can discover capabilities at runtime — it calls the tool listing, sees what is available, and decides which tools to invoke autonomously[^c2] — rather than relying on hardcoded integrations. MCP has become the near-universal standard for connecting models to tools and data, with thousands of public servers in production use[^c7], and monthly downloads of its official SDKs passed 400 million during 2026[^c19]. The protocol itself reached a milestone revision in 2026 that transformed it from a bidirectional stateful protocol into a request-and-response stateless one[^c12], making MCP servers deployable on ordinary web infrastructure at scale. It now sits alongside the Agent Skills standard under neutral foundation governance, and the skills extension that carries skills over MCP reached Final status with a complete reference implementation[^c16].
Skills themselves are governed by a design discipline. Progressive disclosure — the core principle that makes agent skills flexible and scalable[^c3] — keeps only a skill's name and description resident until a task matches, so a library can grow without consuming the model's attention budget on every request. The economics of that choice are exact: reading a skill costs nothing that persists, keeping one costs a folder in the repository, and only firing unprompted costs the prompt[^c10]. Authoring practice converges on a small set of habits: keep skills focused, write descriptions that trigger reliably, keep references shallow, and build evaluation suites that compare output with and without the skill. A newer research direction treats the library as something that maintains itself: systems that evolve skills from real interactions, and curated libraries that retrieve the right skill rather than merely accumulating them — curated retrieval raised measured skill-benchmark performance to 22.6%, while dumping in a raw crawl of hundreds of thousands of skills performed almost as badly as no skills at all[^c21]. Agents are also beginning to author their own tools, with research showing that a model can learn to build tools, refine them, and share proven ones across model sizes[^c24].
The ecosystem's central lesson is that reach is not quality. Distribution is solved — skills are now published through plugins that bundle connectors and instructions into a single installable unit[^c17], and the same manifest format is used across vendors, including by companies publishing first-party skills in a competitor's format[^c18] — but many public skills are weak or unsafe, and the catch is quality variance[^c9]. The risk is measurable: a large-scale security study of tens of thousands of published skills found that roughly a quarter contained at least one vulnerability, spanning prompt injection, data exfiltration, privilege escalation, and supply-chain patterns[^c13], which places skill vetting alongside dependency review as a production concern. Marketplace operators have responded with safety-scanned submission portals and reviewed directories[^c14], but open community catalogs remain largely unaudited.
Above the protocols sit frameworks and platforms that structure multi-step work. Frameworks range from graph-based orchestration to role-based agent teams and conversational multi-agent collaboration, and they are increasingly complemented by hosted platforms that supply managed runtimes, memory, retrieval, identity, and observability, together with marketplaces and directories through which reviewed connectors and skills are distributed. The infrastructure market also split during 2026 between usage-metered services and flat-price subscriptions that bundle compute, tools, and security, a change framed as betting that predictable pricing matters as much as architectural parity[^c22]. Selection and economics cut across all of it. Benchmark fragmentation means no single model or framework dominates — see [[Model Selection and Comparison]] for frontier and open-weight families, pricing, and context windows — and the durable finding is that orchestration choice matters less than the quality of the context agents reason over[^c4]. Cost behaves the same way: because output tokens are the dominant cost driver on almost every workload[^c5], caching, routing, context trimming, and local-versus-cloud execution matter as much as model choice, and automated optimization against a held-out evaluation can cut cost while improving quality — one documented loop moved a support agent to a smaller model at low effort, scoring higher at a fraction of the cost per ticket[^c15]. Evaluation, guardrails, security, and deployment round out the lifecycle, because a skill that cannot be tested, constrained, or rolled back safely is not production-ready.