agentleFS
Sign inStart free
Ormus-SolutionsOrmus-Solutions/ormus-agent-ops/skills/agent-status/SKILL.md

agent-status

Skill0 starsChanged 7 months agoMITView on GitHub

At-a-glance overview of an autonomous coding agent — health, running tasks, queue, fail rate. Use to answer "is the agent working and what's it doing?" in a single dashboard.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 1

    1. HermeticOrmus/ormus-agent-ops★ 0100% same

    Edited · 0

    None found.

    Wrote their own version · 1

    1. jiayi-ThE-CREATOR/macos-llm-agents★ 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.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If your agent exposes different endpoints, adapt the curl invocations below.

    line 26
  2. Very specific:

    Don't paginate failures here — that's /agent-triage's job.

    line 96
  3. Distinctive:

    Keep the dashboard one screen.

    line 97

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

/agent-status — Agent Status Dashboard

One screen. Health, queue, throughput, recent failures. No spelunking.

Prerequisites

Set these env vars (or pass via shell when invoking):

VarPurpose
AGENT_API_URLBase URL of the agent's HTTP API (e.g. https://agent.example.com or http://localhost:7777)
AGENT_API_TOKENBearer token for authenticated endpoints

The skill expects a task-queue-shaped agent that exposes endpoints roughly matching:

  • GET /api/health — health summary
  • GET /api/tasks?status=running — running tasks
  • GET /api/tasks?status=queued — queued tasks
  • GET /api/tasks?status=failed&since=24h — recent failures

If your agent exposes different endpoints, adapt the curl invocations below.

When invoked

Pull a single dashboard frame answering:

  1. Health — service up? DB reachable? Workers responsive?
  2. Active work — what's running right now (count + brief task summaries)
  3. Queue — how many queued, how long is the oldest
  4. Throughput — tasks completed in the last hour / 24h
  5. Failures — fail rate over last 24h, top 3 most recent failures
  6. Cost — if the agent tracks per-task spend, sum last 24h

Workflow

# 1. Health
curl -s -H "Authorization: Bearer $AGENT_API_TOKEN" "$AGENT_API_URL/api/health"

# 2. Running tasks
curl -s -H "Authorization: Bearer $AGENT_API_TOKEN" "$AGENT_API_URL/api/tasks?status=running"

# 3. Queue depth + oldest
curl -s -H "Authorization: Bearer $AGENT_API_TOKEN" "$AGENT_API_URL/api/tasks?status=queued&order=created_at"

# 4. Recent failures
curl -s -H "Authorization: Bearer $AGENT_API_TOKEN" "$AGENT_API_URL/api/tasks?status=failed&since=24h"

Output format

AGENT STATUS — <ISO timestamp>
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

HEALTH    [✓ healthy | ⚠ degraded | ✗ down]
  service: <up/down>
  workers: <N/M alive>
  db: <reachable/error>

ACTIVE    <N running>
  • <task-id> <slug> · running <duration>
  • <task-id> <slug> · running <duration>
  • <task-id> <slug> · running <duration>

QUEUE     <N queued | oldest <duration> ago>

LAST 24H  <N completed | <N failed> | <X.X% fail rate>

FAILURES  (last 3)
  • <task-id> <slug> — <error class> — <duration> ago
  • <task-id> <slug> — <error class> — <duration> ago
  • <task-id> <slug> — <error class> — <duration> ago

COST      $<amount> spent / 24h (if tracked)

NEXT      Recommended action: <triage failures / clear queue / nothing>
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

When to recommend follow-up

  • Fail rate >5% over last 24h → suggest /agent-triage
  • Queue depth >20 with oldest >1h → suggest investigation (worker stuck?)
  • Health degraded → suggest checking logs / restart
  • Workers <expected count → suggest checking process supervisor

Notes

  • The skill assumes a single agent. For multi-agent setups, set AGENT_API_URL per-invocation or run the skill once per agent.
  • Don't paginate failures here — that's /agent-triage's job. Show only the top 3.
  • Keep the dashboard one screen. If anything overflows, summarize and suggest the deeper-dive skill.

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