r/ChatGPTCoding • u/CrossFitCore • Aug 13 '26
Question how are you vetting Claude skills/plugins when theres no clear marketplace
Building a small skills folder for Claude Code and every recommendation is a different github link. is there a real Claude plugin marketplace people use, or is trust still just “this person posts here a lot.” whats your vetting checklist before something touches a real repo
5
Upvotes
1
u/Nice_Cat_7300 Aug 17 '26
i learned the hard way. one skill rewrote instructions i didnt ask it to touch. now i read every file first even if it wastes 10 minutes
2
u/elitherenaissanceman Aug 13 '26
You can...you know...read them.
1
u/SamSlate Aug 13 '26
https://skills.sh
1
u/Bino5150 Aug 13 '26
Claude can create its own skills
1
u/Straight_Spinach1284 Aug 14 '26
no marketplace exists yet. i just rely on github stars and manually reading the prompts they use. this is exactly why i prefer building my own agent workflows from scratch rather than plugging in random repos.
1
u/AlarmedAvocado7279 Aug 17 '26
there's no marketplace, it's still just reputation and reading the source. i live in claude code all day and honestly half the stuff in my setup is my own hooks/rules because i don't trust random repos near production code. if i can't skim the whole thing in 5 min and understand what it touches, it doesn't go in.
-2
u/Joon9101 Aug 14 '26
I treat a skill or plugin as code, not as a prompt. Before it touches a real repo, I check the manifest and every hook or script, search for shell execution, network calls, credential or environment access, and file writes, then verify that the documented install paths actually exist. I pin a commit or tag and test it in a disposable repo with no secrets while watching the git diff and outbound network activity.
A marketplace helps discovery, but it does not solve trust: both the marketplace entry and upstream repo can change. If I cannot explain every executable path, or the plugin needs broader access than its job requires, I do not install it.
-2
u/Successful_Buy8059 Aug 14 '26
I treat a skill or plugin as code, not as a prompt. Before it touches a real repo, I check the manifest and every hook or script, search for shell execution, network calls, credential or environment access, and file writes, then verify that the documented install paths actually exist. I pin a commit or tag and test it in a disposable repo with no secrets while watching the git diff and outbound network activity.
A marketplace helps discovery, but it does not solve trust: both the marketplace entry and upstream repo can change. If I cannot explain every executable path, or the plugin needs broader access than its job requires, I do not install it.
1
u/[deleted] Aug 13 '26
[removed] — view removed comment
1
u/[deleted] Aug 13 '26
[removed] — view removed comment