Menu
Triage report for your projects — surfaces what needs attention, grouped by urgency.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | pc-triage |
| description | Triage report for your projects — surfaces what needs attention, grouped by urgency. |
Use this skill when the user asks for a triage report, asks "what projects need my attention", asks for a Monday-morning kickoff, or otherwise wants a prioritized list of which projects to deal with.
It runs project-commander with JSON output, applies a fixed set of
heuristics, and returns a markdown action list grouped by urgency.
Trigger on requests like:
Do not trigger on requests for a general fleet view — for that,
just run project-commander directly. This skill is specifically for
deciding what to act on next.
Run the bundled script:
python skills/pc-triage/scripts/triage.py [--since N] [--root /path]
Or, if just is available in the repo:
just triage # full triage
just triage-week # restrict to last 7 days
Optional arguments:
--since N — restrict to projects active in the last N days--root /path — scan a specific root (otherwise auto-detected)Both pass through to project-commander. The script assumes
project-commander is on $PATH.
Markdown with up to four sections, each emitted only if it has items:
| Section | Triggers |
|---|---|
| Urgent | prompt-injection-detected flag |
| This week | plan-drift flag; or dirty-tree flag plus last_active > 7 days |
| When you have time | Dormant progress; Stub progress |
| For your records | tool-cluster flag; Drifting progress; Hot progress (informational) |
If nothing trips any rule, the output is Nothing to triage. Clean fleet..
The user wants the action list, not your interpretation of it.
--project NAME.Do not paraphrase, re-rank, or invent recommendations beyond what the script emitted. The whole point of the skill is that the heuristics are auditable and stable.