Skip to content

fix: Skill 缺乏能力边界判断与替代方案引导:任务要求使用已禁用 CLI 时未切换至 MCP 工具#656

Open
binggg wants to merge 1 commit intomainfrom
automation/attribution-issue-mo8y1ju6-9v68qo-skill-cli-mcp
Open

fix: Skill 缺乏能力边界判断与替代方案引导:任务要求使用已禁用 CLI 时未切换至 MCP 工具#656
binggg wants to merge 1 commit intomainfrom
automation/attribution-issue-mo8y1ju6-9v68qo-skill-cli-mcp

Conversation

@binggg
Copy link
Copy Markdown
Member

@binggg binggg commented Apr 28, 2026

Attribution issue

  • issueId: issue_mo8y1ju6_9v68qo
  • category: skill
  • canonicalTitle: Skill 缺乏能力边界判断与替代方案引导:任务要求使用已禁用 CLI 时未切换至 MCP 工具
  • representativeRun: atomic-js-cloudbase-cli-permission-get/2026-04-21T18-08-06-bu4bbx

Automation summary

  • root_cause: The cloudbase-cli skill lacked capability boundary judgment and alternative solution guidance. When a task requires querying resource permissions via CLI (tcb permission get) but the CLI is disabled in the environment, the skill did not guide the agent to use MCP tools (queryPermissions) as an alternative. The runtime notice showed "tcbCliEnabled": false and "mcpEnabled": true, but the skill had no guidance for this scenario.
  • changes:
  1. Added a "⚠️ Capability Check: CLI vs MCP" section to config/source/skills/cloudbase-cli/SKILL.md that includes:
  • How to check if CLI is available (tcb --version)
  • Runtime capability check table showing what to do when CLI is disabled
  • Comprehensive mapping table between CLI commands and MCP tool equivalents (permission, role, user, function, env, storage, hosting operations)
  1. Added a "⚠️ CLI Availability Check" section to config/source/skills/cloudbase-cli/references/permission.md with:
  • Quick verification step for CLI availability
  • MCP tool equivalents specifically for permission-related operations
  • Guidance on how to discover available MCP tools
  • validation: All 10 mandatory regression tests pa

Changed files

  • config/source/skills/cloudbase-cli/SKILL.md
  • config/source/skills/cloudbase-cli/references/permission.md
  • package-lock.json
  • package.json

@chatgpt-codex-connector
Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@binggg
Copy link
Copy Markdown
Member Author

binggg commented Apr 28, 2026

Attribution post-PR evaluation

  • visibility: internal identifiers, run ids, and private links are intentionally omitted
  • attempt: 1
  • eval_scope: primary_only
  • overall: FAILED
  • summary: at least one planned evaluation case failed
  • updated_at: 2026-04-28T21:29:02.482Z

Cases

  • [FAILED] — primary — evaluation failed

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant