I run Skill Harbor, an open directory of builds people made for their AI agents: skills, connectors, little tools, that kind of thing. The idea is boring on purpose. One place to find them, one listing that says what a build does, and an install prompt you copy into your own agent. Nothing installs itself behind your back. The part I worry about is that install prompt. You are basically letting a stranger tell your agent what to do, on your machine. So here is what we do on our side, and what we do not do. We do not audit the code in these builds, and we do not hand out a safe badge. Anyone who promises you that at this scale is selling you something. What we do is smaller, and dated. When a build downloads code from a public repo, the install grabs the exact commit we tested in our sandbox, not whatever the repo points to today. We scan the install prompt, and the listing says in plain words if it runs commands, talks to the network, installs packages, writes files, or uses API keys. We also list the hosts the install contacted during our test, and every night we recheck the fingerprints of what gets downloaded. If something changes, the listing gets flagged until a human looks at it. The full method is on the site under How we verify. We also try not to play gatekeeper. If a build looks made to help, we list it and label it as clearly as we can, so you can decide for yourself. If you have built something for your agent, you can list it there: theskillharbor.com. If you have not, I am curious what stops you from installing skills other people made. Is it the code, the prompt, or just not knowing what changed since the test? submitted by /u/toohightottype
Originally posted by u/toohightottype on r/ArtificialInteligence