ultrawork
Parallel execution engine for high-throughput task completion
40
38%
Does it follow best practices?
Impact
—
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 extremely vague and reads more like a marketing tagline than a functional skill description. It fails on all dimensions: no concrete actions, no natural trigger terms, no 'when to use' guidance, and no distinguishing characteristics. It would be nearly impossible for Claude to correctly select this skill from a pool of available options.
Suggestions
Replace abstract language with concrete actions: specify exactly what tasks this skill performs in parallel (e.g., 'Runs multiple file processing tasks simultaneously, batches API calls, and parallelizes data transformations').
Add an explicit 'Use when...' clause with natural trigger terms users would actually say (e.g., 'Use when the user needs to process many files at once, run batch operations, or speed up repetitive tasks').
Define the specific domain or niche this skill operates in to distinguish it from other task-execution skills (e.g., specify whether it handles file I/O, web scraping, data processing, or testing).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language like 'parallel execution engine' and 'high-throughput task completion' without naming any concrete actions. It doesn't specify what tasks are being completed or what domain it operates in. | 1 / 3 |
Completeness | Both 'what' and 'when' are extremely weak. There is no explanation of what specific tasks it performs, no 'Use when...' clause, and no explicit trigger guidance whatsoever. | 1 / 3 |
Trigger Term Quality | The terms 'parallel execution engine' and 'high-throughput task completion' are technical jargon that users would almost never naturally say. There are no natural keywords a user would use when needing this skill. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so generic ('task completion') that it could conflict with virtually any other skill. There is nothing to distinguish it from other skills that also complete tasks. | 1 / 3 |
Total | 4 / 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 well-structured skill with strong actionability and clear workflow sequencing. The concrete Task() examples with tier routing and good/bad comparisons make it immediately usable. The main weaknesses are moderate verbosity (explanatory sections like 'Why_This_Exists', parenthetical notes in 'Do_Not_Use_When') and a somewhat monolithic structure that could benefit from splitting detailed examples and tier guidance into separate referenced files.
Suggestions
Remove or significantly trim the 'Why_This_Exists' section — Claude doesn't need motivation for using a skill, just instructions on when and how.
Remove parenthetical explanations in 'Do_Not_Use_When' (e.g., '-- use ralph instead (ralph includes ultrawork)') since the Advanced section already covers the relationship hierarchy.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary sections like 'Why_This_Exists' which explains concepts Claude can infer, and the 'Purpose' section partially overlaps with the steps. The 'Do_Not_Use_When' section is useful but slightly verbose with parenthetical explanations. Some XML-style tags add structural overhead without adding clarity over markdown headers. | 2 / 3 |
Actionability | The skill provides concrete, executable Task() invocations with specific model parameters, clear tier routing guidance, and good/bad examples with explanations. The steps are specific and the tool usage section gives copy-paste ready patterns. | 3 / 3 |
Workflow Clarity | The 10-step workflow is clearly sequenced from intent grounding through context gathering, task classification, graph creation, routing, execution, and verification. It includes explicit validation checkpoints (step 10), dependency handling (step 8), and background operation guidance (step 9). The escalation and stop conditions provide clear error recovery paths. | 3 / 3 |
Progressive Disclosure | The skill references external files like 'docs/shared/agent-tiers.md' and 'docs/REFERENCE.md' which is good, but no bundle files are provided to verify these exist. The content is somewhat monolithic — the examples, execution policy, and advanced relationship diagram are all inline rather than split into separate reference files. The Advanced section at the bottom is a reasonable attempt at layering but the overall document is long. | 2 / 3 |
Total | 10 / 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
3e94567
- 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.