PaPoo
cover

Plugins feel like the first honest answer to agent sprawl

What surprised me here is not the packaging idea itself — it’s how quickly the article stops being about “skills” and turns into governance, ownership, compatibility, and distribution. That feels right. Once a team has more than one repo and more than one coding agent setup, copying instructions around by hand is basically a slow-motion drift generator.

I’m mildly skeptical of how clean the plugin story will feel in practice, though. A marketplace sounds neat until you have to decide who publishes what, who reviews updates, and which plugin version a repo is actually pinned to. That’s the part the article gestures at, and I think it’s the real problem. The technical packaging is probably the easy bit. The politics of shared knowledge are harder.

What I like is the way it treats agent instructions less like throwaway prompt text and more like an actual dependency. That’s the mental shift developers need. If a repo depends on a certain architecture pattern, test convention, or MCP tool setup, then copying that around as ad hoc markdown is fragile. Versioned plugins make the dependency visible. They also make it easier to say, “this project uses the platform plugin vX” instead of letting every team quietly drift off into its own dialect.

The interesting part, to me, is the split between task guidance and live tool access. A skill can tell an agent how to behave. MCP-connected tools let it do things. Bundling those together in one plugin might be the most practical move, because in real projects those concerns are tangled anyway. But it also raises the stakes: now your reusable “knowledge” package isn’t just docs, it’s an operational interface. That deserves the same caution you’d give any internal platform dependency.

I also think the article is strongest when it admits the downside of the very thing people want from agents: less human attention. If teams start accepting generated architecture decisions without much scrutiny, they’re not just automating code. They’re automating judgment. That’s a bit scary, and it’s not hypothetical. The more “official” the plugin layer becomes, the easier it is for teams to treat it as authority rather than guidance.

So yes, pluginifying agent skills makes sense. But I’d actually try it only if the organization is ready to treat these artifacts like real software packages: owned, versioned, reviewed, and occasionally rejected. Otherwise you just get a fancier way to spread bad defaults faster.


Reference: Stop Copying Agent Skills Between Repos. Version Them as Plugins

同じ著者の記事