A community skill runs inside your Claude, so adding one is a real trust decision — not a free freebie. Here are the five checks that take two minutes and keep a bad skill out.
When you install someone else's skill, you're letting their instructions and code run inside your Claude, with access to your tools and files. That's the same trust question you'd ask before running any script you found online. 'Free' and 'popular' are not the same as 'safe.'
This isn't a reason to avoid community skills — they're one of the best parts of the ecosystem. It's a reason to spend two minutes vetting before you click install.
Look at who made it. Is it a real account with a track record, or anonymous and brand-new? Is the project actively maintained — recent updates, open issues being answered — or abandoned a year ago? A trusted maintainer and a living project are the strongest, cheapest signals you have.
Stars and downloads help, but they're not proof. Plenty of low-star skills are great and a few popular ones are sloppy. Use them as one input, not the verdict.
A good skill asks for the minimum it needs. Check the tools and files it wants access to, and whether it reaches out to the internet. A skill that fixes your grammar has no business requesting your whole drive or phoning home to an unknown server.
If the permissions are wider than the job, that mismatch alone is a reason to pass.
Reasonable for a writing skill: tools: read, edit network: none scope: this document Suspicious: tools: everything network: unknown server
Before you point a new skill at anything that matters, run it on throwaway files in a scratch folder and watch what it does. If it behaves — only touches what it should, no surprise network calls — promote it to real work. If anything feels off, delete it.
Five checks, two minutes: source, maintainer, permissions, network, sandbox test. That's the whole routine.
A two-minute checklist to run before installing any community skill or plugin — so a bad one never reaches your real files.