5 ms·

Please standardize the folder. .claude/skills .codex/skills .opencode/skills .github/skills

by davidkunz 8mo ago

tobyhinloopen 8mo ago
ln -s to the rescue!
- davidkunz 8mo ago
  The root cause should be fixed.
- deleted 8mo ago
  [deleted]
- xrd 8mo ago
  Why not hardlinks?
  - dmd 8mo ago
    You can't hardlink a directory.
    - deleted 8mo ago
      [deleted]
- smithkl42 8mo ago
  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.
  - tobyhinloopen 8mo ago
    Win developers aren't using WSL?
- flurdy 8mo ago
  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 https://github.com/flurdy/agent-skills
verdverm 8mo ago
.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 8mo ago
  Skills are a really simple concept. They're just custom prompts with a name and some metadata. What are you afraid of handcuffing?
  - likium 8mo ago
    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-skill https://code.claude.com/docs/en/skills#control-who-invokes-a... [2]: https://opencode.ai/docs/skills/#disable-the-skill-tool https://opencode.ai/docs/skills/#disable-the-skill-tool [3]: https://developers.openai.com/codex/skills/#enable-or-disable-skills https://developers.openai.com/codex/skills/#enable-or-disabl...
    - arrowsmith 8mo ago
      All the more reason to standardise it
      - verdverm 8mo ago
        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?
      - wernerb 8mo ago
        We keep standardising without adding versioning :(
  - verdverm 8mo ago
behnamoh 8mo ago
Worse yet; opencode uses singular words by default: .opencode/skill
- davidkunz 8mo ago
  On the website[1] it says: .opencode/skills [1]: https://opencode.ai/docs/skills/#place-files https://opencode.ai/docs/skills/#place-files
  - the_mitsuhiko 8mo ago
    They changed it. It was singular.
prettyblocks 8mo ago
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 8mo ago
  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.
rvz 8mo ago
There are 14 competing standards.
- smithkl42 8mo ago
  Soon...
- PurpleRamen 8mo ago
  Now, there are 15 competing standards.
- d1sxeyes 8mo ago
  The problem is that the de facto standard is `.claude`, which is problematic for folks not using Claude.
  - OtherShrezzing 8mo ago
    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 8mo ago
      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?
    - JoBrad 8mo ago
      My repos are littered with agent-specific files containing “treat this other file as if it were this one.” We’re moving so fast on so many fronts, and it seems odd that this is the persistent problem. It doesn’t even help lock folks into one agent, so I’m not clear why the industry hasn’t yet standardized on one project-specific file name yet.
m4r71n 8mo ago
That is being discussed in https://github.com/agentskills/agentskills/issues/15 https://github.com/agentskills/agentskills/issues/15.
albert_e 8mo ago
This is happening as we speak. Codex started this and OpenCode followed suit with the hour. https://x.com/embirico/status/2018415923930206718 https://x.com/embirico/status/2018415923930206718
- PantaloonFlames 8mo ago
  “Proposal: include a standard folder where agent skills should be“ https://github.com/agentskills/agentskills/issues/15 https://github.com/agentskills/agentskills/issues/15
- wernerb 8mo ago
  Could we adhere to the XDG standard and put config in ~/config/agents Or perhaps create a new XDG standard? Like $XDG_AGENTS_HOME ?
throwaway98797 8mo ago
might be too early to standardize standards are good but they slow development and experimentation
deleted 8mo ago
[deleted]
mijoharas 8mo ago
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).

Please standardize the folder. .claude/skills .codex/skills .opencode/skills .github/skills

tobyhinloopen 8mo ago

ln -s to the rescue!

davidkunz 8mo ago
The root cause should be fixed.
deleted 8mo ago
[deleted]
xrd 8mo ago
Why not hardlinks?
- dmd 8mo ago
  You can't hardlink a directory.
  - deleted 8mo ago
    [deleted]
smithkl42 8mo ago
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.
- tobyhinloopen 8mo ago
  Win developers aren't using WSL?
flurdy 8mo ago
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 https://github.com/flurdy/agent-skills

verdverm 8mo ago

.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 8mo ago
Skills are a really simple concept. They're just custom prompts with a name and some metadata. What are you afraid of handcuffing?
- likium 8mo ago
  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-skill https://code.claude.com/docs/en/skills#control-who-invokes-a... [2]: https://opencode.ai/docs/skills/#disable-the-skill-tool https://opencode.ai/docs/skills/#disable-the-skill-tool [3]: https://developers.openai.com/codex/skills/#enable-or-disable-skills https://developers.openai.com/codex/skills/#enable-or-disabl...
  - arrowsmith 8mo ago
    All the more reason to standardise it
    - verdverm 8mo ago
      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?
    - wernerb 8mo ago
      We keep standardising without adding versioning :(
- verdverm 8mo ago

behnamoh 8mo ago

Worse yet; opencode uses singular words by default: .opencode/skill

davidkunz 8mo ago
On the website[1] it says: .opencode/skills [1]: https://opencode.ai/docs/skills/#place-files https://opencode.ai/docs/skills/#place-files
- the_mitsuhiko 8mo ago
  They changed it. It was singular.

prettyblocks 8mo ago

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 8mo ago
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.

rvz 8mo ago

There are 14 competing standards.

smithkl42 8mo ago
Soon...
PurpleRamen 8mo ago
Now, there are 15 competing standards.
d1sxeyes 8mo ago
The problem is that the de facto standard is `.claude`, which is problematic for folks not using Claude.
- OtherShrezzing 8mo ago
  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 8mo ago
    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?
  - JoBrad 8mo ago
    My repos are littered with agent-specific files containing “treat this other file as if it were this one.” We’re moving so fast on so many fronts, and it seems odd that this is the persistent problem. It doesn’t even help lock folks into one agent, so I’m not clear why the industry hasn’t yet standardized on one project-specific file name yet.

m4r71n 8mo ago

That is being discussed in https://github.com/agentskills/agentskills/issues/15 https://github.com/agentskills/agentskills/issues/15.

albert_e 8mo ago

This is happening as we speak. Codex started this and OpenCode followed suit with the hour. https://x.com/embirico/status/2018415923930206718 https://x.com/embirico/status/2018415923930206718

PantaloonFlames 8mo ago
“Proposal: include a standard folder where agent skills should be“ https://github.com/agentskills/agentskills/issues/15 https://github.com/agentskills/agentskills/issues/15
wernerb 8mo ago
Could we adhere to the XDG standard and put config in ~/config/agents Or perhaps create a new XDG standard? Like $XDG_AGENTS_HOME ?

throwaway98797 8mo ago

might be too early to standardize standards are good but they slow development and experimentation

deleted 8mo ago

[deleted]

mijoharas 8mo ago

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).