CD ultrawork
The binding ultrawork-mode directive. This file IS the directive; read it only when ultrawork mode is requested and the directive is not already in the conversation.
The binding ultrawork-mode directive.
As a process D 48/100 · Unfinished process — References files that are not bundled: scripts/omowright.mjs
This is a copy of a skill from another catalog; the rating counts the canonical one: ultrawork (code-yeongyu/oh-my-openagent)
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 8103 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: scripts/omowright.mjs
Process rating: all ten parameters 48/100
Will not run. References files that are not bundled: scripts/omowright.mjs
- 0Tools and files. 1 referenced file(s) missing: scripts/omowright.mjs
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 34 mutating operations with no state check
- 40Execution cost. Instruction body is 8103 tokens: crowds the task out of the window
- 50Failures and branches. 0 branches, has a failure section
- 85Steps. 39 steps, 1 vague phrases
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (19 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- -5TODO / placeholder text left in the skill
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +3Description length 165: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 39 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.