minutes-x1-send-meeting SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
minutes-x1-send-meeting from silverstein/minutes is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add silverstein/minutes/minutes-x1-send-meeting@git:20261007.32c59e5Pins git:20261007.32c59e5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- silverstein/minutes
- Path
.agents/skills/minutes/minutes-x1-send-meeting/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261007.32c59e5, committed Oct 7, 2026
- First version recorded
- Sep 29, 2026
- Size
- 10,786 bytes
- Repository stars
- 1,591
- License
- MIT
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# /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` …
Read the whole file at its exact version.
How to install
mdr add silverstein/minutes/minutes-x1-send-meeting@sha256:555bf35a2f03f4fdThe line at the top of this page pins the label git:20261007.32c59e5, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_vnn2qdjrqmso6al5)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Sep 29, 2026 and Oct 7, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261007.32c59e5 latest | 2026-10-07 | 32c59e5 | 10,786 B | A | view · diff |
| git:20260929.e9a52ac | 2026-09-29 | e9a52ac | 7,625 B | A | view · diff |
| git:20260929.41306cb | 2026-09-29 | 41306cb | 7,187 B | A | view · diff |
| git:20260929.c780366 | 2026-09-29 | c780366 | 5,397 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10786 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
silverstein/minutes · 1,591 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_vnn2qdjrqmso6al5 GET https://markdownregistry.com/api/v1/resolve?ref=silverstein/minutes/minutes-x1-send-meeting GET https://markdownregistry.com/api/v1/blob/555bf35a2f03f4fd18fd768603266e0d32bd30b6309ea36f4edb01068cea6655
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from silverstein/minutes
Every file in silverstein/minutes