triage

Organizes un-triaged agenda items into a hub graph and ranks items needing owner attention.

14|Updated Mar 2, 2026
Ready to run
npx skills add https://github.com/intendant-dev/Intendant --skill triage-intendant-dev
πŸ’¬ Prompt for ChatGPT / Claude Chatβ–Ό
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/intendant-dev/Intendant/tree/main/automations/triage
Command: npx skills add https://github.com/intendant-dev/Intendant --skill triage-intendant-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Standing agendas accumulate un-filed items over time, making it hard for an owner to see what actually needs attention. This Skill runs a scheduled triage pass that files the un-triaged frontier into the agenda's hub graph and surfaces a ranked attention list. ## Core Features & Use Cases - Frontier-Scoped Placement: Files only un-triaged items into the hub graph using part_of links, seeding placement from each item's provenance-derived project and creating hub notes when two or more items share a project. - Attention Ranking: Ranks what genuinely needs the owner β€” blocking questions first, then approval-pending manifests, suspended standing effects, decision items, and resolvable blocked items β€” with a one-line recommendation annotation on each. - Orientation Maintenance: Proposes refreshed orientation paragraphs as annotations when a hub's body drifts from its children, and supplies missing Situate lines for decision items. - Use Case: On a weekly cadence, the run reads the agenda via ctl agenda list --all --json, files new items under project hubs, and parks a single triage:summary item listing every placement and the ranked attention list. ## Quick Start Ask the agent to run an agenda triage pass over the un-triaged frontier and produce a ranked attention summary.

Frequently Asked Questions about triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage a backlog of agenda items automatically?β–Ό

Run a triage pass scoped to the un-triaged frontier: open items newer than the newest triage:summary item, plus items lacking placement or triage annotation. Each item is filed into the hub graph and ranked items receive a recommendation annotation.

What is the un-triaged frontier in agenda triage?β–Ό

The frontier is the set of open agenda items newer than the newest triage:summary item, plus open items lacking both a part_of placement and a triage annotation. Daemon-parked items that are already placed are excluded from the frontier.

Can the triage run complete or resolve agenda items?β–Ό

No. The triage mandate is strictly propose-don't-dispose: it never completes or retires items, clears blockers, answers questions, or touches reminder and urgency policy. It only places, links, annotates, and ranks.

What happens when the agenda frontier is empty?β–Ό

The run writes nothing β€” no summary item and no annotations β€” and ends by stating that the frontier is empty with no action taken, so the run's write-back records the no-op.

How does triage decide where to place an agenda item?β–Ό

Placement is seeded from the item's provenance-derived project: items go under the matching existing hub, or a new hub note is parked when two or more frontier items share a project. Singletons with no matching hub stay unplaced with a standalone annotation.