docs(cli): tell MCP-only sessions to skip the CLI skill opener [ship] - #1434
Merged
Conversation
stefanjudis
changed the title
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Affected Components
Notes for the Reviewer
The checkly skill is written entirely for CLI usage, but agents can also reach Checkly through the Checkly MCP server. An MCP-only session (e.g. a desktop or sandboxed agent without shell access) that loads this skill would try to run
npx checkly skillsand fail.This adds an MCP sessions gate as the first paragraph of the skill body, before the "Required" directive, telling such agents to stop and use the Checkly MCP tools for live account work instead.
The condition is deliberately "MCP and no shell", not just "MCP connected": a coding-agent session can have both the repo and the MCP server attached, and skills + CLI remain the recommended path there — the closing sentence guards that case so agents don't abandon the skill unnecessarily.
Edited the source at
packages/cli/src/ai-context/skill.mdand regeneratedskills/checkly/SKILL.mdviaprepare+sync:skills, so the CI sync check should pass.