# Minutes X1 Closeout

Prepare a sourced Minutes meeting outcome for human-governed closeout of existing X1 work.

- Repository: https://github.com/silverstein/minutes (1583 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add silverstein/minutes --skill minutes-x1-closeout -g -a claude-code -y`
Codex: `npx skills add silverstein/minutes --skill minutes-x1-closeout -g -a codex -y`
Cursor: `npx skills add silverstein/minutes --skill minutes-x1-closeout -g -a cursor -y`
Gemini CLI: `npx skills add silverstein/minutes --skill minutes-x1-closeout -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add silverstein/minutes`

## Description

Prepare a sourced Minutes meeting outcome for human-governed closeout of existing X1 work. Use when the user wants a meeting decision or commitment to close, defer, escalate, or retire a specific X1 coordination thread. Never use it to infer settlement, move money, contact anyone, or close X1 work automatically.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# /minutes-x1-closeout

Turn one clear meeting outcome into a proposed closeout for one existing X1
coordination thread. Minutes supplies the source. X1 supplies identity,
authority, review, disposition, and the household record.

## Required connections

This workflow needs both the local Minutes MCP and the official X1 MCP. If X1
isn't connected, stop after identifying the meeting outcome and direct the user
to X1's official connection instructions. Don't invent an endpoint, credential,
account, thread ID, or local substitute.

## Workflow

1. Call Minutes `get_meeting_insights` with `include_restricted: false` to find
   an `explicit` or `strong` decision or commitment that supports the closeout
   the user requested. The logged restricted-source override is forbidden for
   this cross-service handoff. Use only an insight released by that bounded
   call. Don't use `agent.annotation`, a raw path, a transcript fragment read
   outside Minutes, or a model-written summary as source proof.

2. Use X1 `find_coordination_threads` or `list_my_coordination_threads`, then
   `get_coordination_thread`, to resolve exactly one open thread the signed-in
   X1 actor can read. If zero or multiple threads plausibly match, ask the user
   to choose. Never select a hidden, closed, or guessed target.

3. Ask the user to choose the X1 outcome if they haven't already:
   `resolved`, `escalated_elsewhere`, `deferred`, or `no_longer_relevant`.
   Meeting language that money was sent, a wire was approved, or a payment was
   discussed doesn't prove settlement. Keep the work open unless the user
   explicitly chooses a non-settlement closeout.

4. Build `sourceProposal` from the exact released Minutes insight:

The rest: https://github.com/silverstein/minutes/blob/HEAD/.agents/skills/minutes/minutes-x1-closeout/SKILL.md