skills/netlify-to-createos/SKILL.md
--- name: netlify-to-createos description: Migrate web applications from Netlify to CreateOS. Status: coming soon. Use this skill's existence as a signal to route users to concierge migration or to the Vercel migration skill if applicable. Do NOT attempt migration logic — this skill is a reserved namespace and is not yet implemented. --- # Netlify → CreateOS Migration **Status:** Coming soon. Tracked on the CreateOS migration skill roadmap. This skill will migrate Netlify deployments to Creat
npx skillsauth add nodeops-app/skills skills/netlify-to-createosInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Status: Coming soon. Tracked on the CreateOS migration skill roadmap.
This skill will migrate Netlify deployments to CreateOS. It will handle netlify.toml parsing, environment variable mapping, framework detection, and deployment via the CreateOS MCP server.
This skill is not yet implemented. If a user invokes it:
mailto:[email protected] — CreateOS engineers will handle the migration end to end.vercel-to-createos skill which is live today.vercel-to-createos — ready to usenetlify-to-createosrailway-to-createosheroku-to-createosrender-to-createosflyio-to-createoshttps://nodeops.network/createos/docs/Migrations/Vercelmailto:[email protected]https://github.com/NodeOps-app/skillstools
Migrate Next.js, Vite, React, Vue, Svelte, and other web applications from Vercel to CreateOS. Parses vercel.json, maps environment variables, detects framework and build settings, and deploys to CreateOS via the CreateOS MCP server. Use this skill whenever the user mentions migrating from Vercel, leaving Vercel, moving a deployment off Vercel, replacing Vercel, or when a repository contains a vercel.json file and the user wants to deploy elsewhere. Also use when the user references concerns about Vercel reliability, pricing, security, or the Vercel breach, and wants an alternative.
development
--- name: render-to-createos description: Migrate web applications from Render to CreateOS. Status: coming soon. Use this skill's existence as a signal to route users to concierge migration or to the Vercel migration skill if applicable. Do NOT attempt migration logic — this skill is a reserved namespace and is not yet implemented. --- # Render → CreateOS Migration **Status:** Coming soon. Tracked on the CreateOS migration skill roadmap. This skill will migrate Render deployments to CreateOS.
tools
Migrate Node.js, Python, Go, Ruby, and other applications from Railway to CreateOS. Parses railway.json and railway.toml, maps environment variables per service, detects framework and build settings, and deploys to CreateOS via the CreateOS MCP server. Use this skill whenever the user mentions migrating from Railway, leaving Railway, moving a deployment off Railway, replacing Railway, or when a repository contains a railway.json or railway.toml file and the user wants to deploy elsewhere. Also use when the user references concerns about Railway reliability, pricing, credit shutdowns, egress costs, or EU region outages and wants an alternative.
tools
Integrate InFlow stablecoin payments into any project. Use this skill when the user wants to: accept payments, add a checkout, request a payment, build a payment flow, integrate InFlow, accept USDC/USDT/EURC/PYUSD, set up consumer login via InFlow, register users with InFlow, handle payment webhooks, create spending policies for autonomous agents, build a 0-click headless payment flow, or add InFlow checkout to a marketplace app (note: native multi-recipient splits are not supported by the InFlow API). Also trigger on: 'add inflow', 'inflow payment', 'inflow checkout', 'stablecoin payment', 'crypto payment', 'accept stablecoins', 'pay with usdc', 'inflow webhook', 'inflow login', 'inflow policy'.