Content
67%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill body is a compact, well-structured orchestration protocol: clear when-to-use, sequenced procedure with an explicit fail-fast gate, and a clean one-level-deep reference bundle. Its main weakness is actionability — the circular 'work owned by execution-plan' phrasing and the absence of any concrete stage-result template or example leave the executor dependent on the reference files to know exactly what to produce.
Suggestions
Include a minimal inline example of the stage-result artifact (a few lines showing schema_version, stage, status, evidence_refs, blocked_by, next_stage) so the deliverable is executable without opening contract.yaml.
Replace the circular 'Perform only the work owned by execution-plan' with the concrete scope (e.g., 'Decide implementation order, name target files, select validation gates, and define rollback steps — not writing the code').
Add a load-when hint to each References entry (e.g., 'contract: required for artifact fields; source-context: only when provenance is needed') and drop the verbatim duplicate of the description in When to use.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean with no over-explanation of known concepts, but the When-to-use section duplicates the frontmatter description verbatim and Failure modes overlaps Gotchas (e.g., 'Missing previous-stage artifact: block and request...' vs. procedure step 2). Anchor 4 fits: efficient with minor trimming possible; not 5 because of the duplication and redundancy. | 4 / 5 |
Actionability | Concrete elements exist (Deliverables enumerates 'schema_version, stage, status, evidence_refs, blocked_by, and next_stage' and the pass/fail/blocked/not_checked vocabulary), but steps like 'Perform only the work owned by execution-plan' are circular and the body never shows an artifact template or example — key execution details are missing. Anchor 3 rather than 4 because the guidance is not mostly executable standing alone. | 3 / 5 |
Workflow Clarity | A clear 5-step Procedure with an explicit fail-fast checkpoint ('stop at the first failed required gate... do not proceed to downstream stages') and exit-criteria gating of the handoff; the operation is a planning stage, so the destructive/batch cap does not apply. Not 5 because actual gate commands are unspecified ('run plugin validation and SDK proof commands from the repository wrapper') and no validate→fix→revalidate loop is stated. | 4 / 5 |
Progressive Disclosure | The body is a well-organized overview whose References section links all four real bundle files (contract.yaml, evals.yaml, task-profile.json, source-context.yaml) one level deep with short labels. Anchor 4 rather than 5 because the body gives no load-when guidance per reference (that lives inside source-context.yaml) and labels are terse. | 4 / 5 |
Total | 15 / 20 Passed |