project-status
Skill0 starsChanged 9 days agoMITView on GitHub
Report the current project's repository state, recent work, brain QA health (if applicable), and pending handoff items. Use for session orientation or an on-demand project checkpoint.
15 other projects use a version of this.
Adopted by
Most recently taken up by
- fullstackhouse/skillstheir own version, first seen Nov 15, 2026
- odytrice/metaskillstheir own version, first seen Nov 15, 2026
- eranw2000/claude-maintenance-skillstheir own version, first seen Nov 8, 2026
- desertcache/agent-ostheir own version, first seen Nov 1, 2026
- lautioliver/barrilete-kittheir own version, first seen Nov 1, 2026
- MrEddieO/claude-skillstheir own version, first seen Oct 20, 2026
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- eranw2000/claude-maintenance-skills★ 8same name
- ozgurkarahan/ai-agent-memory★ 8same name
- lautioliver/barrilete-kit★ 6same name
- AJBcoding/claude-skill-eval★ 4same name
- korchasa/flowai★ 3same name
- Manshooo/astral-genesis★ 3same name
- fullstackhouse/skills★ 1same name
- odytrice/metaskills★ 1same name
- philpalmieri/engineering-manager-skills★ 1same name
- Tracebrain/mcp★ 1same name
5 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 repository66 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/bootstrap-project/resources/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- skills/bootstrap-project/resources/CLAUDE.mdCLAUDE.md
- act-tenetsSkill
- adversarial-reviewSkill
- annotate-screenshotSkill
- anti-hallucinationSkill
- ascii-chartSkill
- assess-brainSkill
- big-ideaSkill
- bootstrap-coreSkill
- bootstrap-projectSkill
- browser-toolsSkill
- chart-big-ideaSkill
- chart-interpretationSkill
- chart-vocabularySkill
- code-reviewSkill
- communication-craftSkill
- compile-brainSkill
- convertSkill
- corpus-qa-sweepSkill
- critical-thinkingSkill
- deep-reviewSkill
- doc-hygieneSkill
- docs-shellSkill
- docx-to-mdSkill
- ethical-reasoningSkill
- evaluate-before-adoptingSkill
- figure-generatorSkill
- flint-chartSkill
- flint-interactionsSkill
- flint-themeSkill
- git-workflowSkill
- html-to-mdSkill
- humanizerSkill
- install-visual-companionsSkill
- lint-clean-markdownSkill
- markdown-mermaidSkill
- markdown-sanitization-chainSkill
- md-to-emlSkill
- md-to-htmlSkill
- md-to-txtSkill
- md-to-wordSkill
- meditationSkill
- mutation-testingSkill
- planSkill
- platform-awarenessSkill
- print-svg-style-guideSkill
- proactive-awarenessSkill
- problem-framing-auditSkill
- project-capability-authoringSkill
- render-chartSkill
- render-verifySkill
- rich-emailSkill
- risk-analysisSkill
- security-and-hardeningSkill
- setup-dependenciesSkill
- setup-enterprise-stackSkill
- spikeSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
4
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 23
Continuity: Read HANDOFF.md if present for current state, blockers, next action, and verification.
- Distinctive: line 31
Brain health: If the project ships brain-QA scripts, run them.
- Distinctive: line 45
Never modify sibling projects or native memory during status work.
- Distinctive: line 46
Never infer health from a stale dashboard without naming its date.
- Distinctive: line 47
Do not commit, pull, or push.
“Common” is measured: kept by at least 6 in 10 of the 11 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
Status
Produce a terse, read-only orientation report for the current project.
This prompt is self-contained: execute the numbered steps directly. If the
generic skill tool does not list status-reporting, that is not evidence the
skill is missing — plugin-shipped skills are not always in its inventory.
Shared recovery
Load and follow proactive-awareness for read-only recovery. Return the project checkpoint below; this does not authorize writes or a stakeholder-reporting workflow.
Steps
- Identity: Confirm which project this is and read the active branch (
git branch --show-current). - Git & artifact state: Report uncommitted file count and the latest commit subject. When an authorized remote operation or an authentication failure makes it relevant, use the Git auth preview with
--repository-root <repo> --user <account>; do not infer an account from an organization owner. For artifact delivery or recovery, run the session-artifact check with--repository-root <repo>and, when known,--session <id>. Scope unavailable/unsupported states separately from clean results. Routine orientation does not require an unconditional full-session or network-auth scan. - Continuity: Read
HANDOFF.mdif present for current state, blockers, next action, and verification. Read the authoritative task list linked from handoff orAGENTS.md; otherwise use rootTODO.mdif present. Report relevant pending work without assuming a backlog lives in handoff. Follow existing project conventions and tolerate older section names. If the handoff is absent but tasks exist, report those with the missing restart context noted; do not infer there is no work. Keep this read-only and do not re-litigate closed decisions or create an episodic record. Brain health: If the project ships brain-QA scripts, run them. A project with structural and semantic brain checks usually exposes them as:
node scripts/brain-qa.cjs node scripts/brain-semantic-qa.cjsOtherwise skip and note absence in the report.
- Output: Lead with material state, then blockers and next action. Omit empty sections.
Boundaries
- Never modify sibling projects or native memory during status work.
- Never infer health from a stale dashboard without naming its date.
- Do not commit, pull, or push.
- Repository absence is not evidence of retirement.
Would Revise If
Revisit by 2026-10-28 if the handoff format changes, brain-QA muscles cease to represent brain health for projects that ship them, or status reports repeatedly omit a material blocker present in current repository evidence.
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.