Agent skill · data analytics · jeremylongshore
miro-data-handling
Design and implement repository-side controls for Miro reads, storage, exports, redaction, retention, and deletion by purpose and data class. Use when processing collaborative board content. Trigger with \"miro board data handling\".
Why this skill is useful
Adds executable scripts for PII detection and GDPR/CCPA compliance that are not commonly known or documented.
What it needs
Requires miro installed locally. Requires 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 Board Data Handling Overview Assume collaborative canvases can contain personal, confidential, regulated, or credential-like material; use the evidence produced here to make the next decision explicit and reviewable. Prerequisites Approved Miro application, tenant, and board scope Current repository and deployment evidence Named owner, success criteria, and rollback or recovery boundary 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 Board read scope can expose metadata, members, and item content. Resource URLs and payloads must not enter logs or debug bundles. Enterprise export/audit/organization scopes require plan and role checks. Stored Miro data needs application-layer authentication and authorization. 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. Map each field to purpose, source, class, owner, destination, retention, and deletion. 2. Minimize boards, item types, fields, windows, and tenants. 3. Pseudonymize operational identifiers and keep content out of telemetry. 4. Enforce tenant authorization, encryption, access logs, expiry, and deletion paths. 5. Test deletion, revoked access, cross-tenant denial, redaction, and backup expiry. 6. Block any field without purpose, owner, retention, or access policy. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/miro-data-handling