Skills

minutes-x1-send-meeting

minutes-x1-send-meeting is a skill in silverstein/minutes, last changed 7 Oct 2026. It is instructions only: no scripts, no named hosts and no pre-approved tools. Our pattern check flagged nothing at commit 4ddfb60 on 27 Oct 2026.

Pattern check: nothing flagged · commit 4ddfb60 · 27 Oct 2026

Install
From the author
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.
Licence
MIT
Repo stars
1.6k
Folder last changed
7 Oct 2026 (opens in a new tab)
Publisher
silverstein
Files
1 file
Checked
4ddfb60 (opens in a new tab) · 27 Oct 2026

Install

Each tab says whether it installs commit 4ddfb60, the one we checked, or the latest version.

No tab for your agent? Use Any agent for OpenCode, Goose, Windsurf (Devin Desktop), Zed, Roo Code, Factory Droid, Junie, Amp and Antigravity, and Claude Code for Cline. Kiro needs the folder copied by hand.

Pinned to commit 4ddfb60, the one we checked.

From your project's root folder:

tmp="$(mktemp -d)" &&
  git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/silverstein/minutes.git "$tmp" &&
  git -C "$tmp" fetch -q --depth 1 origin 4ddfb60d756515ce10c2844d3d4c5bdf5b928154 &&
  git -C "$tmp" sparse-checkout set -- tooling/skills/sources/minutes-x1-send-meeting &&
  git -C "$tmp" checkout -q 4ddfb60d756515ce10c2844d3d4c5bdf5b928154 &&
  mkdir -p .claude/skills &&
  mkdir .claude/skills/minutes-x1-send-meeting &&
  cp -R "$tmp"/tooling/skills/sources/minutes-x1-send-meeting/. .claude/skills/minutes-x1-send-meeting/ &&
  rm -rf "$tmp"

If Claude Code was already running and this created the skills folder, run /reload-skills.

Claude Code docs (opens in a new tab)

What it can touch

From the files and frontmatter at commit 4ddfb60. This is how much a skill can do, not whether it is risky.

What it can touch: Instructions only

It is instructions only: no scripts, no named hosts and no pre-approved tools.

Pattern check

Pattern check: nothing flagged · commit 4ddfb60 · 27 Oct 2026

We checked every text file in this skill, at commit 4ddfb60 on 27 Oct 2026, against 45 published patterns such as download-and-run commands, hidden text and credential access. We don't run the skill, we don't read the web pages it points to, and we can't judge everything its instructions might lead an agent to do. In published tests, pattern checks like this one missed most malicious skills. Read the skill before you install it — especially anything it asks you to download or run.

How the check worksReport an incorrect finding

Format check

Each agent reads SKILL.md a little differently. We check the file against each one's published rules; we don't run the skill in any agent.

  • Agent Skills specFails

    The open format from agentskills.io, held to what the strictest agents enforce, so one folder loads everywhere.

    • Error

      The file is named skill.md. Codex and GitHub Copilot need SKILL.md exactly, though the spec's validator accepts lowercase. F1

      Fix: Rename the file to SKILL.md.

    • Warning

      The frontmatter uses [ ] or { } values. Most agents accept them, but the spec's validator (skills-ref) rejects the file. F4

      Fix: Write lists as "- item" lines and maps as indented key: value lines, without anchors or tags.

    • Warning

      Fields outside the spec: triggers, user_invocable, assets, output and tests. Uploads to the Claude apps and API, and the spec's validator, reject the file; most agents ignore these fields. O1

      Fix: Delete them for a portable skill, or keep them if you only target the agents that read them.

    • Note

      There is no license field, so readers can't tell whether they may reuse the skill. O2

      Fix: Add license: with an SPDX name such as MIT or Apache-2.0, or the name of a bundled licence file.

  • Claude CodePasses with warnings

    Claude Code reads its own extra fields, ignores unknown ones, and still loads a skill whose frontmatter is broken, without its fields.

    • Warning

      The file is named skill.md. Claude Code opens SKILL.md by name, so it finds this file only on disks that ignore case, such as the macOS and Windows defaults. F1

      Fix: Rename the file to SKILL.md.

    • Note

      Claude Code ignores fields it doesn't know: triggers, user_invocable, assets, output and tests. O1

      Fix: Check the spelling against Claude Code's field list, or delete them.

  • Claude apps & API uploadFails

    Uploading to claude.ai or the Claude API, or packaging with Anthropic's script, accepts only the six spec fields and stops on anything else.

    • Error

      Upload and packaging fail on fields outside the spec: triggers, user_invocable, assets, output and tests. O1

      Fix: Delete them, and keep your own data under metadata as text values.

    • Warning

      The file is named skill.md. Anthropic's API docs and packaging script use SKILL.md; the claude.ai Help Center writes skill.md, so the apps may accept it. F1

      Fix: Rename the file to SKILL.md.

    • Note

      The description is 427 characters. The claude.ai Help Center says 200 at most, though Anthropic's API docs and validator allow 1,024. D4

      Fix: If the claude.ai upload refuses it, trim the description to 200 characters.

  • OpenAI (Codex & API)Fails

    Codex finds SKILL.md by its exact name and needs a description; OpenAI's Skills API checks the frontmatter against the spec and caps uploads.

    • Error

      The file is named skill.md. Codex looks only for SKILL.md, though OpenAI's upload matches the name in any case. F1

      Fix: Rename the file to SKILL.md.

    • Warning

      Fields outside the spec: triggers, user_invocable, assets, output and tests. Codex ignores them; OpenAI doesn't say whether its upload accepts them. O1

      Fix: Delete them, or move your own data under metadata as text values.

  • VS Code & CopilotFails

    VS Code reads skills one folder below .github/skills, .claude/skills or .agents/skills and falls back to the folder name when the name is missing or differs; GitHub's Copilot docs require the exact name SKILL.md.

    • Error

      The file is named skill.md. GitHub Copilot requires SKILL.md, and VS Code finds this file only on disks that ignore case. F1

      Fix: Rename the file to SKILL.md.

    • Note

      VS Code ignores fields it doesn't support: triggers, user_invocable, assets, output and tests. O1

      Fix: Delete them unless another agent you target reads them.

