docs(skills): note the skills CLI command is only in the release candidate#4047
docs(skills): note the skills CLI command is only in the release candidate#4047D-K-P wants to merge 2 commits into
Conversation
|
|
Caution Review failedAn error occurred during the review process. Please try again later. WalkthroughThe documentation now describes agent rules as skills installed with the 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 3
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 40435acc-ec51-41ce-bbe1-c7609f69c5b6
📒 Files selected for processing (3)
docs/building-with-ai.mdxdocs/mcp-agent-rules.mdxdocs/skills.mdx
📜 Review details
🧰 Additional context used
📓 Path-based instructions (1)
docs/**/*.mdx
📄 CodeRabbit inference engine (docs/CLAUDE.md)
docs/**/*.mdx: MDX documentation pages must include frontmatter with title (required), description (required), and sidebarTitle (optional) in YAML format
Use Mintlify components for structured content: , , , , , , /, /
Always import from@trigger.dev/sdkin code examples (never from@trigger.dev/sdk/v3)
Code examples must be complete and runnable where possible
Use language tags in code fences:typescript,bash,json
Files:
docs/building-with-ai.mdxdocs/skills.mdxdocs/mcp-agent-rules.mdx
🧠 Learnings (2)
📚 Learning: 2026-03-10T12:44:14.176Z
Learnt from: nicktrn
Repo: triggerdotdev/trigger.dev PR: 3200
File: docs/config/config-file.mdx:353-368
Timestamp: 2026-03-10T12:44:14.176Z
Learning: In the trigger.dev repo, docs PRs are often companions to implementation PRs. When reviewing docs PRs (MDX files under docs/), check the PR description for any companion/related PR references and verify that the documented features exist in those companion PRs before flagging missing implementations. This ensures docs stay in sync with code changes across related PRs.
Applied to files:
docs/building-with-ai.mdxdocs/skills.mdxdocs/mcp-agent-rules.mdx
📚 Learning: 2026-04-30T20:30:29.458Z
Learnt from: ericallam
Repo: triggerdotdev/trigger.dev PR: 3226
File: docs/ai-chat/quick-start.mdx:13-13
Timestamp: 2026-04-30T20:30:29.458Z
Learning: In this repo’s documentation MDX files (`docs/**/*.mdx`), use `ts` and `tsx` (not `typescript`) as the code-fence language tags for TypeScript/TSX snippets. Do not flag `ts`/`tsx` code-fence language tags as incorrect in any docs MDX file, since this is the site-wide Mintlify-compatible convention.
Applied to files:
docs/building-with-ai.mdxdocs/skills.mdxdocs/mcp-agent-rules.mdx
| <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> |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Make the example match the warning.
The warning says skills is RC-only, but the install snippet above still uses npx trigger.dev@latest skills. Anyone copying it will land on the wrong release channel until stable. Switch the example to @rc for now.
🔧 Suggested fix
- npx trigger.dev@latest skills
+ npx trigger.dev@rc 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> |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Make the example match the warning.
The warning says skills is RC-only, but the snippet above still shows npx trigger.dev@latest skills. Readers copying this will hit the wrong release channel until stable. Switch the example to @rc for now.
🔧 Suggested fix
- npx trigger.dev@latest skills
+ npx trigger.dev@rc 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> |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Make the example match the warning.
The warning says skills is RC-only, but the example above still uses npx trigger.dev@latest skills. Readers copying the snippet will hit the wrong channel until stable. Switch the example to @rc for now.
🔧 Suggested fix
- npx trigger.dev@latest skills
+ npx trigger.dev@rc skills…ences 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.
| 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, and `trigger dev` offers to install the skills on first run. |
There was a problem hiding this comment.
🚩 Pre-existing install-rules alias reference may confuse users given the new RC warning
In docs/mcp-agent-rules.mdx:27, the pre-existing (unchanged) line states "npx trigger.dev@latest install-rules still works as an alias". The new warning at lines 22-25 says the skills command is RC-only. Since install-rules is registered as an alias for skills (packages/cli-v3/src/commands/skills.ts:59), running npx trigger.dev@latest install-rules would also fail if @latest doesn't include the skills command yet. This is a pre-existing line that the PR didn't modify, but the newly added warning above it creates a potential contradiction that could confuse readers. Consider adding a parenthetical note to line 27 or adjusting it to mention @rc as well.
Was this helpful? React with 👍 or 👎 to provide feedback.
Summary
The
skillsinstaller command (npx trigger.dev@latest skills) ships in the release candidate but is not yet on the stable release, so running it with@latestfails today. Adds a warning on each docs page that shows the command, telling users to run it with the@rctag until it lands in@latest.The commands themselves stay on
@latest, so nothing needs reverting once the next stable release ships, just the warnings.Pages updated:
/skills/mcp-agent-rules/building-with-ai