agentleFS
Sign inStart free
crisandrewscrisandrews/ClawCode/skills/status/SKILL.md

status

Skill64 starsChanged 2 months agoMITView on GitHub

Show agent runtime status — identity, model, context, memory, crons, voice. Works from CLI or messaging. Triggers on /status, /agent:status, "status del agente", "cómo estás técnicamente".

177 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use off, list and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • StakeholderSenseiSkill

    off

    Disable polygraph for this repo (user-only escape hatch; all hooks no-op)

    Also in 4 projects that use this

  • SuShuhengSkill

    list

    Use when checking obshare-cli upload history, finding document tokens, or reviewing previous upload URLs and permission snapshots.

    Also in 8 projects that use this

  • kennethleungtySkill

    pause

    Pause — stop the music (alias for /stop)

    Also in 6 projects that use this

  • genomewalkerSkill

    resume

    Resume a thread by loading its ~800-token context capsule

    Also in 15 projects that use this

  • stotihvSkill

    knowledge

    Extracts knowledge from Amp threads and updates project docs. Use when asked to document recent work, sync docs after an epic, summarize what changed, or update AGENTS.md from thread history.

    Also in 4 projects that use this

  • clearsmogSkill

    finish

    Master pipeline — compile, review, fix, and finalize any document. Auto-detects format and runs the full quality loop.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 146 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the file doesn't exist or is stale, fall back to "run /cost for details".

    line 42
  2. Distinctive:

    Keep it compact — one line per category, no paragraphs.

    line 74

“Common” is measured: kept by at least 6 in 10 of the 146 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.

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

/status — Runtime Status

Show a compact status card with everything the user needs at a glance. Works from CLI and messaging channels.

Output format

👽 <Name> <emoji>
🧠 Model: <model name> (e.g. Opus 4.6)
📊 Context: <used%> · Memory: <N> files, <M> chunks · <backend>
🕐 Crons: heartbeat <schedule>, dreaming <schedule>
🔊 Voice: <tts backend> (<enabled|disabled>)
📡 Channels: <active channels or "none">

Steps

  1. Call agent_status MCP tool — gives identity, memory stats, dream data.
  2. Call agent_config MCP tool (action='get') — gives backend, voice, http config.
  3. Get model name — you know your own model. Use the display name (e.g. "Opus 4.6"), not the internal ID.

  4. Get context + session usage — the statusline script writes the latest Claude Code runtime data to /tmp/claude-statusline-latest.json. Read it:

    cat /tmp/claude-statusline-latest.json 2>/dev/null

    This JSON contains:

    • model.display_name — current model (e.g. "Claude Opus 4.6 (1M context)")
    • context_window.used_percentage — context window usage (0-100)
    • rate_limits.five_hour.used_percentage — 5-hour session usage
    • rate_limits.five_hour.resets_at — epoch when session resets
    • rate_limits.seven_day.used_percentage — weekly usage
    • rate_limits.seven_day.resets_at — epoch when week resets

    If the file doesn't exist or is stale, fall back to "run /cost for details".

  5. Get cron info — Bash: jq '.entries | length' memory/crons.json 2>/dev/null || echo 0 to count active registry entries. Optionally: jq '[.entries[] | select(.paused == false and .tombstone == null)] | length' memory/crons.json for the expected-alive count.
  6. Get channel info — if channels_detect MCP tool is available, call it. Otherwise check ls ~/.claude/plugins/cache/ 2>/dev/null for installed plugins.
  7. Build the card using REAL data. Never fabricate numbers.

Format per surface

CLI

👽 **Wally** 👽
🧠 Model: Opus 4.6 (1M context) · Context: 23%
📊 Memory: 42 files, 120 chunks · builtin (QMD vsearch)
⏱️ Session: 15% (3h 20min left) · Week: 8% (Resets Fri, 6:00AM)
🕐 Crons: heartbeat */30, dreaming 3am
📡 Channels: whatsapp (connected)

WhatsApp

Same content, *bold* instead of **bold**. No markdown headers.

Telegram

Same content, **bold** is fine.

Important

  • PURELY informational — does not modify state.
  • Get REAL data from MCP tools and filesystem. Never fabricate.
  • For detailed cost/token info, tell the user to run native /cost or /usage.
  • For MCP server details, tell the user to run native /mcp.
  • Keep it compact — one line per category, no paragraphs.

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.

Check your setup, free