Mar 23, 2026 | Issue 43
One people prompt 🧠
🔭 Signal: The Skill You Don’t Need to Have
Two weeks ago we flagged the vocabulary fork. Last week we showed that skills were never guarantees to begin with. This week, something genuinely new for many readers: a real-world example of what Agent Skills mean at work.
TLDR: The barrier to access collapsed, but the barrier to judgment didn’t.
I recently packaged years of accessibility auditing experience into an agent skill called a11y-audit. It’s a portable bundle that any developer can install using the Agent Skills standard. It runs automated checks, maps findings to WCAG 2.1 AA criteria, generates structured reports, and can file issues in your tracker. Someone with zero accessibility background can install it in thirty seconds and get results that cover more ground, more consistently, than running the same checks manually.
That’s the part that changed. Not just “AI can do things faster.” What changed is that expertise became installable. A person who has never studied accessibility can now summon most of mine.
Not all of it, though. Not the judgment calls about which findings to prioritize, not the instinct for what a screen reader user actually experiences, not the taste that comes from years of working with people who navigate the web differently than I do. But the execution layer? The structured audit itself? That travels now.
This pattern works anywhere someone has hard-won expertise that includes a repeatable methodology. The expert still matters. But what the expert does and what the expert knows just became separable in a way they never were before.
🧠 Strategic (People) Prompt: What Could You Package?
Instead of asking: What skills does our team need to develop? Ask: What expertise do we already have that others could use without our background?
Think about the person on your team who everyone turns to for one specific thing. The one who “just knows” how to do it. Now ask:
- Could the repeatable part of what they do be described in steps and packaged?
- Who else inside or outside the organization would benefit from being able to run it?
- What would that person be freed up to do if the execution layer was no longer only theirs?
➖ Subtraction Opportunity: Gatekeeping Reflex
Stop assuming that only credentialed people should have access to expert-grade tools.
The instinct to gatekeep is understandable. If someone doesn’t have the training, they might misread the output. They might act on findings they don’t fully understand. Those are real risks.
But the alternative, locking the tool away until everyone completes a training program that may never happen, means the audit never gets run, the check never gets made, and the gap never gets found. That’s a worse outcome for almost everyone.
Instead, separate the two layers:
- Running the skill requires access and a clear prompt. Lower this barrier.
- Interpreting the results requires context, judgment, and often a human. Raise the visibility and the frequency of this step.
The skill should be easy to summon. The judgment should be hard to skip.
🍛 Analogy of the Week: The Recipe
A master chef spends twenty years refining a dish. Tasting, adjusting, failing, learning. The broth reduces for exactly as long as it needs to. The seasoning shifts depending on the humidity that day. Every decision carries decades of accumulated instinct.
Then the chef writes it down. A recipe. Ingredients, quantities, timing, technique. Clear enough that someone who has never cooked this dish before can follow the steps and produce something genuinely good. Not identical to what the chef makes. But far better than what that person would have made on their own.
The recipe traveled. The palate stayed with the chef.
Now imagine the chef refuses to share the recipe because “you wouldn’t understand why I use this particular salt.” Maybe true. But the person following the recipe still eats better tonight than they would have without it. And when they taste something that doesn’t seem right, they know to call the chef.
That’s what packaged skills do. They carry the methodology. They don’t carry the taste. And the world eats better when the recipe circulates, even if the palate stays rare.
♬ Closing Notes
This is the third in our skills series, and now you know the execution layer is separable from the judgment layer. Let that sink in, it definitely changes things.
Next week, the final piece: when both humans and agents describe their skills in the same format, skills stop being a personal attribute and become a shared operational language. That’s when allocation decisions start looking very different.
Until next week,
Sam Rogers Recipe Sharer Snap Synapse – from AI promise to AI practice
Speaking of packaged skills: is your website ready for the agents that are already browsing it? Siteline runs a free scan and tells you where they get stuck.