From 5f2d16dc60e580cffd62ad56acddeeaa979ab525 Mon Sep 17 00:00:00 2001
From: D-K-P <8297864+D-K-P@users.noreply.github.com>
Date: Thu, 25 Jun 2026 17:52:29 +0100
Subject: [PATCH 1/2] docs(skills): note the skills CLI command is only in the
release candidate
The skills installer ships in the release candidate but is not yet on the
stable release. Add a warning on each page that shows the command, telling
users to run it with the @rc tag until it lands in @latest.
---
docs/building-with-ai.mdx | 5 +++++
docs/mcp-agent-rules.mdx | 5 +++++
docs/skills.mdx | 5 +++++
3 files changed, 15 insertions(+)
diff --git a/docs/building-with-ai.mdx b/docs/building-with-ai.mdx
index 7290a39b3e..1e0fde5eb1 100644
--- a/docs/building-with-ai.mdx
+++ b/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
```
+
+ 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`.
+
+
[Learn more →](/skills)
diff --git a/docs/mcp-agent-rules.mdx b/docs/mcp-agent-rules.mdx
index 20daadb518..341e9b859b 100644
--- a/docs/mcp-agent-rules.mdx
+++ b/docs/mcp-agent-rules.mdx
@@ -19,6 +19,11 @@ The install command is the same, and now installs skills:
npx trigger.dev@latest skills
```
+
+ 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`.
+
+
`npx trigger.dev@latest install-rules` still works as an alias, 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.
diff --git a/docs/skills.mdx b/docs/skills.mdx
index 43cfbe758a..3386d3ddae 100644
--- a/docs/skills.mdx
+++ b/docs/skills.mdx
@@ -24,6 +24,11 @@ Run the installer with the CLI:
npx trigger.dev@latest skills
```
+
+ 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`.
+
+
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.
From 28ffdd54b7407a1260ea6091f9ac19975247cd66 Mon Sep 17 00:00:00 2001
From: D-K-P <8297864+D-K-P@users.noreply.github.com>
Date: Fri, 26 Jun 2026 10:19:38 +0100
Subject: [PATCH 2/2] 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.
---
docs/building-with-ai.mdx | 2 +-
docs/skills.mdx | 4 +++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/docs/building-with-ai.mdx b/docs/building-with-ai.mdx
index 1e0fde5eb1..21cf5d4251 100644
--- a/docs/building-with-ai.mdx
+++ b/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) |
diff --git a/docs/skills.mdx b/docs/skills.mdx
index 3386d3ddae..6b58ce0721 100644
--- a/docs/skills.mdx
+++ b/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