trio-ship
Skill2 starsChanged 26 days agoMITView on GitHub
Recover an orphaned SHIP verdict — perform the Evaluator's retirement commit (product + mailbox) when a SHIP's commit: lines are missing. No subagent, no model config.
In this repository6 other files it gives its agents.
- trio-initSkill
- trioSkill
- trio-claudeSkill
- trio-initSkill
- trio-productionizeSkill
- trioSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 1 is distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
If a verdict says SHIP but those commits never landed (a legacy or orphaned run), recover it yourself — the same two-commit pattern, using …
- Very specific: line 14
Mailbox directory: default loop/. If invoked with dir=<path>, that directory is the mailbox — every loop/ reference below means it.
- Very specific: line 17
Read loop/VERDICT.md. Its first non-empty line must be VERDICT: SHIP.
- Very specific: line 21
Check git status. Clean tree → there is no product commit to make.
- Very specific: line 23
Commit the product changes attributable to the loop in one commit: git add <those paths> then git commit -m "slice(<id>): <summary>" (the …
- Very specific: line 30
Commit the mailbox: git add loop/ then git commit -m "loop: iteration N — SHIP" (iteration N from STATE.md).
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
A SHIP verdict normally ends with the Evaluator's retirement commit: one
product commit slice(<id>): <summary> plus one mailbox commit
loop: iteration N — SHIP, recorded as commit: lines in loop/VERDICT.md.
If a verdict says SHIP but those commits never landed (a legacy or orphaned
run), recover it yourself — the same two-commit pattern, using the verdict's
own suggested commit message. No subagent and no model config: you run the git
commands directly.
Mailbox directory: default loop/. If invoked with dir=<path>, that
directory is the mailbox — every loop/ reference below means it.
- Read
loop/VERDICT.md. Its first non-empty line must beVERDICT: SHIP; otherwise STOP and tell the user the verdict is not machine-readable. - Take the suggested commit message from the verdict's
## Guidance for next iterationsection. - Check
git status. Clean tree → there is no product commit to make; recordcommit: <HEAD sha>and jump to step 6. - Commit the product changes attributable to the loop in one commit:
git add <those paths>thengit commit -m "slice(<id>): <summary>"(the suggested message, shaped to the slice convention; other slice ids in the body). Leave unrelated changes uncommitted and flag them to the user — never sweep foreign paths in. - Append
commit: <product sha>toloop/VERDICT.md. - Commit the mailbox:
git add loop/thengit commit -m "loop: iteration N — SHIP"(iteration N from STATE.md). - Confirm and report both shas to the user (
git rev-parsethe product commit and the mailbox commit).
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.

