unlock
Skill2 starsChanged 5 months agoApache-2.0View on GitHub
Use to force-clear the Volley STATE lock when something has gone wrong - Codex's terminal crashed, was closed, or otherwise left STATE in a bad state. Confirms with the user before clearing. The escape hatch from the concurrency model.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- tboome33/obsidian-mcp-routertheir own version, first seen Nov 15, 2026
- chris-santiago/ml-wikitheir own version, first seen Jul 16, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- tboome33/obsidian-mcp-router★ 1same name
- chris-santiago/ml-wiki★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- diagnoseSkill
- implementSkill
- review-codeSkill
- review-planSkill
- review-prSkill
- setupSkill
- statusSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Wait for user response. Anything other than yes aborts.
≈ “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
/volley:unlock
Force-clear the lock. The escape hatch.
Steps for Claude
- Read current STATE and show the user.
[ -f .volley/STATE ] || { echo "ERROR: .volley/STATE not found. Run /volley:setup first." >&2; exit 1; } . "${CLAUDE_PLUGIN_ROOT}/scripts/lib.sh" echo "Current STATE:" cat .volley/STATE echo "" AGE=$(volley_state_lock_age .volley/STATE 2>/dev/null) && echo "Lock age: ${AGE}s" || echo "Lock age: unknown" Confirm with the user. Output:
"Force-clear this lock? STATE will be reset to ACTIVE=claude, TASK=idle, PID=0. Any work Codex was doing in a terminal tab will NOT be stopped automatically - you'll need to close that tab manually if you want Codex to stop. Confirm with 'yes' to proceed, or 'no' to abort."
Wait for user response. Anything other than
yesaborts.- Reset STATE.
. "${CLAUDE_PLUGIN_ROOT}/scripts/lib.sh" volley_state_write .volley/STATE claude idle 0 echo "Lock cleared." - Print the next-step block.
. "${CLAUDE_PLUGIN_ROOT}/scripts/lib.sh" volley_next_step "/volley:status" "Verify the lock is clear and Claude is the active actor."
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.

