test-statusline
Skill4 starsChanged 9 months agoMITView on GitHub
Test statusline.js with mock JSON input and validate output
In this repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- clear-cacheSkill
- dev-installSkill
- statusline-checkSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Run scripts/statusline.js with mock JSON input to verify output formatting and color-coded progress bars.
- Very specific: line 39
If $ARGUMENTS is empty, run all four scenarios above sequentially and compare outputs.
- Distinctive: line 46
No errors or crashes in stderr
≈ “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
Test statusline.js
Run scripts/statusline.js with mock JSON input to verify output formatting and color-coded progress bars.
Instructions
Based on $ARGUMENTS, pick one of these test scenarios:
low — Low usage (all green)
echo '{"model":{"display_name":"Claude Opus 4"},"cost":{"total_cost_usd":0.12},"context_window":{"used_percentage":25},"workspace":{"current_dir":"/Users/test/my-project"},"session_id":"test-low"}' | node scripts/statusline.jsmedium — Medium usage (yellow zone)
echo '{"model":{"display_name":"Claude Sonnet 4.5"},"cost":{"total_cost_usd":1.87},"context_window":{"used_percentage":75},"workspace":{"current_dir":"/Users/test/big-refactor"},"session_id":"test-medium"}' | node scripts/statusline.jshigh — High usage (red zone)
echo '{"model":{"display_name":"Claude Opus 4"},"cost":{"total_cost_usd":5.42},"context_window":{"used_percentage":95},"workspace":{"current_dir":"/Users/test/marathon-session"},"session_id":"test-high"}' | node scripts/statusline.jsnull — Null/missing values (fallback handling)
echo '{"model":{},"cost":{},"context_window":{},"workspace":{},"session_id":"test-null"}' | node scripts/statusline.jsNo argument — Run all scenarios
If $ARGUMENTS is empty, run all four scenarios above sequentially and compare outputs.
Validation
After running, verify:
- Line 1 contains model name (or
?for null), folder name, and cost - Line 2 contains context progress bar with percentage
- No errors or crashes in stderr
- Null scenario shows safe fallbacks:
[?],$0.0000,0%
Report PASS/FAIL for each check.
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.

