mirror of https://github.com/NodeOps-app/skills.git synced 2026-09-19 07:25:09 +08:00

T

pratikbin e7dce93833 feat(createos-deploy): ship runnable deploy script

The skill only had a TypeScript sample. Using it meant creating a
scratchpad, installing viem, and rewriting the sample before deploying.
The sample also hardcoded a two-file upload, so the file list had to be
written by hand.

Add deploy.mjs plus a pinned package.json, and fix the gaps found while
deploying a real Go project with this skill:

- Collect files with git ls-files instead of by hand. It honours
  .gitignore, so build output and node_modules drop out with no list.
- Filter secrets. An untracked .env is not ignored by git, so it reached
  the upload. That file usually holds the wallet key paying for the
  deploy.
- Filter agent and editor tooling. In a six-file Go project, .agents/
  added 39 files and grew the upload from 8 KB to 649 KB.
- Require --port. A wrong port only shows after payment: the deploy
  reports ready and the endpoint answers nothing.
- Gate the payment behind --yes, and print the price first. The floor is
  $0.50 but a real quote came to $1.81.
- Check the endpoint after ready, so a wrong port fails loudly.
- List existing projects, to name what a credit-sharing warning risks.

Docs: document the git collection step, port discovery, the price gate,
and that this gateway ignores createos.json. One Go project declared
node:20, reactjs-spa, and port 80 for a server listening on 8080.

Redeploying under an existing uniqueName stays an open question. It is
flagged as unverified rather than guessed, because names are validated
only after payment.

viem is pinned to 2.55.19, the current latest stable. Lock files stay
untracked: the exact pin already fixes the version, and a lock file only
creates churn when the skill is copied into a project.

2026-08-26 15:15:33 +05:30

skills

feat(createos-deploy): ship runnable deploy script

2026-08-26 15:15:33 +05:30

.gitignore

feat: initial commit

2026-02-09 11:52:01 +05:30

MIGRATIONS.md

feat: migration skill family + URL audit (.createos.io → .createos.nodeops.network) (#11 )

2026-04-20 15:41:59 +05:30

package.json

feat: initial commit

2026-02-09 11:52:01 +05:30

README.md

feat: claude to codex migration skills (#16 )

2026-05-18 11:44:58 +05:30

README.md

NodeOps Skills

AI agent skills for the NodeOps ecosystem. Works with Claude Code, Cursor, Windsurf, and 40+ other AI coding agents via the skills 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`
claude-code-to-codex	Migrate Claude Code CLI hooks, MCP servers, plugins, instructions, and sessions to Codex CLI	`npx skills add https://github.com/NodeOps-app/skills --skill claude-code-to-codex`

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 for the full list and roadmap.

Agent migration skills

claude-code-to-codex migrates Claude Code CLI setups to Codex CLI, with focused coverage for hooks, Claude Code CLI MCP servers, plugins, and session handoff.

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:

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:

npx skills add https://github.com/NodeOps-app/skills --skill createos

Install to a specific agent:

npx skills add https://github.com/NodeOps-app/skills --skill createos -a claude-code

List all available skills:

npx skills add https://github.com/NodeOps-app/skills --list

Adding a New Skill

Create a new directory under skills/ with your skill name:
```
skills/
└── your-skill/
    └── SKILL.md
```

Add a SKILL.md with frontmatter:

---
name: your-skill
description: What the skill does and when to activate it.
---

# Your Skill

Instructions for the agent...

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