I think people are looking at skills the wrong way. It's not like it gives it some kind of superpowers it couldn't do otherwise. Ideally you'll have Claude write the skills anyway. It's just a shortcut so you don't have to keep rewriting a prompt all over again and/or have Claude keep figuring out how to do the same thing repeatedly. You can save lots of time, tokens and manual guidance by having well thought skills.
Some people use these to "larp" some kind of different job roles etc and I don't think that's productive use of skills unless the prompts are truly exceptional.
replyI have sometimes found "LARPing job roles" to be useful for expectations for the codebase.
replyClaude is kind of decent at doing "when in Rome" sort of stuff with your codebase, but it's nice to reinforce, and remind it how to deploy, what testing should be done before a PR, etc.
If you build up and save some of those scripts, skills help Claude remember how and when to use them.
replySkills are crazy useful to tell Claude how to debug your particular project, especially when you have a library of useful scripts for doing so.