agentleFS
yusufalikyncyusufalikync/ccs/.claude/skills/statusline-check/SKILL.md

statusline-check

Skill4 starsChanged 9 months agoMITView on GitHub

Health check and troubleshooting for installed statusline

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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
  1. Distinctive:

    Run a comprehensive health check on the installed statusline setup and provide troubleshooting guidance.

    line 11
  2. Distinctive:

    Run these checks in order and report results:

    line 15
  3. Very specific:

    Read ~/.claude/settings.json and verify:

    line 24
  4. Distinctive:

    Must be >= 18 (for fetch API support).

    line 33
  5. Distinctive:

    Should not return an error about item not found.

    line 46
  6. Distinctive:

    Should produce two lines of output without errors.

    line 58
  7. Very specific:

    If any check fails, provide specific fix instructions (e.g., ccs install, update Node.js).

    line 66

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Statusline Health Check

Run a comprehensive health check on the installed statusline setup and provide troubleshooting guidance.

Checklist

Run these checks in order and report results:

1. Script installed

ls -la ~/.claude/statusline.js

Expected: file exists and is readable.

2. Settings configured

Read ~/.claude/settings.json and verify:

  • statusLine key exists
  • command value references statusline.js
  • padding is set

3. Node.js version

node --version

Must be >= 18 (for fetch API support).

4. Credential access

macOS:

security find-generic-password -s "Claude Code-credentials" 2>&1 | head -3

Linux:

secret-tool lookup service "Claude Code-credentials" 2>&1 | head -3

Should not return an error about item not found.

5. Cache status

ls -la ${TMPDIR:-/tmp}/claude_usage_cache_*.json 2>/dev/null || echo "No cache files found"

Report count and age of cache files.

6. Quick smoke test

echo '{"model":{"display_name":"Test"},"cost":{"total_cost_usd":0},"context_window":{"used_percentage":50},"workspace":{"current_dir":"/tmp"},"session_id":"healthcheck"}' | node ~/.claude/statusline.js

Should produce two lines of output without errors.

Output Format

Present results as a checklist:

  • Check passed
  • Check failed — explain what's wrong and how to fix it

If any check fails, provide specific fix instructions (e.g., ccs install, update Node.js).

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.