By CloudCannon
Migrate static site generator sites to CloudCannon CMS, including site configuration, visual editing, snippet support, and an end-to-end migration workflow.
Use before any creative or architectural work — migrations, adding features, restructuring, or modifying site behavior. Explores intent, requirements, and design before implementation.
Use when configuring a site for CloudCannon for any of the following. Download the JSON schemas before writing any configuration (see the top of SKILL.md). - Setting up cloudcannon.config.yml or .cloudcannon/initial-site-settings.json - Generating a baseline with the CloudCannon CLI - Adding or modifying Collections, Inputs, Structures, or Select Data - Setting up Structures for Array and Object Inputs - Configuring Collection URLs - Troubleshooting missing fields or Input types
Use when adding snippet support to a CloudCannon site, configuring MDX components for the Content Editor, debugging snippet round-trip issues, or setting up inline HTML snippets in markdown content.
Use when adding Visual Editor support to a CloudCannon site, setting up editable regions, debugging visual editing issues, or making page sections editable in the CloudCannon preview.
Migrate an existing SSG site to work with CloudCannon. Use when the user wants to onboard a site to CloudCannon, add CMS support, or make a template CloudCannon-compatible.
Based on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Agent skills that help AI coding agents migrate existing SSG sites to CloudCannon. Copy the skills into your project, open it in your AI coding agent, and ask it to migrate your site.
Run npx skills add CloudCannon/agent-skills in the root of your project
Open your project in your AI coding agent
Ask the agent to migrate your site to CloudCannon, following a suggested prompt:
For a full migration:
Migrate this site to CloudCannon using the migrating-to-cloudcannon skill. If the skill is not found, look in .agents/, otherwise do not continue.
Or, for creating configuration:
Create CloudCannon configuration files using the cloudcannon-configuration skill. If the skill is not found, look in .agents/, otherwise do not continue.
Or, for setting up Visual Editing:
Configure Visual Editing for CloudCannon using the cloudcannon-visual-editing skill. If the skill is not found, look in .agents/, otherwise do not continue.
The agent should pick up skills automatically based on their trigger descriptions in SKILL.md.
If you use Claude Code, you can install all five skills as a plugin instead of copying them in. Add the marketplace, then install the plugin:
/plugin marketplace add CloudCannon/agent-skills
/plugin install agent-skills@cloudcannon
The skills are then available namespaced as agent-skills:<skill-name> (e.g. agent-skills:migrating-to-cloudcannon), and Claude picks them up automatically based on their trigger descriptions — same as the copy-in route above.
| SSG | Status |
|---|---|
| Astro | Supported |
More SSGs are planned. Each SSG has its own directory within the relevant skills containing SSG-specific guidance.
The tooling is split across composable skills that can be used together or independently.
| Skill | Purpose | When to use |
|---|---|---|
migrating-to-cloudcannon | Full migration orchestrator | Migrating a site to CloudCannon end-to-end (audit, configure, content, visual editing, build) |
cloudcannon-configuration | CloudCannon config setup | Setting up cloudcannon.config.yml, collections, inputs, structures, or the CloudCannon CLI |
cloudcannon-snippets | Snippet configuration | Configuring MDX components or inline HTML for CloudCannon's Content Editor |
cloudcannon-visual-editing | Visual Editor support | Adding editable regions so page content can be edited inline in CloudCannon's Visual Editor |
brainstorming | Structured design exploration | Exploring intent, requirements, and tradeoffs before implementation |
For a full migration, start with migrating-to-cloudcannon -- it orchestrates the other skills at the right time. The standalone skills (cloudcannon-configuration, cloudcannon-snippets, cloudcannon-visual-editing) are useful when you only need one piece, e.g. "add visual editing to my existing CloudCannon site".
A full migration runs through five phases:
cloudcannon-configuration and optionally cloudcannon-snippets)cloudcannon-visual-editing)Each phase has a verification checklist. The agent reads docs just-in-time during each phase rather than front-loading everything. Deterministic steps are automated as scripts to save tokens and improve consistency.
Not every site needs all phases. Small sites may skip content restructuring. Visual editing is optional but high-value.
skills/
migrating-to-cloudcannon/ # Migration orchestrator
cloudcannon-configuration/ # Config skill (standalone)
cloudcannon-snippets/ # Snippets skill (standalone)
cloudcannon-visual-editing/ # Visual editing skill (standalone)
brainstorming/ # Design exploration skill
npx claudepluginhub cloudcannon/agent-skills --plugin agent-skillsMatt Pocock's agent skills for real engineering — grilling, spec/ticket flows, TDD, code review, domain modelling and more. Plug-and-play, not vibe coding.
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Design fluency for frontend development. 1 skill with 23 commands (/impeccable polish, /impeccable audit, /impeccable critique, etc.) and curated anti-pattern detection.
Harness-native ECC plugin for engineering teams - 67 agents, 279 skills, 94 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses
Lazy senior dev mode. Forces the simplest, shortest solution that actually works: YAGNI, stdlib first, no unrequested abstractions.