docs(skills): add the RC caveat to the remaining skills command references

Cover the non-interactive install example, the keeping-updated section, and
the comparison table so users who deep-link past the install section still
see the @rc note.

Author: D-K-P

docs/building-with-ai.mdx

@@ -46,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/skills.mdx

@@ -43,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                                                                       |
@@ -70,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