Skills, plugins, and marketplaces - what's a girl to do?

[hesreallyhim]

What should "awesome-claude-code" do when it comes to Agent Skills (complicated, domain-specific packages of instructions, tools, and other resources), plugins (even more complicated groupings of other things), and marketplaces (groupings of groupings of complicated things)?

[marcindulak]

I think due to the infeasibility to verify the quality of complex things, especially those that are markdown-only, or are collections of external, unvetted resources, you could wait until the market stabilizes a bit.

In terms of markdown-based tools, I believe the inability of LLMs to follow instructions is still an unsolved problem (see for example https://github.com/ykwon0407/reasonIF, anthropics/claude-code#13689, or anthropics/claude-code#3382).

[hesreallyhim]

@marcindulak I wonder how you feel about this statement today. It's largely case-by-case and anecdotal but I am spending a lot less time "baby-sitting" the more recent Claude models.

[EthanFrostpro]

this hits a real gap. i started writing scope rules + AGENTS.md / CLAUDE.md files for every project i build (claude code on a nuxt 3 + go-zero stack), then realized i kept losing them across machines and forgetting which boundaries already worked on which subsystem.

ended up putting together https://tokrepo.com/en — a small public registry for skills, AGENTS.md files, and MCP server configs. not trying to be a marketplace with monetization or curation gatekeeping; just a place to dump the boundary rules / context files that worked for me and pull what others have published.

the thing i appreciate about awesome-claude-code is that it indexes the projects. what's been missing for me was an index of the configurations — the skill files, scope rules, and context that go inside a project. they feel like different artifacts and people end up rebuilding both from scratch every time.

[hesreallyhim]

@EthanFrostpro I basically do this too but I just have a special skill/agent that creates them for me so it's no hassle. I hear what you're saying, and I haven't checked out your site, but in my opinion as a maintainer it's hard to find things that have strong general utility, because Claude can basically build bespoke tooling for every project you work on pretty easily. So I try to focus on generic patterns. Anyway, I hope you will enjoy the new "experience."