Claim an open Advance-Technologies-Foundation/clio GitHub issue before investigation or implementation by assigning the current gh user and creating its predictable linked development branch. Use only when the user authorized taking or triaging an issue; do not use for brainstorming or read-only review.
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…
Coordinate a GitHub issue submitted to Advance-Technologies-Foundation/clio from visible claim through repository diagnosis and repair. Use when the user asks to take, triage, fix, implement, or resolve a Clio issue across clio, clio-knowledge, or a referenced example repository. Do not mutate GitHub or files during…
Investigate a claimed Clio GitHub issue and determine whether the defect belongs to clio, clio-knowledge, or a repository referenced by clio-knowledge. Use after the claim-clio-issue skill and before implementation, including when downstream issues and GitHub blocking relationships must communicate ownership.
Implement and validate the evidence-backed repair for a diagnosed Clio issue in clio, clio-knowledge, or affected example repositories. Use only after ownership is established and the user authorized implementation; maintain issue stage, downstream relationships, draft PR visibility, optional cross-agent consultation…
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…
Create or update a clio MCP tool when command behavior, MCP exposure, prompts, or resources must be added or kept in sync. Use for work in clio/Command/McpServer/Tools, Prompts, or Resources, especially when adding a new MCP tool, updating arguments, or aligning the MCP contract with an existing command.
Create or update documentation for a single clio CLI command, including clio/help/en/command-name.txt, clio/docs/commands/command-name.md, and the command index in clio/Commands.md. Use when user asks to document a command by name or alias, update command help, or align docs with current command options from source…
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…
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.
Provision or safely reuse an exclusive local Creatio environment, install ClioGate and the real AutoTest fixtures, then run the complete clio MCP E2E suite. Use when preparing a local Creatio stand for clio.mcp.e2e or when proving the full E2E suite locally; do not use for shared stands or teardown.
Prepare a live Creatio stand so the clio.mcp.e2e suite can actually run against it, and run the environment-dependent tests. Use when a task hands you a stand URL and asks to run MCP e2e tests, when a Sandbox-category test is skipped for want of a reachable environment, or when an acceptance criterion is stuck at…
★not rated 56 todayA145 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: