← ClaudeAtlas

agent-inspectlisted

Deep dive into a single task in an autonomous coding agent — details, log, events, dependencies, review verdict. Use when a task's behavior is mysterious or `/agent-triage` couldn't classify it.
HermeticOrmus/ormus-agent-ops · ★ 0 · AI & Automation · score 70
Install: claude install-skill HermeticOrmus/ormus-agent-ops
# /agent-inspect — Deep Task Inspection > When a task is weird, this is where you go. ## Prerequisites | Var | Purpose | |---|---| | `AGENT_API_URL` | Base URL of the agent's HTTP API | | `AGENT_API_TOKEN` | Bearer token | Endpoints used (adapt to your agent's API): - `GET /api/tasks/:id` — task metadata - `GET /api/tasks/:id/log` — execution log - `GET /api/tasks/:id/events` — event stream - `GET /api/tasks/:id/review` — review verdict (if your agent runs review) - `GET /api/tasks/:id/deps` — task dependencies / dependents ## Usage ``` /agent-inspect <task-id> ``` ## Workflow ### 1. Pull metadata ```bash curl -s -H "Authorization: Bearer $AGENT_API_TOKEN" \ "$AGENT_API_URL/api/tasks/<task-id>" | jq ``` Capture: status, prompt, model, project, created_at, updated_at, attempt count, parent task (if subtask), priority, cost. ### 2. Pull events timeline ```bash curl -s -H "Authorization: Bearer $AGENT_API_TOKEN" \ "$AGENT_API_URL/api/tasks/<task-id>/events" | jq ``` Build a timeline. Look for: - State transitions (queued → running → review → done/failed) - Retry attempts - Worker reassignments - Review pass/fail rounds - External events (was the agent restarted? did the worker die?) ### 3. Pull log ```bash curl -s -H "Authorization: Bearer $AGENT_API_TOKEN" \ "$AGENT_API_URL/api/tasks/<task-id>/log" ``` Read the **last 100 lines** for failures. For successful but mysterious tasks, scan for unusual patterns: long pauses, retries, tool errors, low-confidence