CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mass-ulw

Drives dependency-ordered child work through the native workflow tool, each phase's stages defined up front in one run, with retry/amend/send recovery. Use when the user asks for mass-ulw, a DAG of tasks, or fan-out work where some tasks must wait on others.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Excellent orchestration skill content: executable SDK examples with recovery semantics, an explicit evidence-verification contract with feedback loops, and clean one-level progressive disclosure to a verified planning reference. The only notable issue is minor rhetorical over-explanation in the supervision and goal sections that could be tightened for token efficiency.

DimensionReasoningScore

Conciseness

The body is dense with operational rules and assumes Claude's competence — no padding explaining known concepts — but minor over-explanation could be trimmed (e.g., "Observation is supervision, not spectating" rhetoric, the TREAT-AS-FALSE directive stated twice). Not 5 due to these minor rhetorical instances; well above 3's unnecessary-explanation level.

4 / 5

Actionability

Fully executable copy-paste JS for define/node/start/wait, run lifecycle, and recovery, plus the exact Python tool.workflow payload including the detach: False gotcha and refusal codes mapped to remedies. The examples cover the common define-run-recover cases; minor placeholders (run_stub_1, editedDefinition) are fully specified by the earlier definition-shape section.

5 / 5

Workflow Clarity

Clear sequence with explicit validation: a mandatory planning-first gate, an evidence-bound completion contract ("the run ends when the criteria pass, never when the last node reports completion"), recovery feedback loops keyed to refusal codes (node_not_retryable → amend, node_not_continuable → retry, run_still_active → let settle), and mid-run drift correction via send. This satisfies the batch-operation validation requirement fully.

5 / 5

Progressive Disclosure

The body is a well-sectioned overview that defers planning doctrine to a single clearly-signaled, one-level-deep reference (references/planning.md, "read IN FULL", path given), which exists and covers exactly what the body claims (decomposition, routing table, prompt contract, verification wave, failure playbook). No nested references within the bundle.

5 / 5

Total

19

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with explicit what and when clauses, concrete named capabilities, and a distinctive trigger set anchored by the unique skill name. The only weakness is modest synonym coverage in the trigger terms and a few unmentioned capabilities (supervision, resume), which keep specificity and trigger quality at 4 rather than 5.

DimensionReasoningScore

Specificity

Lists several concrete actions — "Drives dependency-ordered child work", "each phase's stages defined up front in one run", "retry/amend/send recovery" — naming distinct define/drive/recover capabilities. Not 5 because coverage has minor gaps (no mention of monitoring, resuming, or supervising runs); clearly above 3's 1-2 actions.

4 / 5

Completeness

Explicitly answers both: what ("Drives dependency-ordered child work through the native workflow tool... with retry/amend/send recovery") and when ("Use when the user asks for mass-ulw, a DAG of tasks, or fan-out work where some tasks must wait on others") with concrete trigger phrases, in third person.

5 / 5

Trigger Term Quality

"mass-ulw", "a DAG of tasks", "fan-out work", "some tasks must wait on others" are natural phrases a user needing this skill would say. Not 5 because common synonyms like "task graph", "orchestrate", or "pipeline" are absent; well above 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

The unique skill name "mass-ulw" and the dependency qualifier ("where some tasks must wait on others") carve a clear niche distinct from plain parallel-spawn or generic workflow skills, minimizing conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

code-yeongyu/oh-my-openagent

Path

packages/omo-senpi/skills/mass-ulw/SKILL.md

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.