fix: 任务要求使用 CLI 但 CLI 被禁用，且缺少替代方案引导

[binggg]

Attribution issue

• issueId: issue_mo8xf0sr_dpi15o
• category: skill
• canonicalTitle: 任务要求使用 CLI 但 CLI 被禁用，且缺少替代方案引导
• representativeRun: atomic-js-cloudbase-cli-cors-lifecycle/2026-04-21T17-56-37-5ckv9y

Automation summary

• root_cause: The cloudbase-cli skill only provided CLI command guidance but lacked alternative solution guidance when CLI is disabled. When the runtime has tcbCliEnabled: false, the agent received an error and didn't know to fall back to MCP tools.
• changes: Added "When CLI is not available" sections to both:

1. config/source/skills/cloudbase-cli/SKILL.md - main skill file with MCP alternatives table and examples for CORS, custom domains, and static hosting
2. config/source/skills/cloudbase-cli/references/access.md - access reference with detailed MCP tool examples for CORS (envDomainManagement), custom domains (domainManagement), and routing (no MCP support)

• validation: All skill tests pass (build-skills-repo.test.js, build-compat-config.test.js, skill-quality-standards.test.js)
• follow_up: None - the fix addresses the issue by providing clear guidance for agents to use MCP tools when CLI is disabled

Changed files

• config/source/skills/cloudbase-cli/SKILL.md
• config/source/skills/cloudbase-cli/references/access.md

[chatgpt-codex-connector]

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

[binggg]

Attribution post-PR evaluation

• visibility: internal identifiers, run ids, and private links are intentionally omitted
• attempt: 1
• eval_scope: primary_only
• overall: ERROR
• summary: post-PR evaluation errored
• updated_at: 2026-04-28T22:15:03.981Z

Cases

• [ERROR] — primary — evaluation errored