AI Post

@kaka_ruto retweeted I've been building agent CLIs a lot lately and I ran into a basic problem recentlyThe CLI would change, but the agentic instructions would not(important if you supply instructions that teach agents how to use your cli)So an agent could be “correct” and still fail, because it was following steps from the wrong cli versionI tried a few ideas that sounded easier but weren’t ideal - eg one global “latest” SKILL.md, but this meant older CLI installs would break because they read newer instructionsThen I had an idea today - ship the CLI with a SKILL.md, and make that file version-linked to the CLI releaseHere's the magic about that: when you install an older CLI, you get the matching older skill; when you upgrade the CLI, the managed skill updates with it!So now I keep the skill in the CLI repo, update it in the same PRs, and release them together. On install/update, I place it in a predictable path like .agents/skills/<skill-name>/SKILL.mdThis completely eliminates drift, and for agent workflows that matters more than anything else, try it! Posted Mar 27, 2026 at 7:34PM