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
- zaynram/scholartheir own version, first seen Nov 8, 2026
- hydra-db/hydradb-claude-codetheir own version, first seen Nov 8, 2026
- dsifry/metaswarmtheir own version, first seen Nov 8, 2026
- leinardi/adversarial-review-looptheir own version, first seen Nov 8, 2026
- emotixco/claude-skills-foundertheir own version, first seen Nov 8, 2026
- flung-official/flung-claude-plugintheir own version, first seen Nov 8, 2026
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.
StakeholderSenseiSkilloff
Disable polygraph for this repo (user-only escape hatch; all hooks no-op)
Also in 4 projects that use this
SuShuhengSkilllist
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
kennethleungtySkillpause
Pause — stop the music (alias for /stop)
Also in 6 projects that use this
codebycoreySkillnew
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
michaelenglandSkillimport
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
genomewalkerSkillresume
Resume a thread by loading its ~800-token context capsule
Also in 15 projects that use this
Other versions177 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 177
- anthropics/claude-for-legal★ 9.5ksame name
- microsoft/TokenEconomizer★ 5ksame name
- zereight/gitlab-mcp★ 2.1ksame name
- indranilbanerjee/digital-marketing-pro★ 934same name
- H-mmer/pentest-agents★ 815same name
- emotixco/claude-skills-founder★ 796same name
- me2resh/apexyard★ 542same name
- dsifry/metaswarm★ 426same name
- ffroliva/gflow-cli★ 367same name
- serithemage/serverless-openclaw★ 196same name
167 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- agent-toolkit-modeSkill
- architectureSkill
- assessSkill
- autopilotSkill
- debug_toolSkill
- evaluateSkill
- exploreSkill
- implementationSkill
- precommitSkill
- requirementsSkill
- reviewerSkill
- setupSkill
- updaterSkill
- verifySkill
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
- Very specific: line 14
Read shared/guardrails-quick.md if needed.
- Distinctive: line 18
Read-only: Never modify any file. Just report.
- Distinctive: line 19
Fast: Don't analyze code. Read docs and reports only.
- Distinctive: line 20
Honest: If something is missing or incomplete, say so.
- Distinctive: line 38
If the project slug is blank, search for ALL report files and present a project list first:
- Distinctive: line 60
Read the completeness table from the requirements doc:
- Distinctive: line 74
If Codebase Index exists: "Feature mode — existing app: [tech stack summary]"
- Distinctive: line 78
Read the decision log:
- Distinctive: line 92
Read the slab progress:
- Distinctive: line 104
If no slab sequence: show files changed and test summary from report.
“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.
Files
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
- Read-only. Never modify any file. Just report.
- Fast. Don't analyze code. Read docs and reports only.
- Honest. If something is missing or incomplete, say so. Don't infer completion.
- 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.
| Artifact | Path | What to extract |
| Requirements doc | requirements/the project slug.md | Completeness table, mode, codebase index (if feature mode) |
| Architecture doc | architecture/the project slug.md | Decision log, areas covered |
| Wireframes | requirements/wireframes/ | List of wireframe files |
| Requirements report | reports/requirements/req_the project slug_*.md | Status, progress steps |
| Architecture report | reports/architecture/arch_the project slug_*.md | Status, decisions made/pending |
| Implementation report | reports/implementation/impl_the project slug_*.md | Status, slab progress, test results |
| Test report | reports/test/test_the project slug_*.md | Coverage, tests written, bugs found |
| Evaluate report | reports/evaluate/eval_the project slug_*.md | Scorecard, 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:"
| Situation | Suggestion |
| No requirements doc | Run /requirements [topic] |
| Requirements done, no architecture | Run /architecture [topic] |
| Architecture done, no implementation | Run /implementation [topic] |
| Implementation done, no tests | Run /test [topic] |
| Implementation has failing tests | Fix failing tests, then continue |
| Tests done, no evaluation | Run /evaluate [topic] (optional) |
| Everything done | Ship it. Or run /updater to audit the toolkit. |
| Partially complete requirement areas | Run /requirements [topic] to continue (re-entry) |
| Partially complete architecture areas | Run /architecture [topic] to continue |
| Implementation in progress | Run /implementation [topic] to continue next slab |
"Run any of these, or ask me for status again anytime."
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
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.

