project-health
Skill509 starsChanged 3 months agoMITView on GitHub
Scan active projects for status, blockers and next actions. Use when the user says 'how are my projects', 'what's stuck', 'project status'. Also use proactively when projects have gone quiet. Not for writing a spec for a new product idea; use `product-brief`.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- Fallen-leaves089/project-healththeir own version, first seen Nov 1, 2026
- manastalukdar/ai-devstudiotheir own version, first seen Oct 13, 2026
- shaunburdick/skillstheir own version, first seen Apr 19, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- Fallen-leaves089/project-health★ 1same name
- manastalukdar/ai-devstudio★ 1same name
- shaunburdick/skills★ 1same name
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 repository153 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .claude/plugins/compound-engineering/CLAUDE.mdCLAUDE.md
- .cursor/rules/search-routing.mdcCursor rule
- anthropic-algorithmic-artSkill
- anthropic-brand-guidelinesSkill
- anthropic-doc-coauthoringSkill
- anthropic-docxSkill
- anthropic-frontend-designSkill
- anthropic-internal-commsSkill
- anthropic-mcp-builderSkill
- anthropic-pptxSkill
- anthropic-slack-gif-creatorSkill
- anthropic-theme-factorySkill
- anthropic-webapp-testingSkill
- anthropic-web-artifacts-builderSkill
- anthropic-xlsxSkill
- atlassian-setupSkill
- backup-nowSkill
- backup-restoreSkill
- backup-setupSkill
- calendar-setupSkill
- commitmentsSkill
- create-mcpSkill
- daily-planSkill
- daily-reviewSkill
- decision-logSkill
- delegate-checkSkill
- dex-backlogSkill
- dex-doctorSkill
- dex-improveSkill
- dex-obsidian-setupSkill
- dex-rollbackSkill
- dex-updateSkill
- dex-whats-newSkill
- diff-profileSkill
- enable-semantic-searchSkill
- getting-startedSkill
- goal-backlogSkill
- google-workspace-setupSkill
- granola-setupSkill
- identity-snapshotSkill
- industry-truthsSkill
- initiative-kickoffSkill
- integrate-mcpSkill
- journalSkill
- manage-capabilitiesSkill
- meeting-closeoutSkill
- meeting-prepSkill
- ms-teams-setupSkill
- pipedrive-setupSkill
- pipeline-syncSkill
- process-meetingsSkill
- product-briefSkill
- prompt-improverSkill
- relationship-radarSkill
- reviewSkill
- save-insightSkill
- scrapeSkill
- skill-scoreSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 8 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 38
No tasks for 2+ weeks = yellow
- Distinctive: line 41
Look for "blocked", "waiting on", "stuck" in project notes
- Distinctive: line 45
Check if there's a clear next action
- Distinctive: line 46
No next step = yellow
- Distinctive: line 71
When feeling disconnected from the big picture
- Distinctive: line 72
Before 1:1s to surface blocked projects
- Distinctive: line 73
When deciding what to work on next
- Very specific: line 79
Call refresh_project_related_tasks (no path) while scanning.
- Very specific: line 81
If the result is on or off, say nothing about the preference.
- Distinctive: line 86
Add a task to Week Priorities
- Very specific: line 102
Call track_event with event_name project_health_checked and properties:
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- Generated from `.claude/skills/project-health/SKILL.md` by `scripts/generate-agents-skills.py`. Do not edit. -->Quick scan of all active projects to see what's stalled, blocked, or needs attention.
What This Does
Checks each project in 04-Projects/ for:
- Activity levels (when was project last touched?)
- Week Priorities presence (does project have active tasks?)
- Blockers (anything blocking progress?)
- Next steps clarity (is the next action clear?)
Process
Step 1: Scan Projects
List all projects in 04-Projects/:
ls -la 04-Projects/Step 2: Check Each Project
For each project folder or file:
Activity Check:
- Get last modification time
7 days without activity = yellow
14 days without activity = red
Week Priorities Presence:
- Scan
00-Inbox/Weekly_Plans.mdfor project mentions - No tasks for 2+ weeks = yellow
Blocker Check:
- Look for "blocked", "waiting on", "stuck" in project notes
- Any logged blocker = red
Next Step Clarity:
- Check if there's a clear next action
- No next step = yellow
Step 3: Output Dashboard
### Project Health Dashboard
| Project | Status | Issue | Days Since Activity |
|---------|--------|-------|---------------------|
| [Project A] | 🟢 | On track | 2 |
| [Project B] | 🟡 | No active tasks | 8 |
| [Project C] | 🔴 | Blocked - waiting on [X] | 15 |
**Summary:** [N] projects ([X] 🟢 / [Y] 🟡 / [Z] 🔴)Status Meanings
- 🟢 Green: Active, clear next steps, no blockers
- 🟡 Yellow: Stale 7-14 days, OR no active tasks, OR unclear next step
- 🔴 Red: Blocked, OR stale 14+ days
When to Use
- Weekly planning to check project health
- When feeling disconnected from the big picture
- Before 1:1s to surface blocked projects
- When deciding what to work on next
Related tasks
Each project page can show a Related tasks list near the top — open work first, a few recently done underneath. The list links to the real task; ticking stays in 03-Tasks/Tasks.md. Only tasks with an explicit Project: link (path or project name) or a path/wikilink to that project file appear.
- Call
refresh_project_related_tasks(no path) while scanning. - If the result is
needs_opt_in, ask once: "Project pages can show a Related tasks list near the top — open work first, a few recently done underneath. Only tasks you linked to that project appear, and you still tick them in the main task list. Turn it on?" Then callset_project_related_taskswithenabledtrue or false. Do not write the section before they answer, and do not ask again after they answer. - If the result is
onoroff, say nothing about the preference.
Follow-up Actions
For yellow projects:
- Add a task to Week Priorities
- Clarify next step in project notes
For red projects:
- Identify what's blocking progress
- Escalate if needed
- Or decide to pause/archive the project
Track Usage (Silent)
Call the mark_feature_used tool on the dex-analytics MCP server with project-health. This ticks the feature's box in System/usage_log.md, which is what /dex-level-up reads to recommend features that have not been tried. It writes locally and sends nothing, so it runs whether or not analytics is enabled.
Analytics (Silent):
Call track_event with event_name project_health_checked and properties:
- projects_reviewed
- blockers_found
This only fires if the user has opted into analytics. No action needed if it returns "analytics_disabled".
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.

