Interesting to see the convergence across Claude Code, Codex, and Gemini CLI on what's becoming an informal SKILL.md standard. The README-for-tool-use pattern is obvious in retrospect but it took a while to get here.
Two things I haven't seen solved cleanly in the format yet:
1. Skill composition/dependencies. If skill A and skill B both need a Python library, there's no dependency manifest -- each skill has to defensively check and install its own requirements. An optional `requires:` block in the frontmatter would make composition cleaner and avoid redundant installs.
2. Versioning. If my workflow depends on the behavior of `hugging-face-cli@huggingface/skills`, is there a mechanism to pin a version, or is it always HEAD? Skills that evolve can silently break downstream workflows.
Would be curious if there's prior art from package managers (npm/cargo workspaces) that could be adapted here -- the distribution problem is similar.
naillang•20m ago
Two things I haven't seen solved cleanly in the format yet:
1. Skill composition/dependencies. If skill A and skill B both need a Python library, there's no dependency manifest -- each skill has to defensively check and install its own requirements. An optional `requires:` block in the frontmatter would make composition cleaner and avoid redundant installs.
2. Versioning. If my workflow depends on the behavior of `hugging-face-cli@huggingface/skills`, is there a mechanism to pin a version, or is it always HEAD? Skills that evolve can silently break downstream workflows.
Would be curious if there's prior art from package managers (npm/cargo workspaces) that could be adapted here -- the distribution problem is similar.