aio-proof
Skill0 starsChanged 31 days agoMITView on GitHub
Collect reproducible backend acceptance evidence bound to source and candidate artifacts.
In this repository54 other files it gives its agents.
- agent-workflowsSkill
- aio-agentsSkill
- aio-algorithmsSkill
- aio-apiSkill
- aio-architectureSkill
- aio-autoplanSkill
- aio-benchmarkSkill
- aio-brainstormSkill
- aio-canarySkill
- aio-checkpointSkill
- aio-ciSkill
- aio-commitSkill
- aio-compoundSkill
- aio-dataSkill
- aio-debugSkill
- aio-devex-reviewSkill
- aio-doc-reviewSkill
- aio-explainSkill
- aio-feedbackSkill
- aio-handoffSkill
- aio-ideateSkill
- aio-observeSkill
- aio-optimizeSkill
- aio-pipelinesSkill
- aio-plan-reviewSkill
- aio-planSkill
- aio-prototypeSkill
- aio-qa-onlySkill
- aio-qaSkill
- aio-releaseSkill
- aio-resumeSkill
- aio-reviewSkill
- aio-securitySkill
- aio-shipSkill
- aio-simplifySkill
- aio-specSkill
- aio-tddSkill
- aio-test-auditSkill
- aio-testSkill
- aio-verifySkill
- aio-workSkill
- aio-worktreeSkill
- all-in-oneSkill
- apple-appstore-reviewerSkill
- backend-algorithmsSkill
- backend-debugSkill
- backend-pipelinesSkill
- backend-planSkill
- backend-reviewSkill
- backend-verifySkill
- complete-destructionSkill
- launch-readinessSkill
- play-policy-insightsSkill
- reverse-engineer-anythingSkill
The file
Files
AIO Proof
Collect reproducible backend acceptance evidence bound to source and candidate artifacts.
Protocol
- Choose the claim and R/V IDs, exact source/revision/build and observation boundary. Determine which evidence needs local tests, a real provider, live service or console access.
- Execute the relevant checks and save raw commands, environment, timestamps, exit status and assertions without secrets. Distinguish mocks/synthetic fixtures from operational proof.
- Bind artifacts to hashes and verify links/files resolve under the workspace. Inspect remote PR/deploy/service state separately; do not turn arbitrary local files into proof of remote success.
- Package a minimal evidence dossier and run the appropriate completion/launch gates. Any unavailable required observation stays unverified and goes to aio-verify.
Return and handoff
A source-bound reproducible proof dossier with actual observations and precisely limited claims.
In a pipeline, use the stage contract and return to the integrating controller. Run only this specialist's owned scope; preserve the user's accepted decisions and existing authorization.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.