Trust
Checked by machine, before it goes on sale
Every capability on SkillsVault is checked automatically before it is published, and every new version is checked again before it replaces the last one. Nobody’s opinion decides whether a capability goes on sale: the checks do, and the results are on the capability’s page.
The listing
What the publisher declares has to be complete
A capability is published by the platform when every one of these passes. If one fails, the listing stays a draft and the publisher is told exactly which check failed.
- 01Identity: a name, a description, a category and a publisher.
- 02Commercial terms: a price, a billing interval, and licence terms that say what a licence grants and for how long.
- 03Declarations: what the capability needs before it can work, and what it may reach once it is running.
- 04Delivery: how it is delivered. A hosted capability is served from its published package, or declares its own service over https.
- 05Operations: a support policy, a maintenance policy, an update policy, and the known limitations.
- 06Trial terms: a trial says what it is and what it allows.
- 07Ownership: a capability may only contain its own publisher’s skills.
- 08Verification: the version on sale has passed the package checks below.
The package
Every version is checked, every time
When a publisher uploads a new version, it is checked before it is stored. These checks run on the version a customer would get, not on an older one.
- 01Format: it is a valid agent skill package, with the files where an AI tool expects them.
- 02Integrity: its checksum, its size and where it is stored are recorded, and the bytes are checked against that checksum whenever they are read.
- 03Safety: nothing that looks like a live secret or key, no file path that would escape the folder it is installed into, no encrypted entries, and nothing that unpacks to far more than it says (a “zip bomb”).
- 04Signed: SkillsVault signs a manifest of every version — what it is, what it grants, its checksum — so anyone can check on their own machine that the bytes are the ones that were published.
The category suite
Checks that fit what the capability does
A marketing capability, a financial analysis capability and a software deployment capability are not judged the same way. Each category has its own required checks on top of the universal ones.
- 01Every required check in the capability’s category has to pass.
- 02A check that does not apply is disclosed as not applying, with the reason. It is never quietly counted as a pass.
- 03A required check that could not be run is a failure, not a pass.
Hosted capabilities
Served, and checked on every use
Many capabilities are not downloaded at all: SkillsVault serves them to your AI tool each time they are used.
- 01A capability SkillsVault serves is read one request at a time, and the licence is checked on every single request. When a subscription ends, the next request is refused, and there is no copy on your machine to fall back on.
- 02A capability that runs on its publisher’s own service is checked against a sandbox, never against a customer’s systems, and only on the addresses its sandbox declares.
- 03For those, the checks confirm that a caller with no licence is refused, that the service reaches nothing it did not declare, and that a failed operation is not billed.
What the status means
Four states, said plainly
- 01Verified: the version on sale passed. The capability page shows the version tested, the date, and every check with its outcome.
- 02Being verified: a run on the version on sale is under way.
- 03Verification failed: the latest run did not pass. A failed update never replaces a working one: the previous passing release stays on sale.
- 04Not yet verified: the version on sale has not been through the checks. It is not marked on the catalogue, and its page says so.
When an update fails
The working version stays
- 01An update that fails its checks is not published.
- 02The previous passing release stays on sale, unchanged.
- 03The report is kept, the publisher sees which checks failed, and they can fix it and send it again.
- 04An administrator can approve a version that has not been verified at all. It is the one manual override, and every use of it is written to the audit log at the moment it happens.
What verification is not
What the checks cannot tell you
Verification checks what a machine can check. It is worth knowing where that stops.
- 01The checks confirm that a declaration is there and well formed. They cannot prove it is true: that a description is honest, that a list of permissions is complete, or that a support policy will be kept.
- 02They cannot tell you that a capability solves your particular problem. The reviews, the known limitations and the trial are there for that.
- 03Verified never means safe in every environment, or guaranteed to work everywhere.
Where to see it
Every report is public
Each capability page has a Verification panel with the version tested, the date and every check. An AI agent connected to SkillsVault can read the same report with the get_verification_report tool. How a licence is held and checked is on How the licence works.
See what a verified capability looks like
Each capability page shows its verification report, what it needs, what it may reach, and what it costs.