Skills replace a model's recall with the vendor's procedure

A model's knowledge of a product is an average of the web

A language model learns a product from whatever was written about it: documentation, forum answers, tutorials and blog posts, spread over several years. What it holds is an average of those sources, weighted by how often each claim was repeated. For a tool that changes often, that average lags the current version and mixes in advice that was already wrong when it was posted.

The failure mode is specific. The model doesn't flag uncertainty. It produces a fluent, confident answer in the style of the most common source, and that answer is correct for a version of the product that may no longer exist.

Skills replace recall with procedure

In Claude, the alternative is called a Skill. A Skill is a folder with written instructions in it, and optionally scripts. The instructions cover the task, the steps in order, the known failure points, and sometimes an example of good output. The model follows them instead of reconstructing the procedure from memory.

The mechanism that makes this practical is progressive disclosure. At the start of a task, only a short description of each Skill sits in the model's context window, its working memory. The full instructions load when the task matches. Context is the scarce resource, so this matters: a library of fifty Skills costs roughly fifty short descriptions, not fifty manuals.

Vendors are starting to publish them

Google now publishes an open-source library of Skills for its own products: more than a hundred, covering Google Cloud, Firebase, BigQuery, the Gemini API and the Ads API, under the Apache 2.0 license (github.com/google/skills). The direction doesn't depend on the number. The party that built the product writes the procedure, and the model executes it.

Documentation written for agents becomes a product surface

If assistants work from vendor-written procedures, the quality of those procedures becomes part of what the product is worth. Take two comparable tools, one with a current, precise procedure an agent can load and one without. The assistant will be better on the first, and the buyer will notice. Documentation for agents stops being a support-team afterthought and starts competing.

Your own procedures can be packaged the same way

Nothing here requires a vendor. A business has procedures too, such as how a client is onboarded, how the month-end pack is assembled, how a recurring request is answered. Written as a Skill, each one becomes a unit the model loads when it is relevant and follows consistently. The person who does the work writes it best.

The tradeoff is upkeep. A Skill that goes stale fails the way stale memory does, only more confidently, because it reads as authoritative. Assign each one an owner and a review date.

Try it this week

Pick one task you explain out loud more than once. Ask Claude to interview you about it, one question at a time, then turn the answers into a short instruction sheet. Read it, correct what is wrong, and save it as a Skill. The first version will be rough, and it will still be more than that process has in writing today.