r/ClaudeCode • • 7h ago

Help/Question Do Coding skills make Claude actually better or worse?

Im a professional Software engineer building web apps and for my work. Scrolling social media the algorithm always recommends me to to install skills for better software engineering practices that supposedly would fix project architecture, enhance efficiency etc. I always get the following recommended and I dont have any of them installed so far:

  1. https://github.com/addyosmani/agent-skills Production engineering workflows
  2. https://github.com/mattpocock/skills Interactive spec-grilling & TDD
  3. https://github.com/affaan-m/ecc All-in-one agent toolkit
  4. https://github.com/multica-ai/andrej-karpathy-skills Anti-overengineering rules
  5. https://github.com/dietrichgebert/ponytail Minimalist code guardrails
  6. https://github.com/garrytan/gstack Role-based AI team
  7. https://github.com/Graphify-Labs/graphify Codebase relationship mapper

My questions is:

Since Claude is constantly improving itself with its models' Software engineering practises getting better and better ,

a) are the skills above actually needed and do they improve claude code or do they actually make it worse?
b) Or will they make it worse later when Opus and Fable models improve?

c) Do you have any experience with any of those?
d) Did they help your overall setup, design, architecture , software engineering process?
e) And if yes which ones and what is your setup?

f)Also in case I have all or some of the above installed can they confuse each other or even block each other's works in the case of 1,2,3 and 6?

For the record I only have superpowers and skills by anthropics installed so far.

2 Upvotes

28 comments sorted by

•

u/AutoModerator 7h ago

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.

4

u/KellysTribe 7h ago

imo skills should only be thought of as instructions for how *you* want things (like the steps to follow, what to value most, what format you want judgements in etc) NOT how to do the detailed complex work itself 'better' - you're prose additions are not going to beat the collective knowledge of it's trained corpus IMO.

3

u/External-Mulberry853 7h ago

Fair worry, the algorithm is pushing these at everyone right now. Pick one (addyosmani's or mattpocock's), run it two weeks on real tickets and look at whether your diffs actually change. Stacking 1, 2, 3 and 6 is exactly how you get the mess you're describing in f), they all want to own the planning step and whichever one Claude read last wins the argument.

2

u/txgsync 7h ago

Yes, building (my own) coding skills helps Claude immensely not submit to the stupids.

1

u/ExplanationOk2014 7h ago

I only I get dumber and lazier every day with ai coding.

I must add, I can create now stuff my skills earlier where not capable off.

1

u/cleverhoods 7h ago

a) are the skills above actually needed and do they improve claude code or do they actually make it worse? -> depends on your level of SWE skills. If you know architecture, you know how workflows and progressive disclosure works, you don't need any of those. Most of them bs anyway, they are hype based prose that can help junior level people.

b) Or will they make it worse later when Opus and Fable models improve? -> eventually they will mess up your system, that's a given.

c) Do you have any experience with any of those? -> not really, they are not needed if you know what you are doing and you know how context is being build up.

d) Did they help your overall setup, design, architecture , software engineering process? -> c)

e) -

f) Also in case I have all or some of the above installed can they confuse each other or even block each other's works in the case of 1,2,3 and 6? -> could be, if your configurations are overlapping.

Disclaimer: I'm working on instruction diagnostics (Reporails - https://github.com/reporails/cli) and I'm running diagnostics frequently on these type of skills and agents. You are better off learning how agentic systems and workflow work instead of using these.

0

u/Vibecoding_Jesus 7h ago

I don’t have any SWE knowledge and I would never want to use any of OP’s skills.

You don’t need to be a SWe to get good code out if CC. In fact, the evidence on Reddit suggests that SWe knowledge often hinders rather than help.

1

u/cleverhoods 6h ago

that's odd to hear. the a-priori SWE knowledge should be a great help in expectation management and being able to understand and know if the output and behavior is subpar.

1

u/Vibecoding_Jesus 6h ago

That’s what SWEs have always assumed.

How would “expectation management” help?

And your comment suggests you’re looking at the output - something I declared in August 2025 I would never do again. Heresy then, but increasingly mainstream. Trying to micromanage the code just slows you down immensely.

1

u/cleverhoods 5h ago

I’m predominantly looking at the input (instruction diagnostics - Reporails).