SKILL.md

Files

1 file

PathSize
skill.md (opens in a new tab)11.4 KB

Copies

These share its SKILL.md or its name and description but not all its files, so we list them separately.

More from silverstein/minutes

  • minutes-brief

    silverstein/minutes

    Fast non-interactive briefing before any meeting — auto-detects your next calendar event, pulls relationship history, surfaces open commitments, and produces a one-page brief in under 30 seconds. Use this whenever the user says "brief me", "give me a quick brief", "what's coming up", "background on my next call", "who am I meeting next", "brief me on Sarah", "I have a call in 10 min", "quick rundown", or right before walking into a meeting. Different from /minutes-prep — brief is the fast hook-fireable version that doesn't ask questions and doesn't set goals. Use brief when speed matters; use prep when the user wants to think hard about goals first.

    • Runs shell commands
    Pattern check: Nothing flagged

    MIT · 1.6k repo stars · Updated 25 Jul 2026

  • minutes-brief

    silverstein/minutes

    Fast non-interactive briefing before any meeting — auto-detects your next calendar event, pulls relationship history, surfaces open commitments, and produces a one-page brief in under 30 seconds. Use this whenever the user says "brief me", "give me a quick brief", "what's coming up", "background on my next call", "who am I meeting next", "brief me on Sarah", "I have a call in 10 min", "quick rundown", or right before walking into a meeting. Different from /minutes-prep — brief is the fast hook-fireable version that doesn't ask questions and doesn't set goals. Use brief when speed matters; use prep when the user wants to think hard about goals first.

    • Runs shell commands
    Pattern check: Nothing flagged

    MIT · 1.6k repo stars · Updated 25 Jul 2026

  • minutes-brief

    silverstein/minutes

    Fast non-interactive briefing before any meeting — auto-detects your next calendar event, pulls relationship history, surfaces open commitments, and produces a one-page brief in under 30 seconds. Use this whenever the user says "brief me", "give me a quick brief", "what's coming up", "background on my next call", "who am I meeting next", "brief me on Sarah", "I have a call in 10 min", "quick rundown", or right before walking into a meeting. Different from /minutes-prep — brief is the fast hook-fireable version that doesn't ask questions and doesn't set goals. Use brief when speed matters; use prep when the user wants to think hard about goals first.

    • Runs shell commands
    Pattern check: Nothing flagged

    MIT · 1.6k repo stars · Updated 25 Jul 2026

  • minutes-brief

    silverstein/minutes

    Fast non-interactive briefing before any meeting — auto-detects your next calendar event, pulls relationship history, surfaces open commitments, and produces a one-page brief in under 30 seconds. Use this whenever the user says "brief me", "give me a quick brief", "what's coming up", "background on my next call", "who am I meeting next", "brief me on Sarah", "I have a call in 10 min", "quick rundown", or right before walking into a meeting. Different from /minutes-prep — brief is the fast hook-fireable version that doesn't ask questions and doesn't set goals. Use brief when speed matters; use prep when the user wants to think hard about goals first.

    • Runs shell commands
    Pattern check: Nothing flagged

    MIT · 1.6k repo stars · Updated 25 Jul 2026

  • minutes-cleanup

    silverstein/minutes

    Manage old recordings — find large files, archive old meetings, delete processed originals. Use when the user says "clean up recordings", "how much space are meetings using", "delete old recordings", "archive meetings", "manage meeting storage", or asks about disk space from minutes.

    • Runs shell commands
    Pattern check: Nothing flagged

    MIT · 1.6k repo stars · Updated 12 May 2026

  • minutes-cleanup

    silverstein/minutes

    Manage old recordings — find large files, archive old meetings, delete processed originals. Use when the user says "clean up recordings", "how much space are meetings using", "delete old recordings", "archive meetings", "manage meeting storage", or asks about disk space from minutes.

    • Runs shell commands
    Pattern check: Nothing flagged

    MIT · 1.6k repo stars · Updated 15 Jul 2026

All skills in silverstein/minutes