# CloudGrid Skills

Multi-agent skills for CloudGrid. Install them in Claude Code, Codex, or Cursor,
and your agent can build, ship, and run things on CloudGrid through the
`grid` CLI.

## Why CloudGrid

Claude Code and Codex removed the wall around writing code. CloudGrid removes the
wall around running it. It is a live runtime environment: your app runs there WITH
the infrastructure it needs out of the box — managed MongoDB, Redis (cache, queues,
pub/sub), a pgvector store, persistent disk, and built-in AI with no API keys — in
any language or stack, with no Docker or Kubernetes to manage. A directory or a URL
becomes a live, addressable, running thing in about 30 seconds. These skills are how
your agent crosses that second wall on your behalf: scaffold, declare what the app
needs, build, plug it in, tail logs, share, read feedback. Everything here is free.

## Install in 3 steps

1. Install the CLI:

   ```
   npm install -g @cloudgrid-io/cli
   ```

2. Log in:

   ```
   grid login
   ```

3. Add the agent-core. In Claude Code (recommended):

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

   One install wires up everything: the skills, the SessionStart orientation
   hook, and the CloudGrid MCP server (`grid_start`, `grid_get_template`, and the
   CLI-wrapping tools). The MCP auto-starts when the plugin is enabled — no
   separate `claude mcp add` needed.

   The skills show under `/plugin` and `/skills` as `cloudgrid:plug`,
   `cloudgrid:login`, … — or just say what you want ("share this HTML page as a
   link") and the right one triggers.

   Or install with the `gh skill` extension:

   ```
   gh skill install cloudgrid-io/skills
   ```

   Other agents (Cursor, Cline, Gemini CLI): `npx skills add cloudgrid-io/skills`.
   They install as `plug`, `login`, … — the CloudGrid brand comes from the plugin
   namespace, which those agents don't have.

   Claude Desktop, claude.ai, ChatGPT, and every route in one place: [USAGE.md](USAGE.md).

## Share something in one step, no login

```
/cloudgrid:plug index.html
```

`cloudgrid:plug` publishes a single HTML page (or deploys a full app) and hands
back a public URL. For a single page: no account, no CLI — the link lasts 7 days,
and you can sign in later to keep it.

## Skills

| Skill | Invoke | 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/URL. 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. |
| `brain` | `/cloudgrid:brain` | Refresh an entity's Grid Brain metadata. |

## The canonical chain

```
init  ->  plug  ->  logs  ->  share  ->  feedback
```

That is the full "I built a thing and shipped it" loop. [COOKBOOK.md](COOKBOOK.md)
walks through it end to end.

## MCP server

The Claude Code plugin above already bundles the MCP server — installing
`cloudgrid@cloudgrid-skills` starts it automatically. For every other client, the
MCP server is published separately as
[`@cloudgrid-io/mcp`](https://github.com/cloudgrid-io/mcp). It exposes the same
actions as MCP tools, for agents that speak the Model Context Protocol.
Install it with `npx -y @cloudgrid-io/mcp`, or point a remote-capable client at
`https://mcp.cloudgrid.io/mcp`. See [USAGE.md](USAGE.md) for per-client setup.

## License

Apache 2.0. See [LICENSE](LICENSE).