docs(skills): note the skills CLI command is only in the release candidate

docs/building-with-ai.mdx

@@ -28,6 +28,11 @@ We provide multiple tools to help AI coding assistants write correct Trigger.dev
   npx trigger.dev@latest skills
   ```
 
+  <Warning>
+    The `skills` command is currently only available in the release candidate. Until it ships to
+    the stable release, run it with the `@rc` tag: `npx trigger.dev@rc skills`.
+  </Warning>
+
   [Learn more →](/skills)
 </Step>
 
@@ -41,7 +46,7 @@ Skills and the MCP server do different jobs and work best together. Here's how t
 |:--|:-----------|:---------------|
 | **What it does** | Drops skill files into your project that teach Trigger.dev patterns | Runs a live server your AI connects to |
 | **Installs to** | `.claude/skills/`, `.cursor/skills/`, `.github/skills/`, `.agents/skills/` | `mcp.json`, `~/.claude.json`, etc. |
-| **Updates** | Re-run `npx trigger.dev@latest skills`, or auto-prompted on `trigger dev` | Always latest (uses `@latest`) |
+| **Updates** | Re-run `npx trigger.dev@latest skills` (`@rc` until it ships to stable), or auto-prompted on `trigger dev` | Always latest (uses `@latest`) |
 | **Best for** | Teaching patterns and best practices | Live project interaction (deploy, trigger, monitor) |
 | **Works offline** | Yes | No (calls Trigger.dev API) |
 

docs/mcp-agent-rules.mdx

@@ -19,7 +19,12 @@ The install command is the same, and now installs skills:
 npx trigger.dev@latest skills
 ```
 
-`npx trigger.dev@latest install-rules` still works as an alias, and `trigger dev` offers to install the skills on first run.
+<Warning>
+  The `skills` command is currently only available in the release candidate. Until it ships to the
+  stable release, run it with the `@rc` tag: `npx trigger.dev@rc skills`.
+</Warning>
+
+`npx trigger.dev@latest install-rules` still works as an alias for `skills` (so the same `@rc` caveat applies for now), and `trigger dev` offers to install the skills on first run.
 
 The old task and realtime guidance now lives in the `trigger-authoring-tasks` and `trigger-realtime-and-frontend` skills, alongside two new skills for building `chat.agent` AI agents. See [Skills](/skills) for the full list and supported assistants.
 

docs/skills.mdx

@@ -24,6 +24,11 @@ Run the installer with the CLI:
 npx trigger.dev@latest skills
 ```
 
+<Warning>
+  The `skills` command is currently only available in the release candidate. Until it ships to the
+  stable release, run it with the `@rc` tag: `npx trigger.dev@rc skills`.
+</Warning>
+
 The CLI detects your installed AI tools, lets you pick which skills to install, and writes each one into that tool's native skills directory (`.claude/skills/`, `.cursor/skills/`, `.github/skills/`, `.agents/skills/`). It also adds a one-line pointer to your primary instructions file (`CLAUDE.md`, `.cursor/rules`, etc.) so your assistant always knows the skills are there and loads the right one on demand.
 
 When you run `trigger dev` for the first time, the CLI offers to install the skills for you.
@@ -38,6 +43,8 @@ Pass `--target` to choose tools and `-y` to install every skill without promptin
 npx trigger.dev@latest skills --target claude-code --target cursor -y
 ```
 
+While the command is still release-candidate only, swap `@latest` for `@rc`.
+
 ## Available skills
 
 | Skill                  | Use for                                                        | Covers                                                                       |
@@ -65,7 +72,7 @@ Using a tool that does not support skills yet? Select "Unsupported target" in th
 
 ## Keeping skills updated
 
-The API guidance updates on its own: it lives in `@trigger.dev/sdk` and is read from `node_modules`, so upgrading the SDK in your project upgrades the guidance with it. Re-run `npx trigger.dev@latest skills` (or accept the prompt that `trigger dev` shows when a newer version is available) only to add skills or refresh the installed pointer files. Re-running overwrites them in place without creating duplicates.
+The API guidance updates on its own: it lives in `@trigger.dev/sdk` and is read from `node_modules`, so upgrading the SDK in your project upgrades the guidance with it. Re-run `npx trigger.dev@latest skills` (use `@rc` until the command ships to the stable release, or accept the prompt that `trigger dev` shows when a newer version is available) only to add skills or refresh the installed pointer files. Re-running overwrites them in place without creating duplicates.
 
 ## Next steps