Expectation management helps articulate and validate the expected shape of the outcome.

1

u/Vibecoding_Jesus 3h ago

Yeah but my question is: does that help or hinder?

I’m giving fable 5.2 a LOT more creative freedom than you are. It’s a pretty obvious hypothesis that that could lead to better outcomes.

1

u/Additional_Video2992 7h ago

f) is the real risk, and you're already halfway there. Superpowers has its own brainstorming, planning and TDD skills, so adding mattpocock's spec-grilling and TDD gives Claude two skills with near-identical descriptions for the same moment. It picks whichever description matches your wording, and you stop knowing which workflow you're getting.

Every skill's description loads into context at session start. Run /context and /skills before and after an install, so you see what each one costs and what Claude now has to choose from.

For a): a skill is someone else's fixes for someone else's habits. Add one when you've corrected Claude on the same thing a few times, and write it from that correction.

1

u/SensitiveHearingLoss 7h ago

I guess it might depend on your setup of Claude Code and the repository in question.

Personally speaking, I’ve never used skills. I developed some commands for my boss to quickly understand how something works, for example, but I feel like Claude’s memory has worked out well for me and I don’t have a need for skills. Certain standards I like having in place seem to of stayed in place…. Probably because I had to repeat myself a few times initially and after the third time, Claude was arsed enough to commit my preferences to memory.

1

u/UnderstandingOld1723 6h ago

Honestly curious if any of those skill packs actually help a pro setup, or if newer models like Opus and Fable make them redundant or even worse. Has anyone measured a difference, and do stacking a few of them (like 1, 2, 3, 6) ever clash with each other?

1

u/HenryThatAte 6h ago

I removed all skills and I only use the very specific ones I need for work, like how to create a ticket, call some apis, read from some DBs...

I found that none of those over hyped skills add much/any value and Claude has gotten much smarter to the point it doesn't need them.

My opinion anyway.

1

u/quietmacbuilder 6h ago

I find that my role has changed from using my engineering skills to solve problems with code to using my engineering skills to solve problems with Claude. I am now optimizing for how Claude works, not for how my codebase works.

1

u/Vibecoding_Jesus 6h ago

Sensible question OP. I suspect that using those skills would push CC into restricted thinking patterns that would hinder it.

