Agent skill · software engineering · jeremylongshore
miro-ci-integration
Design and implement repository-side Miro CI gates with schema-faithful fixtures, protected live-test handoffs, test-board isolation, and cleanup proof. Use when adding Miro checks to CI. Trigger with \"test Miro in CI\".
Why this skill is useful
Adds a complete CI/CD pipeline configuration for Miro API integrations, including executable scripts and specific GitHub Actions workflows.
What it needs
Requires gh, jq installed locally. Requires github, miro account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Miro CI Contract Tests Overview Keep pull-request checks credential-free and reserve live Miro calls for protected, explicitly scoped lanes. A test must never mutate a collaboration board by accident; use the evidence produced here to make the next decision explicit and reviewable. Prerequisites CI trust-boundary and fork policy Pinned schemas/fixtures and test command Dedicated app, team, board, identity, and cleanup owner for live tests 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 Untrusted fork workflows must not receive Miro credentials. Live traffic consumes production-like per-user/application credits even on test resources. Bulk create is transactional but cleanup still needs an explicit inventory and board guard. OAuth refresh rotation can invalidate concurrent jobs sharing one installation. 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. Split formatting, unit, schema, security, and fixture tests from the protected live lane. 2. Assert that PR/fork lanes have no credential context and cannot invoke live helpers. 3. Pin dependencies and validate captured fixtures against current official response contracts. 4. Serialize protected live jobs per installation, assert app/team/board guards, and use bounded read-first tests. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/miro-ci-integration