Index of every page on this site: llms.txt
All skills
Run it yourself

Design and implement a production Miro REST authorization flow with least-privilege scopes, tenant-bound storage, token rotation, and an approval-gated installation handoff. Use when installing or repairing Miro authorization. Trigger with "set up Miro OAuth".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/miro-install-auth

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈70 tokens for metadata: the name and description. ≈1k when used: this file. ≈309 more on demand in 1 file.

Description uses 3.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈280 characters, or 3.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Miro OAuth Installation and Token Lifecycle

Overview

Establish an auditable authorization boundary before any board operation. Prefer expiring-token apps and prove tenant context without exposing credentials; use the evidence produced here to make the next decision explicit and reviewable.

Prerequisites

  • A Miro Developer team and an app configuration for the target environment
  • Approved redirect URIs and a server-side encrypted token store
  • A capability-to-scope map and accountable installation owner

Tool Discipline

Use Read, Glob, and Grep to inspect the repository, configuration names, adapters, tests, and evidence. Use WebFetch only for current official Miro documentation. Use Write or Edit after confirming the requested mode, target environment, tenant, board, and approval boundary. These declared tools do not call authenticated Miro APIs or deployment CLIs; implement client, configuration, and test changes, then return exact operator commands or an approval-gated handoff for live execution.

Current Contract

  • REST apps use OAuth 2.0 Authorization Code; authorization starts at https://miro.com/oauth/authorize and exchange uses https://api.miro.com/v1/oauth/token.
  • The REST resource base is https://api.miro.com/v2; OAuth endpoints remain v1 and are not deprecated by the REST v2 migration.
  • Expiring-token mode provides a one-hour access token and a sixty-day refresh token; refresh rotates both values and invalidates the prior pair.
  • Token-expiration mode is chosen when the app is created and cannot later be enabled, disabled, or changed.

Authentication

For REST work, use OAuth 2.0 Authorization Code with the narrowest Miro scopes. Bind each encrypted token record to its user, application, authorized team, and granted scopes. Never print access tokens, refresh tokens, client secrets, authorization codes, or board content.

Instructions

  1. Inventory environments, redirect URIs, requested capabilities, scopes, and installation owners.
  2. Create or inspect the environment-specific app and select expiring-token mode for new production apps.
  3. Generate the authorization URL with an unguessable, session-bound state value and an exact registered redirect URI.
  4. Exchange the single-use code server-side, atomically store both tokens and expiry metadata, and discard the code.
  5. Call access-token context, compare the returned user/team context with the intended tenant, then perform a read-only board probe.
  6. Exercise refresh rotation, concurrent-refresh locking, revocation, reinstall, and recovery before enabling writes.

Approval Boundaries

Do not add scopes, register a new redirect origin, create a production app, or authorize a different team without the application and data owners' approval. Pause when the responsible owner or exact target is uncertain.

Output

Return app/environment identity, redirect-URI match, approved scopes, token mode, context result, refresh/revocation evidence, and remaining risks. State what was not inspected or changed so the receipt cannot overclaim coverage.

Error Handling

Condition Response
OAuth callback has an error or state mismatch Reject it; do not exchange the code, and restart from a clean session.
Token exchange returns 400 Check one-time code use, exact redirect URI, app identity, and server clock.
Context resolves to the wrong team Quarantine the token and require an intentional reinstall.
Refresh races or returns invalid grant Serialize rotation per installation and recover through reauthorization if the stored pair is stale.

Examples

The example is a redacted operator receipt; identifiers are hashes or bounded labels, not board content or credentials.

environment=staging; scopes=boards:read; expiring=yes; context=matched; refresh-rotation=passed; write-access=disabled

Resources

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides safe and standard instructions for configuring Miro REST API v2 authentication using official libraries and security best practices.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated 2 months ago
What it can do
Reads files Network Edits files
Modelinherit
argument-hint
[app-environment] [required-capabilities]
version
1.9.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 6 allowed tools
ReadGlobGrepWebFetchWriteEdit
Other metadata
tags
[
  "saas",
  "miro",
  "oauth",
  "authentication"
]
model
inherit
effort
high
compatibility
Designed for Claude Code; live work requires an authorized Miro app and redacted evidence

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/miro-install-auth