Read the code. Check the signature. Then decide.
The commons publishes source code that a machine checked. That is a useful thing to know and it is not the same as trust. Here is exactly what we do, what we see and what stays yours.
What actually runs on my machine
A skill is a small file of plain source code in the language it says it is. There is no binary, no installer and no background service. You can read the whole thing on its page before you install it, and the page shows the same bytes the certificate covers.
What leaves my machine
Reading and searching the shelf sends only your query. Installing a skill is a download. Running one is entirely local to wherever your model runs. We never receive your files, your prompts or your outputs.
What a forge sees
If you pay us to forge a skill on your own failing context, we see what you send us: the task description and the example specifications you choose to include. Send redacted examples. We do not want your production data and we do not need it to build a helper.
How a certificate works
Every listed skill carries a sha256 of its code and an ed25519 signature over that hash and its evidence. The verify endpoint recomputes the hash from the stored code and checks the signature against the embedded public key. A mismatch means the code changed after signing, and you should not run it.
What the evidence means, and what it does not
Each evidence line names the held-out set, the executor and the measured scores. It says the code passed an exact checker on cases it never saw. It is not a security audit and it is not a promise about your inputs. Read the code.
Running code a model wrote
Treat a skill the way you would treat any dependency from a stranger. Run it in whatever sandbox your harness already uses, give it no credentials it does not need, and keep it away from anything you cannot afford to lose. Nothing about a signature makes untrusted code safe to run as an administrator.
Contributions
Sharing is opt in, per skill. A contributed skill is re-checked with the same gates before it is listed, and it is signed only if it passes. We take the helper code and its usage guide, never your files or your keys.
Reporting a problem
If you find a skill that misbehaves, a certificate that does not verify or a flaw in the API, email kyle@simgen.dev with the skill id and what you saw. Please do not open a public issue for anything that puts other people at risk before we have had a chance to pull the rung.
Verify a skill yourself
curl -s https://api.neruva.io/v1/commons/rungs/<id>/code -o rung.py
curl -s -X POST https://api.neruva.io/v1/commons/verify \
-H "Content-Type: application/json" -d '{"id": "<id>"}'
# recompute the hash locally and compare it to code_sha256
python -c "import hashlib,sys;print(hashlib.sha256(open('rung.py','rb').read()).hexdigest())"The verify endpoint is public and needs no key. Clouthier Simulation Labs, Ontario, Canada.