zlacker

[return to "Agent Skills"]
1. davidk+O6[view] [source] 2026-02-03 14:45:42
>>moored+(OP)
Please standardize the folder.

  .claude/skills
  .codex/skills
  .opencode/skills
  .github/skills
◧◩
2. verdve+e9[view] [source] 2026-02-03 14:56:30
>>davidk+O6
.agent/

Skills seem a bit early to standardize. We are so early in this, why do we want to handcuff our creativity so soon?

◧◩◪
3. arrows+Rc[view] [source] 2026-02-03 15:13:15
>>verdve+e9
Skills are a really simple concept. They're just custom prompts with a name and some metadata. What are you afraid of handcuffing?
◧◩◪◨
4. verdve+fe[view] [source] 2026-02-03 15:20:07
>>arrows+Rc
They are more than that, for example the frontmatter and code files around them. The spec: https://agentskills.io/specification

Why do I want to throw away my dependency management system and shared libraries folder for putting scripts in skills?

What tools do they have access to, can I define this so it's dynamic? Do skills even have a concept for sub tools or sub agents? Why do I want to put references in a folder instead of a search engine? Does frontmatter even make sense, why not something closer to a package.json in a file next to it?

Does it even make sense to have skills in the repo? How do I use them across projects? How do we build an ecosystem and dependency management system for skills (which are themselves versioned)

[go to top]