parallel-task-format
Compact YAML format for defining parallel task specifications with scope, boundaries, and agent assignments. Use when creating task files for parallel development.
Install with Tessl CLI
npx tessl i github:jpoutrin/product-forge --skill parallel-task-format72
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
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description adequately covers both what the skill does and when to use it, earning full marks for completeness. However, it lacks concrete action verbs and could benefit from more natural trigger terms that users would actually say. The domain is reasonably specific but could conflict with other YAML or task-related skills.
Suggestions
Add concrete action verbs like 'create', 'define', 'structure', or 'generate' to improve specificity (e.g., 'Define and structure parallel task specifications...')
Expand trigger terms to include natural variations like 'multi-agent tasks', 'concurrent work', 'task breakdown', or 'parallel workflow'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (YAML format for parallel task specifications) and mentions some elements (scope, boundaries, agent assignments), but doesn't list multiple concrete actions like 'create', 'validate', 'parse', or 'generate'. | 2 / 3 |
Completeness | Clearly answers both what (compact YAML format for defining parallel task specifications with scope, boundaries, and agent assignments) and when (Use when creating task files for parallel development) with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'task files', 'parallel development', 'YAML', and 'agent assignments', but misses common variations users might say like 'multi-agent', 'concurrent tasks', 'task definition', or 'workflow specification'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to parallel task specifications and agent assignments, but could overlap with general YAML skills, task management skills, or workflow definition skills without more distinctive triggers. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides highly actionable, concrete guidance for creating parallel task specifications with excellent examples and clear syntax rules. However, it's somewhat verbose with redundant explanations and could benefit from a clearer workflow for task creation with explicit validation checkpoints. The content organization is good but the document length suggests some content could be split into reference files.
Suggestions
Add a brief step-by-step workflow at the top: 1) Copy template, 2) Fill frontmatter, 3) Define scope, 4) Validate with checklist, 5) Run validation tool
Move the Agent Type Selection and YAML Frontmatter Fields tables to a separate REFERENCE.md file to reduce main document length
Remove the 'Why Compact Format?' section - Claude doesn't need justification for format choices
Add explicit error recovery guidance: what to do when validation fails, how to resolve circular dependencies
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good use of tables and examples, but includes some redundant explanations (e.g., explaining deps vs blocks twice, the 'Why Compact Format?' section states obvious benefits). Some sections could be tightened. | 2 / 3 |
Actionability | Provides fully concrete, copy-paste ready YAML examples with complete field definitions, clear syntax rules for scoped modifications, and specific file path patterns. The complete task example at the top is immediately usable. | 3 / 3 |
Workflow Clarity | The validation rules checklist at the end provides verification steps, but there's no explicit workflow sequence for creating tasks. Missing feedback loops for what to do when validation fails or how to iterate on task definitions. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but it's a monolithic document (~150 lines) that could benefit from splitting reference tables (agent types, field definitions) into separate files. No external file references for advanced topics. | 2 / 3 |
Total | 9 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.