Skip to content

donaldfilimon/abi / .agents/skills/agent-status-reporter

agent-status-reporter

Verified

Report current agent/session status and system health — skill-loop run state, scheduler/memory counters, and active context. Use when the user runs /status in the abi REPL or asks what the agent is doing or for system health.

agent-status-reporter

Backs the /status slash command in the agent tui REPL (opencode.json slash-command entry status). Reports a compact, read-only snapshot:

What to report

  1. Skill-loop run state — read the last entry of .skill-telemetry/runs.jsonl and .skill-telemetry/.sessions/ for the active session id + status. Summarize the latest run's status + counts; do not dump the file.
  2. Scheduler / memory — run abi scheduler status (one-shot self-terminating probe): report counters + attached MemoryTracker stats + the always-on telemetry block. The probe is a no-op, so memory counters read 0 by design — say so; do not fabricate load.
  3. Context — give one line: loaded files + whether SEA mode is on (from sea-learning-controller). Defer the full context view to context-state-reporter (/context).

Rules

  • Read-only. Never edit source, telemetry, or session files.
  • No performance / accuracy claims without a repo benchmark.
  • If a telemetry file is missing, report "not initialized" — do not invent.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall