Files
Naman 5a2fada0f1 feat: migration skill family + URL audit (.createos.io → .createos.nodeops.network) (#11)
* feat: add migration skill family; fix legacy .createos.io domain

Migration skill family (new):
- skills/vercel-to-createos — live, end-to-end tested against CreateOS
  MCP. CreateProject (Pattern A: useBuildAI; Pattern B: explicit
  commands) and CreateProjectEnvironment shapes verified.
- skills/{netlify,railway,heroku,render,flyio}-to-createos — reserved
  stubs routing users to concierge migration until they ship.
- MIGRATIONS.md — category index at repo root (flat layout because the
  skills CLI does not resolve nested category paths).
- README.md — adds vercel-to-createos row + migration section.
- skills/createos/SKILL.md — "See also" cross-link to migration family.

URL audit (existing skill):
- Replaced legacy .createos.io domain (DNS unreachable) with current
  .createos.nodeops.network across createos/SKILL.md, references/
  api-reference.md, references/deployment-patterns.md, and scripts/
  quick-deploy.sh.

Known issues flagged in PR body:
- https://createos.nodeops.network/migrate currently 404s.
- Stray skills/SKILL.md (untracked, pre-existing) deliberately not
  included in this commit.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* fix(migrate): swap /migrate 404 URL for mailto:business@nodeops.xyz

The concierge migration URL referenced throughout the migration skill
family (https://createos.nodeops.network/migrate) currently 404s. Until
the landing page exists, route users to the business inbox instead.

Affects 15 references across 8 tracked files (vercel + 5 stubs, plus
MIGRATIONS.md and the createos See also section).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* fix(createos): MCP endpoint path is /mcp not /sse in quick-deploy.sh

One-off inconsistency caught by @pratikbin in PR review. Every other
reference in the createos skill (SKILL.md, config.json,
deployment-patterns.md) already uses /mcp — this was the lone holdout.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Naman <naman307@Namans-MacBook-Pro.local>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-20 15:41:59 +05:30

81 lines
2.5 KiB
Markdown

# NodeOps Skills
AI agent skills for the [NodeOps](https://nodeops.network) ecosystem. Works with Claude Code, Cursor, Windsurf, and 40+ other AI coding agents via the [skills](https://skills.sh) CLI.
## Available Skills
| Skill | Description | Install |
|-------|-------------|---------|
| **createos** | Deploy anything to production on CreateOS cloud platform | `npx skills add https://github.com/NodeOps-app/skills --skill createos` |
| **vercel-to-createos** | Migrate Next.js, Vite, React, Vue, Svelte apps from Vercel to CreateOS | `npx skills add https://github.com/NodeOps-app/skills --skill vercel-to-createos` |
### Migration skills
`vercel-to-createos` is the first shipped skill in the migration family. Stubs for `netlify-to-createos`, `railway-to-createos`, `heroku-to-createos`, `render-to-createos`, and `flyio-to-createos` are reserved and route users to the concierge migration path until they ship. See [MIGRATIONS.md](./MIGRATIONS.md) for the full list and roadmap.
## CreateOS Authentication
The `createos` skill can be used in two modes:
- MCP mode (preferred when available): authentication is handled by the MCP server (no API key needed).
- REST/script mode: you must provide an API key via `CREATEOS_API_KEY`.
For REST/script usage:
```bash
export CREATEOS_API_KEY="<your-createos-api-key>"
```
Never commit API keys to git; prefer setting them in your shell or your agent environment.
## Installation
Install a specific skill:
```bash
npx skills add https://github.com/NodeOps-app/skills --skill createos
```
Install to a specific agent:
```bash
npx skills add https://github.com/NodeOps-app/skills --skill createos -a claude-code
```
List all available skills:
```bash
npx skills add https://github.com/NodeOps-app/skills --list
```
## Adding a New Skill
1. Create a new directory under `skills/` with your skill name:
```
skills/
└── your-skill/
└── SKILL.md
```
2. Add a `SKILL.md` with frontmatter:
```markdown
---
name: your-skill
description: What the skill does and when to activate it.
---
# Your Skill
Instructions for the agent...
```
3. Optionally add supporting files:
```
skills/your-skill/
├── SKILL.md # Required: skill definition
├── config/ # Optional: configuration files
├── references/ # Optional: extended documentation
├── scripts/ # Optional: helper scripts
└── assets/ # Optional: templates, images
```