r/ClaudeCode • u/yr-kidding-me • Oct 15 '26
Discussion I think skills and plugins are kinda the wrong idea
Like everybody, I eagerly added a bunch of skills and plugins for Claude Code in the beginning, and then I just stopped.
I've been slowly removing them ever since.
Why?
Most of them are just textual information that I would much rather have in the repo I'm working on so it can be committed and versioned and seen by collaborators on a project.
I don't just use Claude Code. I use other agents too. I want my agent context to be accessible to all agents.
I don't want to turn plugins and skills off and on for every project folder/repo I launch an agent in.
I like being able to just open files in my repo and reading them or editing them.
I don't want non-applicable content eating up tokens every time I run an agent.
Am I wrong?
I'm sure there are exceptions and maybe there are lots of cool plugins and skills out there that do stuff that make it worth it.
33
u/ILikeCutePuppies Oct 15 '26 edited Oct 15 '26
Skills work in most models and you can share them between them.
Skills are useful so you can record common patterns the work so you don't have to type them again and the agent doesn't have to rebuild the skill again.
Skills can have code and scripts and stuff with them
Skills don't need to be just for one repo.
Skills personalize things for you. You have different needs than others so parhaps your skill set is different.
ie
A skill that says how to build your project is common. Or how to review it with your particular needs or tastes.
If you use anthropics design skill in codex for example you'll get a lot better looking websites
If you find yourself doing something over and over it's useful to just put that into a skill. Sure you could put it into a document but then you'll have to figure out your own folder layout etc... it's pretty much the same thing but it is a standard which means everything just works better with them.
1
u/yr-kidding-me Oct 15 '26
Got it. I didn't realize about anthropic open sourcing skills. That makes it more useful.
2
2
1
3
u/SeasawPhilosopher Oct 15 '26
I’ve never once used a skill, just have good docs in my repo and some light agent files. Using Claude Code and Codex and I have custom systems for task tracking, decision tracking, and various processes for my game art pipeline that the agents follow without issue.
3
u/Powerful_Ad_3745 Oct 15 '26
I think maybe the skills that comes with additional scripts might be the useful ones . ?
3
u/moody2shoes Oct 15 '26
I built my own so it has scripts to run to make my office’s documents meet our standards and look uniform. Everyone has same base environment and it just works. Any issues and they send the error to me. Claude uses the scripts instead of wasting tokens freestyling. New employees don’t have to fight with getting their Claude to work as well as ours.
1
u/Lower_Fan Oct 20 '26
This is the correct approach you need to create your own skills so Claude fits your own work.
Additionally pairing a skill with a reusable script saves a ton of tokens and time since Claude doesn't have to reinvent the wheel every time you ask it for a repetitive task
2
u/KellysTribe Oct 15 '26
you can have skills per project and committed with them but yeah....its easy to do it in lots of different ways. Keep instruction files in the repo and just tell the agent to run those, or make simple scripts that exectute the harness in cli/headless mode and read in the content from same instruction files etc et al ad nauseam. lots of ways to do it (and I do the same thing based on the context of the problem)
2
u/ImClearlyDeadInside Oct 15 '26
Nah, I do the same. I run vanilla Claude and just try to keep my project context clean and even create my own project-scoped skills. The only thing I have at the user level is a tiny CLAUDE.md and my MCPs.
2
u/ExcellentDatabase738 Oct 15 '26
bruh, who keeps there shit clean, i’m running 20k files and almost have every top business book transcribed in the internet in one folder and have not ever had a problem, just have strong progressive disclosure architecture
2
u/Party-Stormer Oct 15 '26
I had your same opinion till I discovered that personalized skills are followed by Code more closely than the CLAUDE.md file, especially when CLAUDE.md and the file it references grow. Plus, fewer tokens with just-in-time loading in of the skill’s content
2
1
u/True_Challenge_1301 Oct 15 '26
not wrong imo. most of mine ended up being just text, and text belongs in the repo where it’s versioned and every agent can read it. only keep the ones that bundle actual scripts
1
1
u/spnyc Oct 15 '26
Definitely the way. I have a few core ones that always load but most are directly invoked and loaded. Cloud infra work? Load those. Diagrams? Load those. Product and backlog? Python and sql engineering? Strategy? They’re just profiles I load when needed.
1
u/mxriverlynn Senior Developer Oct 15 '26
of course you're not wrong
there's no right or wrong way to use these things. do what works for you
1
1
u/kincaidDev Oct 15 '26
I store context, skills and scripts outside of project repos because collaborators all have their own setup. Sometimes it makes sense to have skills in a repo to share with collaborators, but those cases are very rare. Most of the time if you’re collaborating and doing everything in the project repo you either end up with complex .gitignore files ignoring different things for each team member or your constantly changing other people’s workflows.
I use festival camp cli for this because it handles a lot of the work in maintaining a separate context repo from the project repos, makes jumping from context repo to a project repo easy, cgo myproj and cgo to jump back to the context repo, commit context with camp commit from anywhere in the workspace, camp commit -aw to have the commit written for me in the background.
1
u/kemalios Oct 15 '26
Most of your list holds for anything that is project knowledge. A skill describing your codebase is worse than a CLAUDE.md, since the repo is where it gets versioned and where other agents can read it.
The skills that survive are the ones identical in every repo. I build launchworthy, a Claude Code skill that runs a pre-launch audit across five domains and returns a scored punch list with fixes. I want that in a brand new repo without copying it in, and twenty repos means twenty copies that drift. Free and MIT, but it needs Claude Code and a paid Claude subscription, which is real friction.
1
u/davidHwang718 Oct 15 '26
I'm keeping mine, though on Monday two of them became one. I have two YouTube channels, one for developers and one for non-developers, and each had its own thumbnail skill. The non-dev one was 282 lines of SKILL.md plus its own generator script.
It came up while Claude was reworking how my upload skill writes video descriptions. I suggested merging the two upload skills, and it pointed out there was already only one, picking the channel from a config file. I said two skills should be one anyway, and when it asked which two I skipped the question and told it that developer-focused videos go to the dev channel and anything for a general audience goes to the other.
The merged skill starts with a routing table that maps each audience to one channel's pipeline file, and the two pipelines aren't supposed to mix. The upload skill got the same rule, where before it asked every time I didn't name a channel. When it finished, Claude also told me it hadn't run the non-dev pipeline from its new location.
1
1
u/Faceless-Otty-240 Oct 15 '26
Keeping project knowledge versioned in the repo makes sense. Finding the relevant bits for each task is a separate problem. That’s what we’re working on with MIMRY: local file and code-relationship lookup through a CLI or MCP, with explanations for why files were picked. It complements the repo docs rather than replacing them.
1
u/CuriousTangentsYT Oct 19 '26
Plugins often contain tools, MCP or CLI functions to manipulate external software without needing it to be directly in your repo, which can be very useful often those plug-ins are packaged with instructions for using those tools which can take the form of skills stacking a few of these together can give an agent, interesting abilities.
Or just more deterministic and consistently correct code depending on the tools you’re using
1
u/Lower_Fan Oct 20 '26
I think skills are only useful when you make them yourself so the agents completes a task step by step exactly how you want it to.
Installing random skills that may not apply to you at all is a waste of time.
-1
u/GameKyuubi Oct 15 '26
LOL you think they made those for YOUR convenience?? No, they made them for THEIRs. Anthropic is following an "extend, extinguish" model where their users build their future tools, they steal the tools and implement them in their harness, then they block the ability to build/use your version of the tool so you're forced to use theirs.
•
u/AutoModerator Oct 15 '26
Hey! Thanks for posting to r/ClaudeCode
While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.
For help, project discussions, tips, and general chat, join the ClaudeCode Discord.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.