ultrawork
Parallel execution engine for high-throughput task completion
56
46%
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 ./skills/ultrawork/SKILL.mdQuality
Discovery
0%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 too abstract and technical to be useful for skill selection. It reads like marketing copy rather than functional guidance, using buzzwords ('high-throughput', 'execution engine') without explaining what the skill actually does or when to use it. Claude would have no clear basis for selecting this skill over others.
Suggestions
Replace abstract language with concrete actions - specify what types of tasks are executed in parallel (e.g., 'Runs multiple file conversions, API calls, or data processing jobs simultaneously')
Add a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user wants to process multiple items at once, batch operations, or mentions running tasks in parallel')
Define the specific domain or use cases to distinguish from other skills (e.g., is this for data processing, file operations, API calls, or something else?)
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language ('parallel execution engine', 'high-throughput task completion') without naming any concrete actions. It doesn't specify what tasks are executed or what domain it operates in. | 1 / 3 |
Completeness | Missing both clear 'what' (no specific capabilities listed) and 'when' (no 'Use when...' clause or trigger guidance). The description is too abstract to answer either question meaningfully. | 1 / 3 |
Trigger Term Quality | Contains technical jargon ('parallel execution engine', 'high-throughput') that users would not naturally say. No natural keywords like 'run multiple tasks', 'batch processing', or specific task types are included. | 1 / 3 |
Distinctiveness Conflict Risk | Extremely generic - 'task completion' could apply to virtually any skill. Without specifying what types of tasks or in what context, this would conflict with many other skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that clearly defines ultrawork's role as a composable parallelism component. The concrete examples with good/bad patterns and explicit tier routing guidance make it highly actionable. The clear delineation of when to use vs not use this skill (recommending ralph or autopilot instead) demonstrates good system design awareness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of concepts Claude already knows. Each section serves a clear purpose with no padding or unnecessary context about what parallel execution is. | 3 / 3 |
Actionability | Provides concrete, executable Task() calls with specific parameters including model selection, subagent_type, and run_in_background flags. Examples are copy-paste ready with clear explanations of why each is good or bad. | 3 / 3 |
Workflow Clarity | Clear 7-step sequence with explicit guidance on task classification, tier routing, and verification. Includes a final checklist and clear escalation conditions. The workflow distinguishes parallel vs sequential execution appropriately. | 3 / 3 |
Progressive Disclosure | References external file (docs/shared/agent-tiers.md) appropriately, but the content is somewhat monolithic. The Advanced section with the relationship diagram is good, but the main content could benefit from clearer section signposting for quick scanning. | 2 / 3 |
Total | 11 / 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 | |
- Repository
- Yeachan-Heo/oh-my-claudecode
- Commit
48ffaac
- 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.