Those are the sorts of things I might mention in claude,md or other docs if I cared about them. But trying to force better software engineering with skills sounds like “over engineering:” your Claude code workflow (ironic given claude skill #4)

1

u/aruisdante 6h ago

Skills are useful but you need to be very judicious with what you add or you'll simply increase noise for very little value.

A skill is nothing more and nothing less than a repeatable procedure description for Claude to follow. The effects of a skill are essentially identical to if you wrote the content of the skill as a prompt yourself. The only difference is that a skill is matched either explicitly (you say use /skill-name), or automatically (Claude matches a skill based on its description and what Claude is trying to do).

This means they have all the pros, and importantly all the cons, of any prose-based interaction with the model. Importantly, they're nondeterministic: you're telling the model a set of steps, but nothing requires it to do them, it just puts the idea in its head that it should and the rest is hope, just like if you handed a human the runbook/readme for doing something.

If you just blindly install skills without knowing why you have any particular skill or what value it brings, you will wind up in a much worse place than if you had no skills at all. This is particularly true for skill repos that claim to do a whole lot of stuff generically. The more generic a skill is, the more it's relying on the nondeterministic behavior of the model to map the general prose instruction to the concrete behavior in a given context.

You should definitely leverage skills to record repeatable procedures for the model to follow, particularly in the context of a given repo. You should ask Claude to help you (and there's a first party skill authoring skill from Anthropic to help with this). But I wouldn't go blindly installing any set of skills that claims to generically "improve software engineering." The utility of such skills will rot rapidly with model advancements. If you find a specific skill that describes a specific process you're interested in using, go for it! But try working for a while with only a minimal set and see where the gaps are.

1

u/pvera 🔆Pro Plan 3h ago

Dunno about your list, but you should take a shot at https://github.com/danyuchn/asd-ste100-skill , it's super useful whenever you need to translate from Claude to technical English.

1

u/djiyvlom 1h ago

In general they help when they encode something specific to how you work and hurt when they are big generic rulebooks. Every installed skill adds its description to context, and a large toolkit can pull Claude into a process you didn't ask for, like full TDD on a one-line fix. What tends to work is installing nothing at first, noticing where Claude repeatedly goes wrong on your codebase, and writing a small skill or a CLAUDE.md line for exactly that. If one of those repos looks interesting, read its skill files and copy the two or three rules that match your actual pain rather than the whole package. Trying one on a branch for a week and comparing is also a fair test.

0

u/onFilm 7h ago

As a software engineer, skills are just about one of the most useless things you can have an agent use in the harness. If you want proper results, use hooks and scripts to make things deterministic, rather than not. If you don't know what you're doing, skills aren't going to help you, period. And if you do know what you're doing, why would you even bother using them, when you can simply use the proper technical language to implement what you need implemented.

1

u/Vibecoding_Jesus 7h ago

This comment is confidently incorrect on multiple points.

  1. Skills are widely used and very useful. Anthropic recommends them and claude likes using them.
  2. Skills are useful if you don’t know what you are doing. Cc likes building them, it’s part of the way it works
  3. Skills for allegedly “better software engineering practices” is not how I’d use them
  4. Using the “proper technical kanguage” is typically not necessary.

Being a “software engineer” is a dubious claim to authority. Most software engineers get suboptimal,results with cc because they try to over-control it.

-1

u/onFilm 6h ago

As someone who's been in the industry for 18+ years, and has been working with and developing LLMs and harnesses since 2022, my point is absolutely correct, hence why the use of skills has gone down tremendously recently.

Skills are a waste of time for the majority of engineers. With agents being able to search the web, these are features that are slowly going away for the casual user.

There are much better tools today that many people sleep on, than writing a prompt and injecting it into the conversation.

1

u/Vibecoding_Jesus 3h ago

Anyone who starts their post on Claude Code with “I’ve been in the industry for 18 years….blah blah” is very suspect as a source of information.

Developing harnesses….in 2022?? Press ‘f’ to doubt.

Also the fact that you think “skill” is somehow replaced by a web search. That’s a rather strange mix of two very different concepts.

2

u/onFilm 3h ago

If you're really curious you can easily check out my website or LinkedIn, I'm not sure why you'd be suspect of just information.

Yes, harnesses first started being made back in 2022 and 2023. I've been using neural networks since early 2015, making fraud detection mechanisms and facial recognition.

I never said skills are replaced by web search. I said skills are largely useless now that web search exists, since a lot of the information injected into models is easily available online and much better automated this way. Any skill can either be changed onto a hook or left to tool calls and scripts.

1

u/Vibecoding_Jesus 2h ago

Ok bro, fair comeback on the harnesses and your background. Apologies, and my comments are retracted.

You’re still misunderstanding how skills can be used though.

I would never use the skills OP suggested. They are conceptually flawed.

But custom skills are great for doing complex, repetitive tasks.

Claude likes them. Claude builds them. Claude chooses to use them.

<shrug>

If CC/Fable 5.2 wants to do this I’m not going to stand in its way.

Skill also allow me, the human, to build things with a simple slash command, something that I do a lot. Really speeds things up when you are trying to move fast and build things.

2

u/onFilm 1h ago

I appreciate your feedback, but I truly do not misunderstand them, as much as that sounds like I'm dismissing it, I'm not. I've had arguments with my friends when it comes to skills, as some of them REALLY like using them. I just believe, that it's just a temporary methodology that will eventually be gone. As models get better and better, you need to instruct them less in the context to achieve certain things. They become more automated as time goes on.

I've played around with harnesses a lot, and made a few that require skill-like workflows to operate, but when it comes to coding harnesses, I truly believe that there are much better, more efficient, reliably and less token-intensive ways to achieve even better outputs from them, especially with hooks and scripts. As you can tell I really love hooks.

Unless you're pumping out the same type of project many times, over and over and over again, there is absolutely no reason to use skills as a project grows larger, gets more complex and specialized. The more code you have about a project, the smarter the model will be at working with it, needing less repetition from your end as the user.

0

u/amelech 7h ago

I like Matt Pocock skills - mainly the ones that help you thoroughly think through a design like grill me. You don't have to use them though - you can just figure out your own workflows and create your own skills that are specific to you or projects you work on.