CD coral-new-task
End-to-end recipe for adding a new task under `examples/` — the three pieces that have to line up (`task.yaml`, `seed/`, and `grader/`), what to put in each, the `TaskGrader` API surface, the `coral validate` → smoke-test loop, and the common mistakes (repo_path pointing at the wrong dir, score direction backwards, hidden answer keys leaking into seed/, grader writing to codebase_path which the daemon force-removes, private-vs-public confusion, missing `run()` signature). Use whenever the user wants to add a new CORAL task or port an existing benchmark into CORAL.
End-to-end recipe for adding a new task under examples/ — the three pieces that have to line up (task.yaml, seed/, and grader/), what to put in each, the…
As a process D 46/100 · Unfinished process — References files that are not bundled: examples/erdos/, examples/dna_design/, examples/swebench-verified/
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: examples/erdos/ - warning
missing-refreference to a missing file: examples/dna_design/ - warning
missing-refreference to a missing file: examples/swebench-verified/ - warning
missing-refreference to a missing file: examples/circle_packing/ - warning
missing-refreference to a missing file: examples/mnist/ - warning
missing-refreference to a missing file: examples/erdos/grader/pyproject.toml - warning
missing-refreference to a missing file: examples/dna_design/grader/src/dna_design_grader/grader.py - warning
missing-refreference to a missing file: examples/dna_design/grader/pyproject.toml - warning
missing-refreference to a missing file: examples/ADRS/txn_scheduling/ - warning
missing-refreference to a missing file: examples/README.md - warning
missing-refreference to a missing file: examples/<task>/ - warning
missing-refreference to a missing file: examples/<task>/seed/
Process rating: all ten parameters 46/100
- 0Tools and files. 12 referenced file(s) missing: examples/erdos/, examples/dna_design/, examples/swebench-verified/
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 85Steps. 7 steps, 2 vague phrases
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3208 tokens
- 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 (10 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 570: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 7 items
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.