if-ok
Skill2 starsChanged 10 days agoMITView on GitHub
Queue a message that runs after Claude finishes the whole turn, but only if the work before it succeeded.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
If you skip it, do none of it.
- Distinctive: line 16
If the work succeeded, do what the message asks.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
This message was queued to run only if the work you just finished went well.
First look back at that work in this conversation. Skip the message if any of these happened:
- a test, build, lint or other check failed
- a command you ran returned an error that you didn't fix
- you stopped before finishing, or said something is still broken or left to do
If you skip it, do none of it. Reply with one line that starts with "Skipped:" and gives the reason. If the work succeeded, do what the message asks.
Message: $ARGUMENTS
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.