Skip to content

docs(skills): reflect the SDK-bundled, version-pinned agent reference#3939

Draft
ericallam wants to merge 1 commit into
mainfrom
docs/skills-pinned-to-sdk
Draft

docs(skills): reflect the SDK-bundled, version-pinned agent reference#3939
ericallam wants to merge 1 commit into
mainfrom
docs/skills-pinned-to-sdk

Conversation

@ericallam

Copy link
Copy Markdown
Member

Summary

The agent skills' deep guidance now ships inside @trigger.dev/sdk and is read from node_modules, so it tracks the @trigger.dev/sdk version installed in your project automatically. This updates the Skills page, the Building with AI step, and the rules-redirect page to drop the old "pinned to the CLI version, re-run to refresh" framing and describe the version-pinned reference instead.

Pairs with the SDK/CLI change in #3937. Keep this draft until that ships, since it describes behavior that is not released yet.

The deep agent guidance now ships inside @trigger.dev/sdk and is read from
node_modules, so it tracks the installed SDK version. Update the Skills page, the
Building with AI step, and the rules-redirect page to drop the old "pinned to the
CLI version, re-run to refresh" framing.
@changeset-bot

changeset-bot Bot commented Jun 13, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: f331e04

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@mintlify

mintlify Bot commented Jun 13, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
trigger 🟢 Ready View Preview Jun 13, 2026, 7:59 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@coderabbitai

coderabbitai Bot commented Jun 13, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Walkthrough

This PR updates documentation to clarify Skills' installation and versioning model in Trigger.dev. Skills are now described as installed via the CLI into native skills directories with API guidance sourced from a version-pinned reference in @trigger.dev/sdk (read from node_modules), rather than being pinned to the CLI version. The main docs/skills.mdx file was updated to explain this behavior in the Installation and "Keeping skills updated" sections, with cross-reference updates in docs/building-with-ai.mdx and docs/mcp-agent-rules.mdx to maintain consistency.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The PR description provides context for the changes but does not follow the required template structure with the standard sections (Checklist, Testing, Changelog, Screenshots). Provide a description that follows the required template, including the checklist, testing steps, and changelog sections. The current summary should be moved to the Changelog section.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title directly reflects the main change: updating documentation to describe that agent reference is now bundled with and version-pinned to the SDK.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/skills-pinned-to-sdk

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint install timed out. The project may have too many dependencies for the sandbox.


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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
docs/skills.mdx (1)

27-27: 💤 Low value

Consider splitting this long sentence for readability.

The sentence runs 52 words and packs four distinct actions (detect, pick, write, add pointer) plus multiple directory/file examples. While accurate, breaking it into 2-3 shorter sentences would improve clarity.


ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: ccd82717-bed8-4896-9100-c81dc63013db

📥 Commits

Reviewing files that changed from the base of the PR and between 034058b and f331e04.

📒 Files selected for processing (3)
  • docs/building-with-ai.mdx
  • docs/mcp-agent-rules.mdx
  • docs/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/sdk in 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/skills.mdx
  • docs/building-with-ai.mdx
  • docs/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/skills.mdx
  • docs/building-with-ai.mdx
  • docs/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/skills.mdx
  • docs/building-with-ai.mdx
  • docs/mcp-agent-rules.mdx
🪛 LanguageTool
docs/skills.mdx

[uncategorized] ~27-~27: The official name of this software platform is spelled with a capital “H”.
Context: ... (.claude/skills/, .cursor/skills/, .github/skills/, .agents/skills/). It also a...

(GITHUB)

🔇 Additional comments (5)
docs/skills.mdx (3)

21-21: LGTM!


31-31: LGTM!


67-67: LGTM!

docs/building-with-ai.mdx (1)

25-25: LGTM!

docs/mcp-agent-rules.mdx (1)

14-14: LGTM!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant