miro-ci-integration
Configure CI/CD pipelines for Miro REST API v2 integrations with GitHub Actions, test board isolation, and automated validation. Trigger with phrases like "miro CI", "miro GitHub Actions", "miro automated tests", "CI miro", "miro pipeline". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill miro-ci-integration --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Miro CI Integration ## Overview Set up CI/CD pipelines for Miro REST API v2 integrations with isolated test boards, proper secret handling, and API validation in GitHub Actions. ## Prerequisites - GitHub repository with Actions enabled - Miro app with test credentials (separate from production) - A dedicated test board ID for integration tests ## GitHub Actions Workflow ```yaml # .github/workflo
What does the miro-ci-integration skill do?
Configure CI/CD pipelines for Miro REST API v2 integrations with GitHub Actions, test board isolation, and automated validation. Trigger with phrases like "miro CI", "miro GitHub Actions", "miro automated tests", "CI miro", "miro pipeline". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill miro-ci-integration --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.