workflow-multi-cli-plan
Multi-CLI collaborative planning with codebase context gathering, iterative cross-verification, and execution handoff.
44
31%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/workflow-multi-cli-plan/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is heavily laden with abstract jargon and buzzwords without conveying concrete actions or use cases. It lacks a 'Use when...' clause, natural trigger terms, and specific capability descriptions, making it nearly impossible for Claude to correctly select this skill from a pool of alternatives.
Suggestions
Replace abstract terms with concrete actions, e.g., 'Coordinates multiple CLI instances to plan and execute complex codebase changes, splitting tasks across agents for parallel work.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user wants to coordinate multiple Claude instances, split a large task across agents, or plan multi-step codebase changes collaboratively.'
Include natural keywords users might say, such as 'parallel agents', 'split task', 'coordinate work', 'multi-agent', 'plan and execute changes'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses abstract, buzzword-heavy language like 'collaborative planning', 'codebase context gathering', 'iterative cross-verification', and 'execution handoff' without describing concrete actions a user would understand. No specific tasks are listed. | 1 / 3 |
Completeness | The 'what' is vague and abstract, and there is no 'when' clause or explicit trigger guidance at all. It fails to answer either question clearly. | 1 / 3 |
Trigger Term Quality | The terms used ('Multi-CLI', 'cross-verification', 'execution handoff') are technical jargon that users would almost never naturally say. There are no natural keywords a user would use when requesting this skill. | 1 / 3 |
Distinctiveness Conflict Risk | The 'Multi-CLI' aspect provides some distinctiveness, but the rest of the description ('collaborative planning', 'codebase context gathering') is generic enough to overlap with many development workflow skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
55%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is highly actionable with excellent workflow clarity, providing concrete code for every phase and clear sequencing with convergence logic and error handling. However, it suffers severely from being a monolithic document—the full agent prompts, JSON schemas, executionContext assembly, and TodoWrite patterns should be split into referenced files. The verbosity significantly undermines its utility as a SKILL.md overview, making it harder to parse and consuming excessive tokens.
Suggestions
Extract the synthesis.json schema, agent prompt templates, and executionContext assembly code into separate referenced files (e.g., SCHEMAS.md, AGENT-PROMPTS.md) and replace with brief summaries and links.
Move the full AskUserQuestion structure and TodoWrite patterns to a separate TEMPLATES.md file, keeping only a brief description of what decisions are collected in Phase 4.
Condense the Phase 5 section significantly—the four detailed steps with full code blocks could be a concise overview with references to implementation details in a separate file.
Add a concise Quick Start or TL;DR section at the top summarizing the 5-phase flow in 5-10 lines before diving into details.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines with extensive inline code blocks that could be referenced externally. Much of the content (JSON schemas, full agent prompts, detailed executionContext assembly) could be split into separate files. The synthesis.json schema, full AskUserQuestion structure, and complete agent prompt templates are all inlined, bloating the document significantly. | 1 / 3 |
Actionability | The skill provides highly concrete, executable guidance with specific JavaScript code for every phase, exact file paths, complete JSON schemas, detailed agent invocation patterns, and copy-paste ready code blocks. Every step has explicit code showing exactly what to do. | 3 / 3 |
Workflow Clarity | The multi-step workflow is clearly sequenced with an ASCII flow diagram, explicit phase transitions, convergence decision logic with branching paths, validation checklists for agent outputs, error recovery paths, and clear routing logic in Phase 4. Feedback loops are well-defined (Phase 2 iteration, convergence checks). | 3 / 3 |
Progressive Disclosure | This is a monolithic wall of content with everything inlined. The full synthesis.json schema, complete agent prompts with checklists, full executionContext assembly, and TodoWrite patterns are all embedded in the main file. The agent prompt templates, JSON schemas, and context-package structure should be in separate referenced files. References to external schemas exist (plan-overview-base-schema.json, task-schema.json) but the skill itself doesn't split its own content appropriately. | 1 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- Repository
- catlog22/Claude-Code-Workflow
- Commit
0f8e801
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.