# Minutes X1 Send Meeting

Send one of the user's own Minutes meetings to their X1 household for review.

- 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-send-meeting -g -a claude-code -y`
Codex: `npx skills add silverstein/minutes --skill minutes-x1-send-meeting -g -a codex -y`
Cursor: `npx skills add silverstein/minutes --skill minutes-x1-send-meeting -g -a cursor -y`
Gemini CLI: `npx skills add silverstein/minutes --skill minutes-x1-send-meeting -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add silverstein/minutes`

## Description

Send one of the user's own Minutes meetings to their X1 household for review. Use when the user wants a meeting's summary, decisions, action items, and open questions to reach X1 so they can confirm what belongs in their household record. X1 asks the user to approve the send, and nothing reaches the household record until they confirm each item. Never use it for a restricted meeting, a transcript, or someone else's meeting.

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

# /minutes-x1-send-meeting

Send one of the user's own meetings to their X1 household for review. Minutes
supplies the meeting's outcomes. X1 decides who the sender is, which
household it goes to, and what gets matched, and the user approves the send
in X1. The meeting lands in the user's own review queue. Nothing reaches the
household record until they confirm each item, and no professional sees it.

## Required connections

This workflow needs both the local Minutes MCP and the official X1 MCP. Call
X1 `get_user_capabilities` first. If `submit_my_meeting` or
`request_human_confirmation` isn't mounted, stop: X1 hasn't turned meeting
sends on for this account yet. Don't substitute another X1 write tool, invent
an endpoint, or save the meeting somewhere else in X1.

Before using `dueStatement` or `detail`, inspect the mounted
`submit_my_meeting` input schema from MCP `tools/list` and check its
`meeting.actionItems` item properties. A mounted tool name alone does not
prove support for a field. If that schema is unavailable, an available X1
`get_user_capabilities` action proposal contract for `submit_my_meeting`
may supply the argument schema; capability discovery never grants approval.
If a needed field is absent or neither discovery path supplies its schema,
stop before requesting a send and ask: “Can you update or reconnect X1 so
it accepts this meeting's original timing or detail?” Do not silently drop
conditional timing or rewrite a task to work around an older backend.

## Workflow

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