team-brainstorm

$npx mdskill add github/plugin-marketplace-starter/team-brainstorm

1. Discover the `marketplace-starter-brainstorm` canvas capabilities. 2. Open it with a stable instance handle. It takes no input. 3. Read the board before changing it. Keep the user's existing notes. 4. Add a few short ideas or questions using `save_note`. Put each note in `ideas`, `questions`, or `next`. Do not fill the board with a complete plan before the user has contributed. 5. Ask one focused question, discuss the answer, and update the board. Use `save_note` with an existing ID to edit or move a note. 6. Summarize agreed next steps in chat. Do not implement them without the user's go-ahead.

SKILL.md

.github/skills/team-brainstormView on GitHub ↗
---
name: team-brainstorm
description: "Brainstorm with the user on a shared board. Use when exploring ideas, comparing options, planning together, or collecting questions and next steps."
---

# Team brainstorm

1. Discover the `marketplace-starter-brainstorm` canvas capabilities.
2. Open it with a stable instance handle. It takes no input.
3. Read the board before changing it. Keep the user's existing notes.
4. Add a few short ideas or questions using `save_note`. Put each note in
   `ideas`, `questions`, or `next`. Do not fill the board with a complete plan
   before the user has contributed.
5. Ask one focused question, discuss the answer, and update the board.
   Use `save_note` with an existing ID to edit or move a note.
6. Summarize agreed next steps in chat. Do not implement them without the
   user's go-ahead.

The board has no persistence or export. Reopening during this session preserves
it; ending or reloading the extension loses it. Tell the user before relying on
it for durable decisions. If canvas tools are unavailable, explain that this
host cannot present the board and brainstorm in chat instead.

More from github/plugin-marketplace-starter

SkillDescription
adversarial-reviewReview supplied code, a local diff, or a plan by challenging assumptions and delegating an evidence-backed pass to the code-reviewer agent. Use when asked for adversarial review, defect review, or to challenge an implementation. Don't use for writing features, explaining unchanged code, or ordinary factual questions.
bug-reportUse when the user asks to draft a bug report or turn rough bug notes into a report. Not for fixing bugs, debugging code, or explaining errors.
json-configurationValidate supplied JSON configuration and look up values by JSON Pointer using the local JSON configuration MCP tools. Use for checking whether JSON is valid or locating a specific configuration value. Don't use for YAML, arbitrary filesystem browsing, or unrelated coding and factual questions.
skill-authoringCreate or improve an agent skill with clear triggers, bounded instructions, and positive and negative Vally evals. Use for requests to author a reusable SKILL.md and its evaluations. Don't use for ordinary coding, factual questions, or simply running an existing skill.