Agent Skills Are Not Fancy Prompts — They Are a Routing Protocol and a Compiler for Context
As agent frameworks mature, the bottleneck shifts from "can the model do X" to "can the model do X the same way every time, on demand, without burning a 16k-token context window." Skills provide the packaging, routing, and evaluation infrastructure to make that repeatable, which is the difference between a chat demo and a production agent that a team can actually maintain.
A Skill is a reusable capability package that bundles a professional's process for a complex task into a standardized folder. Its SKILL.md file uses YAML frontmatter for routing — the description field is a gateway matching condition, not ad copy — and a body that defines the workflow, output template, failure paths, and resource pointers. This structure enables progressive disclosure: metadata is always visible, the body loads on trigger, and bundled scripts or references load on demand, cutting token costs by up to 8x compared to stuffing everything into a system prompt.
Building a Skill follows an engineering lifecycle from intent capture through drafting, trial runs with real samples, and codifying hard logic into scripts, to designing eval sets and running with-skill vs. baseline comparisons. Evaluation spans five layers: trigger accuracy, process adherence, output assertions, cost, and regression. Trigger engineering specifically tackles undertrigger (the skill is not loaded when it should be) and overtrigger (it loads when it shouldn't) by tuning the description with synonyms, colloquial triggers, and precise intent verbs.
Governance treats Skills as version-controlled code assets with a production checklist covering single responsibility, routing clarity, executable workflows, failure handling, and automated assertions. Quality metrics like trigger precision/recall, human rewrite rate, and assertion pass rate feed a dashboard. The anti-pattern catalog warns against prompt relocation, universal skills, missing failure paths, and overfitting to three demo samples. The end state is a capability tree where Skills Engineering sits alongside LLM, Memory, Tool, RAG, and MCP as a first-class Agent element.
Framing the description as a routing rule rather than documentation is a genuinely useful mental model shift: it forces the author to think about matching conditions, synonyms, and false-positive triggers the way an API gateway designer would.
The 8x token savings claim from progressive disclosure is concrete and measurable, but the real leverage is that it makes Skills composable — you can have dozens of them without degrading the agent's performance on unrelated tasks.
Treating Skills as code assets with a governance checklist and quality dashboard is where most agent projects will stall. The anti-pattern catalog is effectively a pre-mortem for teams that treat Skills as glorified prompt libraries.
The five-layer evaluation framework (trigger, process, result, cost, regression) mirrors mature software testing pyramids and suggests that agent reliability engineering will become its own sub-discipline.
Positioning Skills as the element that turns an LLM from a generalist into a 'virtual job employee' clarifies why Tool, RAG, and Memory alone are insufficient — they provide capability but not professional judgment about how to combine them.