play
Skill1 starsChanged 3 months agoMITView on GitHub
Launch a stick man overlay game on top of your terminal. Walk with A/D, jump with W, aim and cast spells with the arrow keys. Press Shift+Q to quit.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- microsoft/Copilot-Managed-Runtimetheir own version, first seen Nov 8, 2026
- Playful-Sincerity/PSDCMS-Playful-Sincerity-Digital-Core-Meta-Systemtheir own version, first seen Oct 11, 2026
- kennethleungty/claude-musictheir own version, first seen Apr 10, 2026
- ericboy0224/learn-docker-and-k8stheir own version, first seen Mar 27, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- ericboy0224/learn-docker-and-k8s★ 472same name
- kennethleungty/claude-music★ 23same name
- microsoft/Copilot-Managed-Runtime★ 4same name
- Playful-Sincerity/PSDCMS-Playful-Sincerity-Digital-Core-Meta-System★ 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.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Do NOT use run_in_background for this command — the script already backgrounds the game process and returns quickly with a status check.
- Very specific: line 24
If the output contains STICK_AROUND_FAILED, or the binary is not found, tell the user to rebuild it by running make dev in the plugin …
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Launch the stick man overlay game by running:
"${CLAUDE_PLUGIN_ROOT}/stick-around" &
STICK_PID=$!
sleep 0.5
if kill -0 "$STICK_PID" 2>/dev/null; then
echo "STICK_AROUND_RUNNING pid=$STICK_PID"
else
echo "STICK_AROUND_FAILED"
fiDo NOT use run_in_background for this command — the script already backgrounds the game process and returns quickly with a status check. Running it in the foreground ensures you see the output.
If the output contains STICK_AROUND_RUNNING, tell the user: "Stick Around is running! A stick man is now walking on your screen. Controls: A/D to walk, W to jump, C to toggle prone, hold S to drill through the platform under you; E to aim the rope (release to throw, press E again to detach mid-swing); 1 toggles the shield, hold 2 to aim lightning (release to fire), hold 3 for stasis; arrow keys ←/→ sweep aim, ↑ casts the active spell, ↓ cycles to the next spell; Q cancels any active spell; F swings the axe to mine crystals; G burns a glowing ball to recharge the flashlight in the dark mission; Shift+R restarts the current mission; Escape hands focus back to your terminal (press Ctrl+Shift+G to grab it back); Shift+Q to quit." Note: the game continues running as a separate process even after the command finishes.
If the output contains STICK_AROUND_FAILED, or the binary is not found, tell the user to rebuild it by running make dev in the plugin directory.
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.

