agentleFS
Sign inStart free
apinizerapinizer/agentnizer-cookbook/.claude/skills/status/SKILL.md

status

Skill2 starsChanged 4 months agoMITView on GitHub

Show the team's current state — daemon running? what tasks are in flight? which agent is on each task? Wraps team.sh status with optional drill-down.

187 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use off, list and 10 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

  • codebycoreySkill

    new

    Start a new change with a proposal. Use when starting a feature, creating a proposal, or beginning planned work.

    Also in 7 projects that use this

  • michaelenglandSkill

    import

    This skill should be used when the user wants to import an existing .pptx file into deckwright, bring in a PowerPoint that was created outside this tool, reverse-engineer a presentation for editing, or invoke /deckwright:import. Converts a .pptx into a PptxGenJS generation script so it can be edited and regenerated through the deckwright pipeline.

    Also in 5 projects that use this

  • genomewalkerSkill

    resume

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

    Also in 15 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 154 edited versions we read keep these.

  • 1

    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:

    When you see the same task ID on multiple rows with different OWNER columns, you're watching the parallel review fan-out.

    line 42

“Common” is measured: kept by at least 6 in 10 of the 154 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 — Team status

Usage:

/status                       # human-readable table
/status --json                # machine-readable

What it does

Calls ./team.sh status, which reads:

  • .state/locks/team.lock — daemon pid, started_at, uptime
  • .state/locks/team.paused — pause flag
  • .state/active.json — DAG of in-flight tasks
  • .state/completed.jsonl — last 5 completed tasks

And prints something like:

=== Team Status ===
Daemon: RUNNING (pid 47213, started 2026-04-27T14:32:00Z, uptime 0:14:22)

Active Tasks (1):
ID                        MODULE       STATUS         OWNER             UPTIME
20260427-1432-hlt         backend      reviewing      reviewer          0:01:23
20260427-1432-hlt         backend      reviewing      tester            0:01:23
20260427-1432-hlt         backend      reviewing      security_reviewer 0:01:23

Recent Completed (last 5):
ID                        MODULE       OUTCOME    DURATION   TOKENS
20260427-1240-cfg         shared       done       0:08:11    42k
20260427-1130-rbc         backend      done       0:11:42    63k
==============================

When you see the same task ID on multiple rows with different OWNER columns, you're watching the parallel review fan-out. That's the team's "wow" moment.

Per-task detail

team.sh status itself has no task-id drill-down. For the full timeline of one task — every handoff in .state/tasks/<task-id>/handoffs.jsonl plus the current meta.json — use /logs <task-id> instead.

Notes

/status is read-only. Safe to run any time. When the daemon has nothing to do it exits cleanly; "Daemon: STOPPED" with empty active tasks means the team finished its work.

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