Your AI Agent Skills Have a Version Control Problem

You build a skill for your AI coding agent. You refine it across five sessions. You upload it to a new conversation and immediately hit the question you can't answer: is this the one from yesterday, or the one from Tuesday? If you're working in Claude Chat, there's no persistent filesystem. If you're in Codex, the session is stateless. If you moved the skill from Claude Code to Gemini CLI, you probably renamed a file and forgot which copy is canonical. And if someone else is using your skill, they have no way to know whether their copy matches yours. Git solves this for code repositories. But agent skills don't always live in repos. They live in chat uploads, settings panels, Obsidian vaults, .skill files, and directories that get copied between surfaces with no audit trail. The version information needs to travel with the files, not alongside them in a system the files might never touch. What skill-provenance does skill-provenance is a meta-skill, or a skill that manages other skills.