The Skill Trigger Bottleneck
Free while signed in. Answers cite the passages they came from.
There are 56,804 public agent skills today, all competing for fewer than 100 reliable trigger slots in the system prompt. Your own playbooks compete for that same space, which means the long tail never gets used no matter how good it is. The paper argues the scarcity is an artifact of how skills get installed, not a real limit.
One word for three separate things: Installation currently bundles content, persistence, and automatic triggering. Only triggering needs to occupy prompt space, so the protocol separates the three and prices each tier by what it actually costs.
A path is the whole interface: A path addresses any skill, subtree, or collection, and reading it is enough to use it. A directory becomes a menu, so bundles stop being all-or-nothing and you can pull one file out of someone else's collection.
Vendoring gives you ownership: Copying a skill into your Git tree at the same path means your team owns and adapts it, with zero token cost until it is named.
Why it matters: No manifest, no lockfile, no registration, and SKILL.md is unchanged, so this is adoptable without an ecosystem migration. The three-tier framing is the useful part even if you never adopt the protocol: decide per skill whether it needs to fire unasked, and most of yours do not.
Get next week’s papers.
The same picks and the same summaries, in your inbox. Free, and 176 issues deep.
Subscribe on Substack