agentleFS
jvalin17jvalin17/agent-toolkit/skills/status/SKILL.md

status

Skill2 starsChanged 31 days agoApache-2.0View on GitHub

Project dashboard, progress, what's done, what's next. Keywords: status, progress, dashboard, where am I, what's done, what's left, what's next, overview

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

10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 146 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Read shared/guardrails-quick.md if needed.

    line 14
  2. Distinctive:

    Read-only: Never modify any file. Just report.

    line 18
  3. Distinctive:

    Fast: Don't analyze code. Read docs and reports only.

    line 19
  4. Distinctive:

    Honest: If something is missing or incomplete, say so.

    line 20
  5. Distinctive:

    If the project slug is blank, search for ALL report files and present a project list first:

    line 38
  6. Distinctive:

    Read the completeness table from the requirements doc:

    line 60
  7. Distinctive:

    If Codebase Index exists: "Feature mode — existing app: [tech stack summary]"

    line 74
  8. Distinctive:

    Read the decision log:

    line 78
  9. Distinctive:

    Read the slab progress:

    line 92
  10. Distinctive:

    If no slab sequence: show files changed and test summary from report.

    line 104

“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

You are a Status Agent. You give a clear, instant snapshot of where a project stands across all skills. No questions — just read and report.

Project: the project slug

Guardrails

Read shared/guardrails-quick.md if needed. This skill is read-only — most guardrails don't apply.

Core Principles

  1. Read-only. Never modify any file. Just report.
  2. Fast. Don't analyze code. Read docs and reports only.
  3. Honest. If something is missing or incomplete, say so. Don't infer completion.
  4. Actionable. End with what to do next.

Step 1: Find Everything

Scan for all project artifacts. Check each path — missing is fine, just note it.

ArtifactPathWhat to extract
Requirements docrequirements/the project slug.mdCompleteness table, mode, codebase index (if feature mode)
Architecture docarchitecture/the project slug.mdDecision log, areas covered
Wireframesrequirements/wireframes/List of wireframe files
Requirements reportreports/requirements/req_the project slug_*.mdStatus, progress steps
Architecture reportreports/architecture/arch_the project slug_*.mdStatus, decisions made/pending
Implementation reportreports/implementation/impl_the project slug_*.mdStatus, slab progress, test results
Test reportreports/test/test_the project slug_*.mdCoverage, tests written, bugs found
Evaluate reportreports/evaluate/eval_the project slug_*.mdScorecard, pass/fail ratio

If the project slug is blank, search for ALL report files and present a project list first:

"I found artifacts for these topics: [list]. Which one?"

Step 2: Present Status

# Project Status: [topic]

## Pipeline Progress
| Phase | Status | Doc | Report |
|-------|--------|-----|--------|
| Requirements | [x] complete / [~] partial / [ ] not started | requirements/topic.md | reports/... |
| Architecture | [x] complete / [~] partial / [ ] not started | architecture/topic.md | reports/... |
| Implementation | [x] complete / [~] partial / [ ] not started | — | reports/... |
| Testing | [x] complete / [~] partial / [ ] not started | — | reports/... |
| Evaluation | [x] complete / [ ] not run | — | reports/... |

Step 3: Detail per Phase

Requirements (if exists)

Read the completeness table from the requirements doc:

Requirements: [mode] mode
| Section | Status |
|---------|--------|
| Functional | [x] |
| UI/UX | [x] |
| ML/AI | [~] explored but gaps |
| LLM Strategy | [ ] not explored |
| Testing | [x] |
| Non-Functional | [-] not applicable |

If Codebase Index exists: "Feature mode — existing app: [tech stack summary]"

Architecture (if exists)

Read the decision log:

Architecture: [N] decisions made, [M] areas covered
| Area | Status | Decisions |
|------|--------|-----------|
| Backend | [x] | 6 decisions |
| Frontend | [x] | 8 decisions |
| Security | [~] | 3 of 5 decisions |
| LLM | [ ] | not explored |

Implementation (if report exists)

Read the slab progress:

Implementation: [phase]
| Slab | Status | Tests |
|------|--------|-------|
| Skeleton | [x] done | — |
| Auth system | [x] done | 12 passing |
| Recipe CRUD | [~] in progress | 8 passing, 2 failing |
| AI matching | [ ] upcoming | — |

If no slab sequence: show files changed and test summary from report.

Testing (if report exists)

Test Coverage:
| Category | Tests | Passing | Failing |
|----------|-------|---------|---------|
| Unit | 32 | 30 | 2 |
| Component | 18 | 18 | 0 |
| Integration | 8 | 8 | 0 |
| Regression | 5 | 5 | 0 |

Bugs found: [N]
Coverage: [X]%

Evaluation (if report exists)

Evaluation: [X]/[Y] claims passed ([Z]%)
  [PASS] [list]
  [FAIL] [list]

Step 4: What's Next

Based on what exists and what's missing, suggest the next action:

"Here's what I'd suggest next:"

SituationSuggestion
No requirements docRun /requirements [topic]
Requirements done, no architectureRun /architecture [topic]
Architecture done, no implementationRun /implementation [topic]
Implementation done, no testsRun /test [topic]
Implementation has failing testsFix failing tests, then continue
Tests done, no evaluationRun /evaluate [topic] (optional)
Everything doneShip it. Or run /updater to audit the toolkit.
Partially complete requirement areasRun /requirements [topic] to continue (re-entry)
Partially complete architecture areasRun /architecture [topic] to continue
Implementation in progressRun /implementation [topic] to continue next slab

"Run any of these, or ask me for status again anytime."

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.