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 very difficult for Claude to know when to select this skill over others.
Suggestions
Replace abstract terms with concrete actions, e.g., 'Coordinates planning across multiple Claude CLI instances, gathers relevant code context, and delegates implementation tasks' instead of 'collaborative planning with codebase context gathering'.
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user wants to plan a large feature across multiple CLI sessions, coordinate parallel development tasks, or break down complex changes across a codebase.'
Include specific file types, workflows, or scenarios that distinguish this skill, e.g., 'multi-agent coordination', 'parallel task execution', 'large refactoring planning'.
| 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 terms like 'collaborative planning' and 'codebase context gathering' are broad enough to overlap with many development-related 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 excels at actionability and workflow clarity with concrete, executable code for every phase and a well-structured 5-phase workflow with convergence checks and error handling. However, it is severely undermined by its monolithic structure and verbosity — the full agent prompts, JSON schemas, and implementation details should be split into referenced files, and the main skill should serve as a concise orchestration overview rather than embedding every detail inline.
Suggestions
Extract the synthesis.json schema, agent prompt templates, and executionContext assembly into separate referenced files (e.g., schemas/synthesis.json, prompts/discuss-agent.md, prompts/planning-agent.md) and reference them with one-level-deep links.
Reduce the main SKILL.md to a concise orchestration overview (~100 lines) covering the 5-phase flow, agent roles, key decision points, and references to detailed files for implementation specifics.
Remove redundant inline code that duplicates what agents already know (e.g., the full AskUserQuestion payload structure, complete TodoWrite examples for each phase) and replace with brief descriptions or single-line references.
Add a 'Quick Start' or 'Summary' section at the top that gives the essential flow in under 20 lines before diving into phase 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 (full JSON schemas, detailed agent prompts, executionContext assembly) is implementation detail that bloats the orchestrator-level skill. The synthesis.json schema, full AskUserQuestion payloads, and complete agent prompt templates all contribute to significant token waste. | 1 / 3 |
Actionability | The skill provides fully concrete, executable JavaScript code for every phase including session initialization, agent invocation with complete prompt templates, convergence decision logic, executionContext assembly, and execution handoff. Code examples are copy-paste ready with specific variable names, file paths, and JSON structures. | 3 / 3 |
Workflow Clarity | The 5-phase workflow is clearly sequenced with an ASCII flow diagram, explicit convergence checks between phases, feedback loops (Phase 4 → Phase 2 for more analysis), validation via convergence scoring, and a completion checklist for each agent invocation. Error handling table covers failure modes with specific resolutions. TodoWrite pattern tracks phase progression. | 3 / 3 |
Progressive Disclosure | The entire skill is a monolithic wall of content with no references to external files for detailed schemas, agent prompts, or configuration. The synthesis.json schema, full agent prompt templates, and executionContext assembly code should be in separate referenced files. No bundle files are provided despite the content clearly needing decomposition into supporting documents. | 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
227244f
- 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.