Skip to content
Skills Library
Design & UX · Review & audit

setup

/setup

Verify the Miro plugin without reading or exposing its API token. Use when: 'set up Miro', 'configure Miro', 'Miro setup', the Miro MCP server is unavailable, or a Miro tool reports an authentication error. Actions: check (read-only verification, default and only action. This plugin's entire configuration is native userConfig, so there is nothing an apply could write); check verify-api additionally authorizes one read-only API call.

Licence
MIT
Last repository change
26.10.2026

Assessment and security

84/ 100Class: good
Format9 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
10
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Verify the Miro plugin without reading or exposing its API token. Use when: 'set up Miro', 'configure Miro', 'Miro setup', the Miro MCP server is unavailable, or a Miro tool reports an authentication error. Actions: check (read-only verification, default and only action. This plugin's entire configuration is native userConfig, so there is nothing an apply could write); check verify-api additionally authorizes one read-only API call.

Triggers from the description

set up Miroconfigure MiroMiro setup

Arguments

/setup [check] [verify-api]
Original author description

Verify the Miro plugin without reading or exposing its API token. Use when: 'set up Miro', 'configure Miro', 'Miro setup', the Miro MCP server is unavailable, or a Miro tool reports an authentication error. Actions: check (read-only verification, default and only action. This plugin's entire configuration is native userConfig, so there is nothing an apply could write); check verify-api additionally authorizes one read-only API call.

How it works

  1. Purpose
  2. Task
  3. Headless installation
  4. Output
  5. Boundaries
Original SKILL.md headings · 147 lines, 1,284 words
SKILL.md preview
---
description: "Verify the Miro plugin without reading or exposing its API token. Use when: 'set up Miro', 'configure Miro', 'Miro setup', the Miro MCP server is unavailable, or a Miro tool reports an authentication error. Actions: check (read-only verification, default and only action. This plugin's entire configuration is native userConfig, so there is nothing an apply could write); check verify-api additionally authorizes one read-only API call."
argument-hint: "[check] [verify-api]"
user-invocable: true
disable-model-invocation: true
---

## Purpose

Guide the user through Claude Code's native configuration flow and verify that the bundled Miro MCP
server is available without reading, printing, or writing the sensitive token. The `miro_api_token`
option is optional in the manifest: the server starts without it, and a Miro tool call without a
token returns an error that says to run `/plugin configure miro@<marketplace>`. Claude Code
owns the secure credential storage.

Check-only per the uniform setup contract's userConfig-only carve-out: this plugin's entire
configuration surface is the native sensitive `userConfig` token, so `check` (default and only
action) verifies and reports, and reconfiguration routes through Claude Code's native flow. An
`apply` here would have nothing to write except the credential storage and `pluginConfigs` setup
must never touch. Non-interactive: the optional API probe runs only when `verify-api` is passed,
never from an in-flow question.

Official contracts:

- **Pointer**: when a step turns on how plugin options or default enablement behave, fetch
  [Plugins reference: User configuration](https://code.claude.com/docs/en/plugins/manifest-reference#user-configuration)
  and [Default enablement](https://code.claude.com/docs/en/plugins/manifest-reference#defaultenabled)
  live.
- **As of**: 2026-10-11
- **Recheck trigger**: either section changes how options are prompted for, stored or delivered, or
  what `defaultEnabled: false` does at install.

## Task

1. Check whether the `miro` plugin is enabled and whether its scoped MCP tools are present in the
   current tool inventory. Do not inspect settings files, environment variables, process arguments,
   debug logs, credential stores, or the token itself.
2. When the plugin is disabled, direct the user to enable `miro` through the `/plugin` interface or
   `claude plugin enable miro`. The token is entered afterward with `/plugin configure miro@<marketplace>`. Do not run
   either command for the user and do not hand-edit `pluginConfigs`. For a non-interactive install
   (CI, a fleet bootstrap, a scripted machine setup), point to the headless path below instead.
3. When the plugin is enabled but its tools are absent, report that startup or configuration failed.
   Direct the user to the `/plugin` Errors view and `/mcp`. An unset token is not a startup
   failure: the server runs and each tool call returns the configure instruction, so absent tools
   point to a different cause. A first launch that cannot install the server's npm dependencies
   (no `npm` on `PATH`, no network, a failed `npm ci`) is such a cause: the server exits, and its
   stderr names the cause and the one shell line that repairs it. To tell the user where to read
   that stderr, read the two sections below at run time and give the user the route they state;
   do not read the user's logs for them.
   - **Pointer**: for where a plugin MCP server's startup error is recorded, see
     <https://code.claude.com/docs/en/plugins/troubleshooting#server-is-configured-but-never-connects>
     and <https://code.claude.com/docs/en/debug-your-config#check-mcp-servers>.
   - **As of**: 2026-10-24 (the first section says `claude --debug`, the second `claude --debug=mcp`;
     both name the log at `~/.claude/debug/<session-id>.txt`)
   - **Recheck trigger**: either section changing where server stderr is shown or the debug flag
     that captures it.

   After configuration, require `/reload-plugins` or a new session before rechecking tool availability.
4. When the scoped Miro tools are present, report only that the server started. The server starts
   and lists its tools with no token, so tool presence proves neither that a token was supplied nor
   that it has API access. Say the token state is unchecked, and that `verify-api` detects an unset
   token.
5. Optional credential check, only when the invocation passed `verify-api` (the explicit opt-in;
   never offer it as an in-flow question): call the read-only `miro_list_boards` tool with
   `limit: 1`. Never create, update, or delete a board during setup.
   - Success verifies API access; report only the count returned, not board names, IDs, or URLs.
   - A tool error saying `miro_api_token` is not set means the token is unconfigured: report
     `token not set` and direct the user to `/plugin configure miro@<marketplace>`, then
     `/reload-plugins`. An authentication failure gets the same direction.
   - Network, rate-limit, or service failure is reported as a distinct degraded state; do not tell the
     user to replace a credential unless the response identifies authentication as the cause.

## Headless installation

For a non-interactive install, CI, a fleet bootstrap, or a scripted machine setup, seed the token
on the initial install instead of the interactive `/plugin` prompt. Three steps, all required:

```shell
claude plugin marketplace add <source> --scope <scope>
claude plugin install miro@<marketplace> -s <scope> --config miro_api_token=<token>
claude plugin enable miro -s <scope>
```

Both placeholders are bootstrap inputs, not lookups: before the first install there is no record
to read them from. `<marketplace>` is the name the catalog registers under when it is added, and
`<scope>` is the scope the bootstrap chooses: `user`, `project`, or `local`. Pass the scope
explicitly on all three commands and carry the same `<scope>` through them; never rely on a
command's default. Each command's scope flag spelling and default are read live:

- **Pointer**: when writing or debugging the bootstrap, fetch
  [`plugin marketplace add`](https://code.claude.com/docs/en/plugins/cli-reference#plugin-marketplace-add),
  [`plugin install`](https://code.claude.com/docs/en/plugins/cli-reference#plugin-install) and
  [`plugin enable`](https://code.claude.com/docs/en/plugins/cli-reference#plugin-enable) live.
- **As of**: 2026-10-11
- **Recheck trigger**: any of those sections changes its scope option, short form or default.

Registering at `user` while
installing at `project` leaves the marketplace declaration out of the project's checked-in
settings, so a fresh clone or CI agent carries the enabled plugin with no registered marketplace
to resolve it from.

**The enable step is not optional.** This plugin ships `defaultEnabled: false`, so it installs
DISABLED. The install seeds the token but leaves the MCP server, and therefore every `miro` tool,
unavailable until it is enabled ([Default enablement](https://code.claude.com/docs/en/plugins/manifest-reference#defaultenabled)).
Passing the scope to `claude plugin enable` explicitly keeps the sequence deterministic in CI. A
bootstrap that stops after `install` looks
successful and delivers no tools.

**Rotating or clearing the token:** `/plugin configure miro@<marketplace>` (interactive, any
time) is the recommended rotation path regardless. It masks input, unlike anything passed on the
command line (see the security note below).

Per the marketplace's plugin-reconfiguration convention
(<https://github.com/melodic-software/claude-code-plugins/blob/main/docs/conventions/plugin-reconfiguration/README.md>,
which owns the verified-version record), a headless `claude plugin install … --config` rerun
against an already-installed plugin prints `already installed` and still writes the value, but
that record covers only a non-sensitive option, so do not rely on it for a `sensitive` credential
such as `miro_api_token`. Do **not** uninstall to rotate either: uninstalling drops this
plugin's entire stored `pluginConfigs` entry, resetting every option in the README's Options
reference to its manifest default, and it can drop the `enabledPlugins` entry as well; a
`defaultEnabled: false` plugin reinstalls DISABLED, so a rotation ending at `install` delivers no tools.

**Security note:** passing the token as a CLI argument records it in shell history
(`.bash_history`, `.zsh_history`) and briefly exposes it in the process table
(`/proc/<pid>/cmdline`, `ps aux`) while the command runs, unlike the interactive `/plugin`
prompt, which masks input and touches neither surface. In CI/CD, route the value through your
secrets manager rather than inlining it literally.

## Output

Report one state: `disabled`, `server unavailable`, `server ready (token not checked)`,
`token not set`, `API access verified`, or `API verification degraded`. Include the exact next action when the state is
not verified.

Claude Code keeps sensitive option values in its own secure credential storage. Never read or
reveal the contents of wherever it keeps them.

- **Pointer**: when a user asks where the token is stored, fetch
  [Plugins reference: Where values are stored](https://code.claude.com/docs/en/plugins/manifest-reference#where-values-are-stored)
  live and give them its answer.
- **As of**: 2026-10-11
- **Recheck trigger**: that section changes where sensitive values are kept.

## Boundaries

- Do not read, echo, log, copy, or persist the token.
- Do not write the plugin cache, Claude Code user settings, or `pluginConfigs`, per the uniform
  setup contract (`docs/plugin-philosophy.md` "Setup is explicit and repeatable" in the
  marketplace repository).
- Do not make a Miro API request without explicit confirmation.
- Do not invoke a mutating Miro tool during setup.
- Do not claim success from tool presence alone when the user requested API verification.
Files in this package (2)
  • SKILL.md 10 KB
  • evals/evals.json 2 KB

Versions

RepositoryScoreLicence
This page · melodic-software/claude-code-plugins84MIT
HwangSlater/harness-fit100MIT
nesquikm/dev-process-toolkit100MIT
userKael/rastro100MIT
als-apg/osprey100BSD-3-Clause
dedujeong/gemba100Apache-2.0
eigenwise/eigenwise-toolshed100MIT
awrshift/agent-memory-kit100MIT
lifecycle-innovations-limited/claude-ops100MIT

Database snapshot: 13.11.2026 · package version 8d97f7cfa8f1 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95miro-mcp
    This skill teaches how to use Miro MCP tools effectively for creating diagrams, documents, tables, and extracting context from Miro boards. Use when the user asks about Miro capabilities, wants to create content on Miro boards, or needs to work with Miro board data.
  • 100miro-common-errors
    Diagnose Miro OAuth and REST failures from status, context, scopes, rate headers, and safe evidence. Use when a Miro integration returns errors. Trigger with \"debug Miro API error\".
  • 100miro-deploy-integration
    Prepare and verify repository-side deployment configuration for a Miro service with isolated settings, health checks, canaries, rollback, and an approval-gated live handoff. Use when promoting a Miro-backed release. Trigger with \"miro integration deployment\".
  • 95miro-spec-guide
    Learn how to extract Miro specifications to local files and use them for AI-assisted planning and implementation. Use when working with Miro specs or when user wants to download board content for reference.
  • 100miro-use-case-diagram
    Draw or update a UML use case diagram on a Miro board (actors, system boundary, use cases, «include»/«extend»). Use when the user asks to create, draw, sketch, or update a use case diagram, actor diagram, or "who does what with the system" view on Miro. Not for sequence or data…
  • 100miro-data-flow-diagram
    Draw or update a data flow diagram on a Miro board (Gane-Sarson symbols, context/level 1, trust boundaries, personal-data markers). Use when the user asks to create, draw, or update a DFD, context diagram, level 0/1 diagram, or trust-boundary / data-residency view on Miro. Not…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.