agentleFS
Sign inStart free
wrg32786wrg32786/aigent-os/skills/status/SKILL.md

status

Skill25 starsChanged 7 days agoMITView on GitHub

Report aigent-OS operational status. Use when checking the current operational state of aigent-OS.

177 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

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

  • 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

  • stotihvSkill

    knowledge

    Extracts knowledge from Amp threads and updates project docs. Use when asked to document recent work, sync docs after an epic, summarize what changed, or update AGENTS.md from thread history.

    Also in 4 projects that use this

  • clearsmogSkill

    finish

    Master pipeline — compile, review, fix, and finalize any document. Auto-detects format and runs the full quality loop.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 146 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read computed runtime state and display a concise operational summary.

    line 8
  2. Very specific:

    Run python3 "$AIGENT_VAULT/daemons/runtime/update-active-state.py" to refresh state

    line 16
  3. Very specific:

    If any reflexes are true, add a line: Reflex: {reflex} — {action hint}

    line 31
  4. Distinctive:

    Keep it tight. Terminal-style.

    line 40

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

Read computed runtime state and display a concise operational summary. Under 12 lines.

Trigger

/status — user-facing command. Also available to the AIgent internally.

Flow

  1. Run python3 "$AIGENT_VAULT/daemons/runtime/update-active-state.py" to refresh state
  2. Read $AIGENT_VAULT/memory/runtime/ACTIVE_STATE.json
  3. Format and display:
Mode:       {mode}
Objective:  {current_objective or "none"}
Next:       {next_valid_action or "none"}
Pressure:   context {p.context}, memory {p.memory}, token {p.token}
Capsule:    {active_capsule.id or "none"} ({active_capsule.status})
Blocked:    {count} items
Gaps:       {count} open skill gaps
Reflexes:   {list of true reflexes, or "none"}
  1. If any reflexes are true, add a line: Reflex: {reflex} — {action hint}
    • should_capsule → "Context pressure high — capsule recommended"
    • should_digest → "Memory backlog >30 — /digest recommended"
    • should_skill_hunt → "Open skill gaps — /skill-hunt queued"
    • should_close → "Session >2hr — consider /close"
    • should_escalate → "Blocked items — escalation needed"

Output format

Keep it tight. Terminal-style. No prose. No headers. Just the state.

Example

Mode:       active
Objective:  Build runtime state layer
Next:       Wire /open and /close to read ACTIVE_STATE
Pressure:   context low, memory medium, token low
Capsule:    2026-05-08-session38-close (active)
Blocked:    0 items
Gaps:       0 open
Reflexes:   digest — Memory backlog >30

Related

  • memory/runtime/ACTIVE_STATE.json — the state this reads
  • memory/runtime/README.md — schema docs
  • daemons/runtime/update-active-state.py — the computer
  • /body-check — deeper vital signs (somatic layer)
  • /open and /close — compute state as part of session lifecycle

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