agentleFS
Sign inStart free
BuddhiliveBuddhilive/buddhi-cli/.agents/skills/status/SKILL.md

status

Skill1 starsChanged 14 days agoMITView on GitHub

Report a quick, point-in-time dashboard of this harness's own state — docs/graph staleness, open plans, memory budget & staleness, and git status — rather than live agent sessions or a preview server. Use when checking harness health and status with /status.

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 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

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

  • 0

    Common

    Most of the 146 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run buddhi docs plan (via terminal-runner) — the same command /document-codebase and /spec-plan already run first — then read …

    line 18
  2. Very specific:

    Check .buddhi/graphs/ for tree-graph.json / tree-graph.db: report whether they exist and, if tree-graph.json is present, its node and edge …

    line 22
  3. Very specific:

    Run buddhi memory status (or buddhi_memory(action="status")) to report:

    line 26
  4. Very specific:

    Run git branch --show-current and git status (via terminal-runner) and report the current branch plus a short working-tree summary.

    line 30

“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

$ARGUMENTS

A quick dashboard of the harness's own generated state, not the project it documents. Nothing here is written to disk.

Steps

  1. Run buddhi docs plan (via terminal-runner) — the same command /document-codebase and /spec-plan already run first — then read .buddhi/docs-plan.json and report its total entries and how many have needs_generation: true, i.e. how many docs are stale relative to source.
  2. Check .buddhi/graphs/ for tree-graph.json / tree-graph.db: report whether they exist and, if tree-graph.json is present, its node and edge counts.
  3. List active feature specifications under .buddhi/specs/.
  4. Run buddhi memory status (or buddhi_memory(action="status")) to report:
    • Total OKF concepts by kind.
    • MEMORY.md line count and byte size vs. the strict 200-line / 25KB cap.
    • Any stale concepts (sources[].content_hash mismatch).
  5. Run git branch --show-current and git status (via terminal-runner) and report the current branch plus a short working-tree summary.
  6. Present all of the above as one concise status report in the conversation.

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