icaire-status
Fetch the authenticated ICAIRE member's tasks from the remote brain and summarize status across open, waiting, blocked, and recently completed work. Use when the user asks for task status, wants an ov
SKILL.mdskills/icaire-status/SKILL.md
GitHubICAIRE Status
Fetch the current member's ICAIRE tasks from the remote brain and summarize the state of their work.
Contract
- Use ICAIRE Cortex MCP, not local TODO files.
- Start with
me. If the authenticated user is not an active member, stop and explain that ICAIRE membership must be configured before task status works. - Fetch tasks with
tasks/listusingassignee: me. - Check at least
open,waiting, andblocked. Includedoneonly when the user asks for completed/recently completed work or a full history. - When task records include
readiness, use it to split open tasks intoReadyandNeeds input. - Prefer slash tool names; use underscore aliases only if needed.
- Output the status in chat. Do not write a file unless explicitly asked.
Workflow
- Call
meand confirmmember.person_slugexists. - Call
tasks/listforassignee: meand each active status:openwaitingblocked
- If the user asks for completed work, also call
tasks/listwithstatus: done. - Group tasks by status, then order by priority, due date when available, and task order returned by the server.
- For thin or unclear tasks, read linked
source_slugsonly when needed to explain the status accurately. - Identify:
- ready tasks the user can act on now, using
readiness: readywhen present - tasks needing input, using
readiness: underspecifiedwhen present - waiting tasks and what they appear to be waiting for
- blocked tasks and the blocking condition
- high-priority items
- stale or unclear tasks that need clarification
- ready tasks the user can act on now, using
Output Requirements
- Start with
Task status. - Include a concise summary count by status.
- Then show sections in this order:
ReadyNeeds inputWaitingBlockedDoneonly when requestedNeeds clarificationonly when readiness is absent and the task is too unclear to classify.
- For each task, include title or human-readable action, priority when useful, and the next visible action or blocking reason.
- Do not include task slugs unless the user explicitly asks for paths/slugs or two tasks would otherwise be ambiguous.
- For
Needs input, include the blocking question(s), preferring the task page's## Open Questionssection when present. - Keep the report scannable; prefer concise bullets over long task bodies.
- End with
Recommended focuslisting the top 1-3 tasks to handle next.
Guardrails
- Do not invent tasks if
tasks/listreturns none. - Do not show other members' tasks when the user asked for their own status.
- Do not silently fall back to all tasks when
mecannot resolve. - Do not mark tasks done, create tasks, or change status unless explicitly asked.
- Do not treat external people as assignable members.