icaire-provide-update
Capture ICAIRE progress updates into the remote ICAIRE brain. Use when the user dumps notes about progress, decisions, blockers, questions, initiative movement, people updates, or next actions and wan
SKILL.mdskills/icaire-provide-update/SKILL.md
GitHubICAIRE Provide Update
Turn unstructured ICAIRE progress notes into durable remote brain updates.
Contract
- Use the ICAIRE Cortex MCP connector as the source of truth and write target.
- Prefer direct remote writes. Do not only summarize in chat when the user is providing an update for the brain.
- Use paths relative to the remote brain root, such as
meetings/...,initiatives/...,people/...,inbox/..., andtasks/...; do not prefix paths withcortex/. - Before choosing target pages or task paths, call ICAIRE MCP
filing_rulesand follow the compiledFILING.mdguidance it returns. If that tool is unavailable, list and read the relevantFILING.mdfiles directly; do not expect a page namedfiling_rulesto exist. - Preserve uncertainty. Separate confirmed progress, inferred implications, blockers, open questions, and candidate tasks.
- Before marking any task
doneorarchived, either create or link the successor task and useNext task: tasks/<slug>in the timeline entry, or stateNo successor task needed: <reason>. - Verify every write by reading the changed page or listing the created task.
Workflow
- Identify the update source, date, people, initiatives, deliverables, and whether the notes include decisions, progress, blockers, questions, or tasks.
- Retrieve filing rules and context with ICAIRE MCP
filing_rules,search,query,list, andread. - Update stable pages when the note changes durable knowledge:
- initiative progress, status, milestones, blockers, dependencies
- people responsibilities or commitments
- deliverable status
- open questions or unresolved triage notes
- Create or update task pages for concrete next actions:
- Prefer MCP
tasks/create; usetasks_createonly if the client cannot call slash-named tools. - Assign only active members from
members/list; usemefor the current authenticated member only when the note clearly assigns the action to them. - When recording completion, create or identify the next concrete task first
unless no successor is needed, then include the completion handoff in
tasks/update. - If no active member can be identified, write the item to
inbox/or report it as unassigned instead of assigning it to an arbitrary person page.
- Prefer MCP
- Verify persistence with
read,list, ortasks/list.
Output
Return:
Updated: pages changed or createdTasks: task pages created or updatedOpen Questions: unresolved pointsUnassigned Items: concrete work without an active memberVerification: read/list checks performed
Guardrails
- Do not invent owners, dates, status, or initiative names.
- Do not assign tasks to external people or non-members.
- Do not create duplicate initiative, person, meeting, or task pages when an existing page should be updated.
- Do not claim the remote brain was updated until the write is verified.
- Do not bypass the MCP
filing_rulestool by guessing from stale local conventions or by reading a nonexistentfiling_rulespage.