# Automate Miro Board Workflows

Manual board setup and maintenance consume collaboration time. This skill uses Rube MCP to find, create, organize, connect, and share Miro content.

## Install

```bash
npx skillstore add sickn33/miro-automation
```

## Metadata

- Status: approved
- Slug: sickn33-miro-automation
- Skillstore revision: r2
- Version status: missing
- Tree hash: 2e49c0b52b94c36d11ed069ecc6596a472a4c4f23829aa959168f4e4728d59e9
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/miro-automation
- Ref: 81e05e636292629114b76cbb3922fbe57672fc02
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 50
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/sickn33-miro-automation
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-miro-automation/manifest

## Capabilities

- Searches current Rube MCP tool schemas before selecting Miro operations.
- Lists Miro boards and resolves board names to board identifiers.
- Creates boards, sticky notes, frames, and multiple items in bulk.
- Lists board items and connectors with the required pagination method.
- Shares boards with specified email addresses and access roles.
- Uses positions, dimensions, colors, and item identifiers to organize board content.

## Use Cases

- Prepare a Workshop Board: Create frames and color-coded sticky notes for workshop topics, then place them in a clear board layout.
- Map Product Work: Find an existing planning board, add grouped work items, and connect related items for review.
- Manage Board Access: Locate a board, review its members, and prepare invitations with defined viewer, commenter, or editor roles.

## Prompt Templates

### Find a Board

```
Find Miro boards matching [name]. List the closest matches with modification details, and do not change any board.
```

### Create a Workshop Layout

```
Create a Miro board named [name] with frames for [sections]. Preview the layout and sticky note text before creating anything.
```

### Organize Existing Items

```
On board [name], find [item types], group them by [rule], and propose positions and connectors. Ask for approval before applying changes.
```

### Build and Share a Planning Board

```
Build a planning board from [content], use bulk creation where supported, validate pagination, then preview recipients and roles before sharing.
```

## Limitations

- Requires Rube MCP, a Miro OAuth connection, and sufficient Miro workspace permissions.
- Available operations and parameters depend on the current Rube MCP tool schemas.
- Miro rate limits, item limits, and organization policies can restrict workflows.
- The documented workflows do not provide transaction rollback for completed changes.

## Best Practices

- Resolve board names to identifiers and confirm the selected board before making changes.
- Search current tool schemas and validate required fields before every workflow.
- Preview content, recipients, and access roles before any create or share operation.

## Anti Patterns

- Do not hardcode board or item identifiers across Miro accounts.
- Do not invite users or assign editor access without explicit approval.
- Do not ignore pagination when listing boards, items, members, or connectors.

## Security Audit

- Audited at: 2026-08-04T14:20:34.34\+00:00
- Summary: All 54 shell-execution alerts and seven reconnaissance alerts are false positives caused by Markdown and Miro terminology. The external Rube endpoint is a real trust boundary. State-changing and sharing actions also need explicit confirmation.

## Stats

- Views: 111
- Downloads: 10
- Favorites: 0
- Popularity score: 0