Turns everything the system is seeing (open work queue, Synapse-graded bookmarks and stories, new Cortex notes, open upgrade records, TELOS goals) into ranked recommendations of what to work on, shown on the Pulse /prioritize page and refreshed every 2 hours by a cheap OpenAI job
The thinking, frameworks, and architecture that distinguish this skill from a generic version of the same task.
latest.json is refreshed first, unchanged inputs cost no model call, and source errors are named rather than hidden.| Intent | Trigger | File |
|---|---|---|
| Run | "run prioritize", "refresh priorities", "what should I work on" (when latest is stale) | Intents/Run.md |
| Review | "show priorities", "why is X recommended", "let's do the first one", "dismiss that" | Intents/Review.md |
| File | Read when |
|---|---|
Setup.md |
first-time install: Config.json, the OpenAI key, the 120-minute schedule |
LIFEOS/USER/CUSTOMIZATIONS/SKILLS/Prioritize/Config.json (lane, window, budget, limits, principal context, category definitions, and routes: which skill owns the action behind each category). Without it every command exits 1 and points at the setup guide: Setup.md.LIFEOS/MEMORY/STATE/prioritize/ (latest.json, status.json, dismissed.json, history/); override with LIFEOS_PRIORITIZE_DIR.LIFEOS/PULSE/state/work-cache.json (optional; skipped with a recorded error when absent), Achilles.ts open-crit --json (rides in the work source), Pulse /api/synapse, KnowledgeQuery.ts, Upgrades.ts list, USER/TELOS/PRINCIPAL_TELOS.md, TELOS.md freshness, LIFEOS_STATE.json, MEMORY/STATE/work-attention.json.GET /api/prioritize (page data), POST /api/prioritize/{dismiss,undismiss,run} (dismissal, detached forced run), at PULSE_URL (default http://localhost:31337).Prioritize.ts run every 120 minutes, set up with whatever scheduler your install uses; the model call goes through Inference.ts with an OpenAI key (Setup.md)./api/synapse; when Pulse is down the capture source errors and the run continues on the rest (recorded in errors).KnowledgeQuery.ts --created-after includes _archive notes; the loader filters them out.goal:G# labels.User: "what should I be working on?"
→ Review: read latest.json; if older than the job cadence, Run first
→ Answer with the focus summary and top three, each with its next action and evidence
User: "do the second one"
→ Review: route the recommendation's next action to the skill Config.json `routes` names for its category (a work issue, an Upgrade record, a Telos edit, a draft), under the normal permission rules
Each workflow is one job the skill runs. The trigger phrases route your request to the right one — this is the skill's routing table.
Intents/Run.md run prioritize, refresh priorities, what should I work on (when latest is stale)
Intents/Review.md show priorities, why is X recommended, lets do the first one, dismiss that
Deterministic executables the workflows call — the code that does the real work, not prompt scaffolding.
Prioritize.tsSay any of these to your DA and LifeOS activates the Prioritize skill automatically:
Or invoke explicitly:
Skill("Prioritize")Auxiliary files the skill loads at runtime — frameworks, guides, configs.
Install LifeOS on your machine — your DA gets the Prioritize skill plus 96 others, all hooked into one Life OS.