How do I install the Status skill?

Run npx skillmds@latest add hashgraph-online/status-11 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Status skill do?

Show the current state of a run — stages, roles, write locks, and gates. It is listed under Coding & Dev Tools on SkillMD.

Is Status safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Status?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Status free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Status?

hashgraph-online (@hashgraph-online) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Status by hashgraph-online — Agent Skill

Name: Status
Rating: 4.5 (4 reviews)
Author: hashgraph-online

File contents

AgenTeam Status

Display the current state of the team's work.

Process

1. Get Status

Use the --progress flag for a compact, human-friendly view:

python3 <runtime>/agenteam_rt.py status --progress

If the user specifically asks for raw JSON state, use without --progress:

python3 <runtime>/agenteam_rt.py status

2. Format Output

Display the progress view in a readable format:

AgenTeam Run: <run-id>
Task: <task description>
Profile: <profile or "full">
Status: <running|completed|failed|stopped>
Elapsed: <Nm Ss>

Stages:
  research   ✓ completed  (0m 45s)
  strategy   ✓ completed  (0m 30s)
  design     ✓ completed  (1m 02s)
  implement  → verifying   (1m 15s)  [verify attempt 2/3]
  test       · pending
  review     · pending

Active Lock: dev
Last Event: stage_verified (implement) — fail, attempt 2
Attempt: implement-dev-a1 | thread_id: <codex-thread-id>
Last heartbeat: 12s ago | idle budget: 14m 48s remaining
Wall budget: 47m remaining | stop reason: (none)

The progress view includes elapsed times per stage, the current verify attempt if applicable, and the most recent event for context. When governance.adoption is present, include the high-signal governance items in the readable status: open follow-ups/escalations, recorded tripwire blocks or warnings, gate rejections, and criteria overrides. Do not ask the user to inspect raw .agenteam/governance files for these summary facts. For an active or interrupted attempt, always include thread_id (or "unavailable"), last heartbeat and age, idle budget and wall budget remaining, attempt/retry counts, PID liveness when known, and stop reason. Treat a stale heartbeat as AT RISK, not as proof that the role failed.

3. No Active Run

If no run is found, show:

Team config status (does .agenteam/config.yaml or legacy agenteam.yaml exist?)
Available roles
Suggestion: "Use $ateam:run to start a new task."

Symbols

✓ — completed
→ — in progress
· — pending
✗ — failed/blocked

Source: hashgraph-online/awesome-codex-plugins → plugins/yimwoo/codex-agenteam/skills/status/SKILL.md

---name: status-11description: Show the current state of a run — stages, roles, write locks, and gates.--- # AgenTeam Status Display the current state of the team's work. ## Process ### 1. Get Status Use the `--progress` flag for a compact, human-friendly view: ```bash python3 <runtime>/agenteam_rt.py status --progress ``` If the user specifically asks for raw JSON state, use without `--progress`: ```bash python3 <runtime>/agenteam_rt.py status ``` ### 2. Format Output Display the progress view in a readable format: ``` AgenTeam Run: <run-id> Task: <task description> Profile: <profile or "full"> Status: <running|completed|failed|stopped> Elapsed: <Nm Ss> Stages: research ✓ completed (0m 45s) strategy ✓ completed (0m 30s) design ✓ completed (1m 02s) implement → verifying (1m 15s) [verify attempt 2/3] test · pending review · pending Active Lock: dev Last Event: stage_verified (implement) — fail, attempt 2 Attempt: implement-dev-a1 | thread_id: <codex-thread-id> Last heartbeat: 12s ago | idle budget: 14m 48s remaining Wall budget: 47m remaining | stop reason: (none) ``` The progress view includes elapsed times per stage, the current verify attempt if applicable, and the most recent event for context. When `governance.adoption` is present, include the high-signal governance items in the readable status: open follow-ups/escalations, recorded tripwire blocks or warnings, gate rejections, and criteria overrides. Do not ask the user to inspect raw `.agenteam/governance` files for these summary facts. For an active or interrupted attempt, always include `thread_id` (or "unavailable"), last heartbeat and age, idle budget and wall budget remaining, attempt/retry counts, PID liveness when known, and stop reason. Treat a stale heartbeat as `AT RISK`, not as proof that the role failed. ### 3. No Active Run If no run is found, show: - Team config status (does `.agenteam/config.yaml` or legacy `agenteam.yaml` exist?) - Available roles - Suggestion: "Use `$ateam:run` to start a new task." ## Symbols - `✓` — completed - `→` — in progress - `·` — pending - `✗` — failed/blocked --- **Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/yimwoo/codex-agenteam/skills/status/SKILL.md`

Frequently asked questions

Status