Skills

CloudGrid Skills are capability files (SKILL.md) that teach an agent — Claude Code, Cursor, Codex, and any tool that reads skills — how to work with CloudGrid. With them installed, the agent can deploy, sign in, share a link, tail logs, and scaffold a project directly, instead of you hand-driving each command.

The skills are published as @cloudgrid-io/skills from the cloudgrid-io/skills repository.

What gets installed

• The skills bundle — the SKILL.md capability files the agent reads to learn each CloudGrid action.
• The CloudGrid CLI (@cloudgrid-io/cli, the grid command).

The skills wrap the grid CLI — every skill drives grid under the hood — so the CLI is always needed. You don’t have to install it yourself, though: the one-command setup installs it upfront, and on the per-agent methods the skills install it on first use (the agent runs grid --version and, if that fails, npm install -g @cloudgrid-io/cli). The only step that always needs you is signing in with grid login. See Install for the CLI on its own.

Install

One command (recommended)

Clone the repository and run its setup script. setup installs everything, including the CLI:

git clone https://github.com/cloudgrid-io/skills.git
cd skills
./setup

setup runs a short sequence. Step 1 (Step 1/4: CloudGrid CLI) checks for grid on your PATH and, if it is missing, installs @cloudgrid-io/cli with npm. It then checks authentication, detects your agent, and installs the skills. Pass --skip-cli to opt out of the CLI step (for example if you manage grid yourself), or --host <claude|cursor|codex> to override agent detection.

Per-agent

These add just the skill files. The skills install the CLI on first use if it’s missing, so you can skip straight to adding them. If you prefer to install it upfront:

npm install -g @cloudgrid-io/cli
grid login

Either way, sign in with grid login when prompted — the skills never log in for you. Add the skills for your agent:

Claude Code

/plugin marketplace add cloudgrid-io/skills
/plugin install cloudgrid@cloudgrid-skills

Installing the plugin bundles the skills, the session-start orientation hook, and the CloudGrid MCP server, which starts automatically — no separate MCP setup is needed. The skills appear under /plugin and /skills as cloudgrid:plug, cloudgrid:login, and so on.

gh skill extension

gh skill install cloudgrid-io/skills

skills CLI (Cursor, Cline, Gemini CLI, and others)

npx skills add cloudgrid-io/skills

On the gh and npx routes the skills install under their bare names (plug, login, …) because the cloudgrid: prefix comes from the Claude Code plugin namespace.

Why use them

Agents can write code; the skills let an agent also ship it. Once installed, you can describe what you want — “share this HTML page as a link”, “deploy this folder”, “show me the logs” — and the agent runs the matching CloudGrid action through the grid CLI, without you typing the commands.

Shipped skills

Skill	Invoke (Claude Code)	What it does
login	/cloudgrid:login	Sign in to CloudGrid, with or without the CLI.
claim	/cloudgrid:claim	Claim an anonymous drop into your account after signing in.
init	/cloudgrid:init	Scaffold a new app or agent.
plug	/cloudgrid:plug	Share a single HTML page (login optional) or deploy a directory or URL, and get a public URL.
logs	/cloudgrid:logs	Tail logs for an entity.
share	/cloudgrid:share	Make an entity shareable and print its URL.
feedback	/cloudgrid:feedback	Read the feedback feed for an entity.
brain	/cloudgrid:brain	Refresh an entity’s Grid Brain metadata.

The canonical chain — init → plug → logs → share → feedback — is the full “build a thing and ship it” loop.

Skills vs the MCP server

Both surfaces wrap the same grid CLI and share the same credentials. Skills are SKILL.md instructions your agent reads and acts on; the MCP server exposes the same actions as callable tools for clients that speak the Model Context Protocol. The Claude Code plugin installs both at once; other clients can add the MCP server separately as @cloudgrid-io/mcp.