| ▲ | davidkunz 9 hours ago |
| Please standardize the folder. .claude/skills
.codex/skills
.opencode/skills
.github/skills
|
|
| ▲ | prettyblocks 9 hours ago | parent | next [-] |
| I find that even though this isn't standard, that these -cli tools will scan the repo for .md files and for the most part execute the skills accordingly. Having said that, I would much prefer standards not just for this, but for plugins as well. |
| |
| ▲ | iainmerrick 8 hours ago | parent [-] | | Standards for plugins makes sense, because you're establishing a protocol that both sides need to follow to be able to work together. But I don't see why you need a strict standard for "an informal description of how to do a particular task". I say "informal" because it's necessarily written in prose -- if it were formal, it'd be a shell script. |
|
|
| ▲ | albert_e 8 hours ago | parent | prev | next [-] |
| This is happening as we speak. Codex started this and OpenCode followed suit with the hour. https://x.com/embirico/status/2018415923930206718 |
| |
|
| ▲ | m4r71n 8 hours ago | parent | prev | next [-] |
| That is being discussed in https://github.com/agentskills/agentskills/issues/15. |
|
| ▲ | verdverm 9 hours ago | parent | prev | next [-] |
| .agent/ Skills seem a bit early to standardize. We are so early in this, why do we want to handcuff our creativity so soon? |
| |
| ▲ | arrowsmith 9 hours ago | parent | next [-] | | Skills are a really simple concept. They're just custom prompts with a name and some metadata. What are you afraid of handcuffing? | | |
| ▲ | likium 9 hours ago | parent | next [-] | | Just the decision of whether to allow models to invoke them has [1][2][3] different ways. [1]: https://code.claude.com/docs/en/skills#control-who-invokes-a...
[2]: https://opencode.ai/docs/skills/#disable-the-skill-tool
[3]: https://developers.openai.com/codex/skills/#enable-or-disabl... | | |
| ▲ | arrowsmith 8 hours ago | parent [-] | | All the more reason to standardise it | | |
| ▲ | wernerb 2 hours ago | parent | next [-] | | We keep standardising without adding versioning :( | |
| ▲ | verdverm 8 hours ago | parent | prev [-] | | Eventually, you can standardize what you don't understand The problem I see now is that everyone wants to be the winner in a hype cycle and be the standards bringer. How many "standards" have we seen put out now? No one talks about MCP much anymore, langchain I haven't seen in more than a year, will we be talking about Skills in another year? |
|
| |
| ▲ | verdverm 9 hours ago | parent | prev | next [-] | | 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) | | |
| ▲ | arrowsmith 8 hours ago | parent [-] | | > They are more than that, for example the frontmatter and code files around them. You are right. I have edited my post slightly. > Why do I want to throw away my dependency management system and shared libraries folder for putting scripts in skills? You don't have to put scripts in skills. The script can be anywhere the agent can access. The skill just needs to tell the LLM how to run it. > Does it even make sense to have skills in the repo? How do I use them across projects? You don't have to put them in the repo. E.g. with Claude Code you can put project-specific skills in `.claude/skills` in the repo and system-wide skills in `~/.claude/skills`. | | |
| ▲ | verdverm 8 hours ago | parent [-] | | 2. The spec / docs show people how to put code in a subdir. While you can reference external scripts, there is a blessed pattern that seems like an anti-pattern to me 3. generalize: how do I store, maintain, and distribute skills shared by employees who work on multiple repos. Sounds like standard dependency management to me. Does to some of the people building collections / registries. Not sure if any of them account for versioning, have not seen anything tied to lock files (though I'd avoid that by using MVS for dep selection) |
|
| |
| ▲ | vidarh 8 hours ago | parent | prev [-] | | Agreed. I think being overly formal about what can be in the frontmatter would be a mistake, but the beauty of doing this with an LLM is that you can pretty much emulate skills in any agent by telling it to start by reading the frontmatter of each skills file and use that to decide when to read the rest, so given that as a fallback, it's hardly imposing some massive burden to standardise it a bit. |
| |
| ▲ | nikcub 4 hours ago | parent | prev [-] | | it's actually .agents/ :) | | |
|
|
| ▲ | mijoharas 7 hours ago | parent | prev | next [-] |
| I mean, it'd be good if these tools followed the xdg base spec and put their config in `~/.config/claude` e.t.c instead of `~/.claude`. It's one of my biggest pet peeves with a lot of these tools (now admittedly a lot of them have a config env var to override, but it'd be nice if they just did the right thing automatically). |
|
| ▲ | tobyhinloopen 9 hours ago | parent | prev | next [-] |
| ln -s to the rescue! |
| |
| ▲ | davidkunz 9 hours ago | parent | next [-] | | The root cause should be fixed. | |
| ▲ | flurdy 8 hours ago | parent | prev | next [-] | | It's why I wrapped my tiny skills repo with a script that softlink them into whichever is your skills folder, defaulting to Claude, but could be any other. I treat my skills the same as I would write tiny bash scripts and fish functions in the days gone to simplify my life by writing 2 words instead of 2 sentences. Tiny improvement that only makes sense for a programmer at heart. [1] https://github.com/flurdy/agent-skills | |
| ▲ | 9 hours ago | parent | prev | next [-] | | [deleted] | |
| ▲ | smithkl42 9 hours ago | parent | prev | next [-] | | That doesn't work very well if your developers are on Windows (and most are). Uneven Git support for symbolic links across platforms is going to end up causing more problems than it solves. | |
| ▲ | xrd 9 hours ago | parent | prev [-] | | Why not hardlinks? | | |
|
|
| ▲ | 8 hours ago | parent | prev | next [-] |
| [deleted] |
|
| ▲ | throwaway98797 8 hours ago | parent | prev | next [-] |
| might be too early to standardize standards are good but they slow development and experimentation |
|
| ▲ | rvz 9 hours ago | parent | prev | next [-] |
| There are 14 competing standards. |
| |
| ▲ | d1sxeyes 8 hours ago | parent | next [-] | | The problem is that the de facto standard is `.claude`, which is problematic for folks not using Claude. | | |
| ▲ | OtherShrezzing 8 hours ago | parent [-] | | Your skill then just becomes an .md file containing >any time you want to search for a skill in `./codex`, search instead in `./claude` and continue as you were. | | |
| ▲ | AndroidKitKat 7 hours ago | parent [-] | | I see it similar to browser user-agents all claiming to be an ancient version of Mozilla or KHTML. We pick whatever works and then move on. It might not be "correct," but as long as our tools know what to do, who cares? |
|
| |
| ▲ | PurpleRamen 9 hours ago | parent | prev | next [-] | | Now, there are 15 competing standards. | |
| ▲ | smithkl42 9 hours ago | parent | prev [-] | | Soon... |
|
|
| ▲ | behnamoh 9 hours ago | parent | prev [-] |
| Worse yet; opencode uses singular words by default: .opencode/skill
|
| |
