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 1 commit into
Conversation
|
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 |
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
There was a problem hiding this comment.
🚩 Other @latest references in the same files lack the RC warning
The new <Warning> blocks are placed immediately after the primary code examples, but several other mentions of npx trigger.dev@latest skills in these same files were not annotated with a similar caveat. For example, the non-interactive install example at docs/skills.mdx:43 (npx trigger.dev@latest skills --target claude-code --target cursor -y), the "Keeping skills updated" section at docs/skills.mdx:73, and the comparison table at docs/building-with-ai.mdx:49 all still reference @latest without any RC note. Users who jump to those sections may miss the warning and try a command that doesn't work yet. This is a minor consistency gap rather than a bug — the primary install sections are correctly annotated.
(Refers to line 43)
Was this helpful? React with 👍 or 👎 to provide feedback.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
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 skills1 participant
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