菜单
Add or update unit and end-to-end coverage for a clio MCP tool. Use when changing MCP tool arguments, tool names, command wiring, prompts, resources, destructive behavior, or when creating a new MCP tool that needs contract tests and E2E coverage.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Develop, validate, restructure, or maintain reliable clio MCP guidance from live Creatio evidence. Use when researching an unfamiliar Creatio behavior, building a repeatable clio lab, turning runtime/source discoveries into agent-facing guidance, adding or revising GuidanceCatalog resources, eliminating duplicated guidance, or defining acceptance tests and ownership boundaries for a clio guidance family.
Develop, validate, restructure, or maintain reliable clio MCP guidance from live Creatio evidence. Use when researching an unfamiliar Creatio behavior, building a repeatable clio lab, turning runtime/source discoveries into agent-facing guidance, adding or revising GuidanceCatalog resources, eliminating duplicated guidance, or defining acceptance tests and ownership boundaries for a clio guidance family.
Develop, validate, restructure, or maintain reliable clio MCP guidance from live Creatio evidence. Use when researching an unfamiliar Creatio behavior, building a repeatable clio lab, turning runtime/source discoveries into agent-facing guidance, adding or revising GuidanceCatalog resources, eliminating duplicated guidance, or defining acceptance tests and ownership boundaries for a clio guidance family.
Turn this session into the Architect — a conversational orchestrator for the Clio codebase. The Architect investigates and reasons about the code WITH you (refactoring ideas, design questions, impact analysis), never edits code itself, and delegates implementation to `coder` subagents one unit at a time, reporting each result back. Use when you want to think through a change, plan a refactor, or have work implemented under supervision rather than editing directly.
Update a working branch from `master`, create or refresh a pull request, monitor build and quality gates, answer and resolve AI or human review comments, and merge the PR only after all actionable threads and checks are cleared. Use for clio delivery tasks that must go end-to-end through GitHub without missing follow-up steps.
Create, update, and validate custom Creatio Configuration Web Services and their tests. Use when users need to expose custom backend endpoints in Creatio, wire service contracts/implementations, return structured success/error results, or verify endpoints with integration-style and unit tests.
| name | test-mcp-tool |
| description | Add or update unit and end-to-end coverage for a clio MCP tool. Use when changing MCP tool arguments, tool names, command wiring, prompts, resources, destructive behavior, or when creating a new MCP tool that needs contract tests and E2E coverage. |
Test MCP tools at two levels: in-process contract tests and external-process end-to-end tests.
Cover all meaningful argument combinations.
[Required].Use clio.tests to verify:
At minimum, assert that each MCP method:
Use clio.mcp.e2e for every new or updated MCP tool.
clio mcp-server process over stdio.Always use explicit AAA structure and separate important assertions into distinct Allure steps.
Required output assertions:
Info message type in the returned execution log.Error message type when execution output is available.Also assert:
IsError state matches the scenarioTests must reference tool names from constants defined on the production tool class.
Example:
private const string ToolUnderTestTag = ClearRedisTool.ClearRedisByEnvironmentName;
Do not hardcode MCP tool names in test files.
clio.testsclio.mcp.e2eInfo and Error message-type assertions added where relevant