feat: add netlify-to-createos migration skill#20
Conversation
| ## Prerequisites | ||
|
|
||
| Before running any migration steps, confirm the user has: | ||
|
|
There was a problem hiding this comment.
Do i need to do something about this yet?
|
|
||
| Before running any migration steps, confirm the user has: | ||
|
|
||
| 1. A CreateOS account — if not, direct them to `https://createos.nodeops.network` to sign in via Email, GitHub, Google, or Wallet. |
There was a problem hiding this comment.
@adityachaudhary99 only email and google login, no wallet, github login
| Before running any migration steps, confirm the user has: | ||
|
|
||
| 1. A CreateOS account — if not, direct them to `https://createos.nodeops.network` to sign in via Email, GitHub, Google, or Wallet. | ||
| 2. CreateOS MCP connected OR a `CREATEOS_API_KEY` environment variable set. |
There was a problem hiding this comment.
you mean CreateOS MCP login using oauth or ....
There was a problem hiding this comment.
I meant the user has the CreateOS MCP server configured in their opencode.json / claude. (the MCP client setup), not OAuth. The alternative is using a CREATEOS_API_KEY env var for REST API fallback. The wording could be clearer? maybe "CreateOS MCP server configured in opencode.json or Claude Desktop" instead.
|
|
||
| 1. A CreateOS account — if not, direct them to `https://createos.nodeops.network` to sign in via Email, GitHub, Google, or Wallet. | ||
| 2. CreateOS MCP connected OR a `CREATEOS_API_KEY` environment variable set. | ||
| 3. Access to their current Netlify project's environment variables (they may need to export these from the Netlify dashboard). |
There was a problem hiding this comment.
If we can utilize Netlify-CLI (https://docs.netlify.com/api-and-cli-guides/cli-guides/get-started-with-cli/) to smooth the migration
There was a problem hiding this comment.
sure I could try that
|
|
||
| - `netlify.toml` — build, redirect, header, and function configuration | ||
| - `package.json` — detect framework, build scripts, and Node.js version | ||
| - `next.config.js` / `next.config.mjs` / `next.config.ts` — Next.js specific configuration |
There was a problem hiding this comment.
this should be more generic since you're mentioning "detected project" below
There was a problem hiding this comment.
Will replace the hardcoded next.config.* / .nvmrc lines with a generic "Framework-specific config files" line. Good?
| | Netlify Identity | Use Auth0, Clerk, Supabase Auth, or NextAuth | | ||
| | Split Testing | App-level A/B testing (e.g., GrowthBook, LaunchDarkly) | | ||
| | Large Media | Use any S3-compatible object storage | | ||
| | Build hooks / webhooks | Use CreateOS API `POST /v1/projects/{id}/trigger-latest` | |
There was a problem hiding this comment.
CreateOS handling -> ...or works out of the box with github
There was a problem hiding this comment.
Will append "or works out of the box with GitHub (git push → auto-deploy)" to that row.
Full migration skill replacing the stub. Parses netlify.toml, maps build settings and environment variables, flags incompatibilities (Edge Functions, Forms, Identity), and guides deployment via the CreateOS MCP server. Includes: - MCP-tool-first SKILL.md matching vercel-to-createos pattern - config/config.json with runtime/framework/platform mappings - references/ with netlify-toml reference and migration patterns - scripts/ with parse-netlify-config.sh and migrate-env.sh helpers - Updated README.md and MIGRATIONS.md tables
3 participants
Summary
Replaces the netlify-to-createos stub with a fully implemented migration skill. Follows the same MCP-tool-first pattern as \�ercel-to-createos.
Changes
Testing
End-to-end migration test passed against netlify-templates/next-netlify-starter — parsed netlify.toml + package.json, created matching CreateOS project with all settings, verified project and environment.
Notes