Author one job
Use the current spec and keep the purpose, expected outcome and Done means narrow enough to test.
FOR CREATORS · OPEN CONTRIBUTION
Submit work others
can inspect
Skills and MCP tools cannot be invented inline. Every executable dependency needs an inspectable source, and every Loadout must pass the validator before review.
SUBMISSION FLOW
From file to public review
The process is inspectable from the first validation result to the final decision.
Validate the file
Run the reference validator. Fix both schema errors and semantic safety failures.
Attach evidence
Provide source URLs, license, supported clients, test notes and a representative output sample.
Open a public review
Submit through GitHub so other people can inspect the file, dependencies and review history.
REQUIRED EVIDENCE
A link alone is not enough
Make it possible for a stranger to repeat the review.
- Valid `.loadout.md` file
- Creator, version and content license
- Inspectable Skill and MCP source URLs
- Supported-platform claim with evidence
- Risk and approval declaration
- No secrets, tokens, cookies or private data
- Output contract and structured fallback
- One representative result or test note
TRUST
Review status lives outside the file
A Loadout cannot verify itself.
01
External Unverified
A source exists, but AILoadout and the community have not completed review.
02
Community Reviewed
Review evidence is attached to an immutable artifact hash.
03
Verified
A detached registry attestation—not a label authored inside the file.
AUTOMATIC REJECTION
Unsafe or unverifiable submissions
Fix these before opening an issue.
- Invented or inline executable Skill/MCP content
- A repository link with no stable artifact or license
- Claims of support with no client/surface information
- Secrets or instructions to paste credentials into chat
- Mass-generated near-duplicate submissions