Should we consider maintaining an official `SKILL.md` file(s) for this library?

[thunderbiscuit]

Opening the discussion here. I know of other projects who maintain official SKILL.md files that devs can add to their repositories (although they're much bigger than this library, but still).

Looking into it a bit it appears that it could be useful, particularly because of the API churn we've had which can confuse models, or sometimes they just plain don't know that their information is stale, which is what the file help shortcut.

Please pitch in if you work with skills a lot and have an opinion either way!

[EliteCoder18]

I think this is a great idea. I'd also suggest explicitly pinning the MSRV in the file, as that's one of the first things models tend to get wrong as a project evolves.

If we structure SKILL.md around a simple schema from the start, we could eventually lint parts of it in CI, verifying API references, feature flags, and deprecations to keep it synchronized with the codebase.