More standard-compliant agent skills setup

[mavam]

Any chance you can improve the UX with the agent skills standard and the "standard" tooling? For example, it'd be nice if I can just write skills add 1weiho/open-slide -g and I'm done, potentially after installing the npm package.

Global/project skills typically reside in ~/.agents/skills unless you only design for Anthropic's custom way of doing things. As Codex and Pi user, getting started with open-slide is clumsy.

But I personally find that the best UX would be that installing a skill should be sufficient. Ideally, the skill just tells how to use a CLI tool and we're done.

(NB: the issue template is a bit awkward to start a standard conversation. The discussion tab 404s, so I had to abuse "bug.")

[1weiho]

@mavam Hey Matthias! Thanks for the feedback.

Right now, open-slide stores skills in .agents/skills, which matches most agent setups, and .claude/skills is just a symlink.
We’re not relying on the skills CLI because the framework’s skill versions are tightly coupled to the built-in primitives.
So 0.x of the framework needs 0.x of the skills. We sync them with an internal skills update mechanism to keep skills and the package version aligned.

I know this has trade-offs. But we can’t let users always pull the latest skills via the CLI, since that might not match the framework version and could break slide generation. Hope that makes sense!

[mavam]

There might be a misunderstanding.

I didn't mean skills for development, which is what the current skills seem to be, but rather skills for using open-slide. Here's an example how skills are discovered with the de-facto skill management tool: https://github.com/vercel-labs/skills#creating-skills.

It's usually a thin discovery layer around the CLI to let agents find the necessary entry point into getting started.