Agent skills hit a 56,804-item trigger bottleneck

A new paper counts 56,804 public agent skills, while installed skill descriptions compete for fewer than 100 reliable trigger slots in an agent’s system prompt. The @skills proposal separates skill content and persistence from automatic triggering, and points to an open protocol that reads a skill from a path instead of keeping every description resident. Builders accumulating playbooks should treat retrieval and invocation as separate infrastructure problems; the archive’s GitHub agent control-plane story shows why the trigger boundary belongs in the workflow design.