dev-install
Skill4 starsChanged 9 months agoMITView on GitHub
Run install/uninstall/status CLI commands for local development
1 other project uses a version of this.
Adopted by
Most recently taken up by
- n2ns/hyper-handtheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- n2ns/hyper-hand★ 5same 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 repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- clear-cacheSkill
- statusline-checkSkill
- test-statuslineSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 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.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Run the CLI command based on $ARGUMENTS:
- Very specific: line 22
If $ARGUMENTS is empty, default to status.
- Distinctive: line 26
After the command completes, verify the result:
- Very specific: line 29
Check ~/.claude/statusline.sh exists: ls -la ~/.claude/statusline.sh
- Very specific: line 30
Check ~/.claude/settings.json contains statusLine key: read the file and confirm the statusLine configuration is present
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Dev Install
Quick shortcut to run the CLI during local development.
Instructions
Run the CLI command based on $ARGUMENTS:
node bin/cli.js $ARGUMENTSIf $ARGUMENTS is empty, default to status.
Post-run Verification
After the command completes, verify the result:
After install
- Check
~/.claude/statusline.shexists:ls -la ~/.claude/statusline.sh - Check
~/.claude/settings.jsoncontainsstatusLinekey: read the file and confirm thestatusLineconfiguration is present
After uninstall
- Confirm
~/.claude/statusline.shis gone:ls ~/.claude/statusline.sh 2>&1 - Confirm
statusLinekey removed from~/.claude/settings.json: read the file and check
After status
Just display the output — no additional checks needed.
Report what happened and whether verification passed.
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.

