workiq skill: use prefixed MCP tool name#41
Open
johnmog wants to merge 1 commit into
Open
Conversation
The Copilot CLI exposes MCP tools as <server>-<tool>. The WorkIQ MCP server is registered as 'workiq', so the tool is exposed as 'workiq-ask_work_iq', not the bare 'ask_work_iq' the skill currently documents. Calling the bare name fails with 'Tool ask_work_iq does not exist.' Observed 4 such failures across 3 distinct CLI sessions in the past week. Update all examples and tables to use 'workiq-ask_work_iq' and add a short note explaining the prefix convention. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Updates the WorkIQ skill documentation to reflect the Copilot CLI MCP tool naming convention (<server>-<tool>), preventing agents from calling a non-existent bare tool name.
Changes:
- Replaced all example references from
ask_work_iqtoworkiq-ask_work_iq. - Added a short explanatory note describing the
<server>-<tool>prefix convention and the expected error when omitted.
Show a summary per file
| File | Description |
|---|---|
plugins/workiq/skills/workiq/SKILL.md |
Updates all documented tool invocations to use the correct prefixed MCP tool name and adds a clarification note to avoid future regressions. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 1/1 changed files
- Comments generated: 0
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
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.
Copilot CLI said this change was worth doing due to trajectory issues using these skills. I'm not sure so I opened the PR to let maintainers judge. Failure rate is pretty low, but it seems like there is probably a better change then renaming everything like this.
Problem
The WorkIQ skill (
plugins/workiq/skills/workiq/SKILL.md) documents the MCP tool as bareask_work_iq. The Copilot CLI exposes MCP tools as<server>-<tool>, and the WorkIQ MCP server is registered asworkiq(perplugins/workiq/.mcp.json), so the actual tool name isworkiq-ask_work_iq.When an LLM trusts the skill examples and calls bare
ask_work_iq, the call fails immediately with:Evidence
From the past week of Copilot CLI session telemetry:
workiq-ask_work_iqworkiq-ask_work_iqask_work_iqThe 4 bare-name failures all came from sessions where the agent followed the skill's examples literally.
Fix
ask_work_iqtoworkiq-ask_work_iq.<server>-<tool>prefix convention and the exact error message you get if you forget it, so future skill maintainers don't accidentally re-introduce the bare name.No behavior change for the MCP server itself — purely a docs/skill fix.