parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Install with Tessl CLI
npx tessl i github:shousper/claude-kit --skill parallel-agentsOverall
score
60%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 fails to explain what the skill actually does - it only describes when to use it. The technical jargon ('shared state', 'sequential dependencies') is not user-friendly, and there are no concrete actions or natural trigger terms that users would employ when seeking this functionality.
Suggestions
Add concrete actions describing what the skill does (e.g., 'Executes multiple independent tasks in parallel to improve efficiency' or 'Coordinates concurrent work streams').
Include natural trigger terms users would say, such as 'parallel', 'at the same time', 'multiple tasks', 'batch processing', or 'concurrent'.
Restructure to lead with capabilities before the 'Use when' clause, following the pattern: '[What it does]. Use when [trigger conditions].'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - it doesn't specify what the skill actually does, only when to use it. 'Independent tasks' and 'shared state' are abstract concepts without specific capabilities listed. | 1 / 3 |
Completeness | The description only addresses 'when' (facing 2+ independent tasks) but completely omits 'what' the skill does. There's no explanation of the actual capability or actions performed. | 1 / 3 |
Trigger Term Quality | No natural user keywords are present. Users wouldn't naturally say 'shared state' or 'sequential dependencies' - these are technical jargon. Missing terms like 'parallel', 'multiple tasks', 'batch', or 'concurrent'. | 1 / 3 |
Distinctiveness Conflict Risk | The '2+ independent tasks' criterion provides some specificity, but 'tasks' is generic enough to potentially overlap with many other skills. The technical framing around dependencies helps somewhat with distinctiveness. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill that clearly explains when and how to dispatch parallel agents. Its main strengths are the concrete prompt templates and real-world examples with specific file names. The content could be tightened by consolidating redundant sections (the real example appears twice in different forms) and potentially splitting detailed examples into a separate reference file.
Suggestions
Consolidate the 'Real Example from Session' and 'Real-World Impact' sections - they contain overlapping information about the same debugging session
Consider moving the detailed agent prompt example and the graphviz decision diagram to a separate EXAMPLES.md or REFERENCE.md file to improve progressive disclosure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy - the 'Real Example from Session' and 'Real-World Impact' sections largely repeat the same information, and some concepts are explained multiple times (when to use vs when NOT to use could be consolidated). | 2 / 3 |
Actionability | Provides concrete, executable guidance with specific TypeScript dispatch syntax, detailed agent prompt templates with exact structure, and real examples showing exact test file names and error messages. The agent prompt structure section is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 4-step workflow (Identify → Create → Dispatch → Review) with explicit verification steps at the end. The 'Review and Integrate' and 'Verification' sections provide clear checkpoints for validating agent outputs before integration. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but it's a monolithic document that could benefit from splitting detailed examples and the decision flowchart into separate reference files. The graphviz diagram is inline when it could be referenced. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.