CtrlK
BlogDocsLog inGet started
Tessl Logo

grade-iterate

Phase 3 of building a Claude Managed Agent — the bounded grade→iterate loop. Define a CMA outcome (a required markdown rubric graded by an isolated grader), read each verdict, decide the next move (sharpen / re-run / promote to schedule), and once a version passes, run held-back eval cases in parallel. Use when the user says "grade my agent", "make it pass the rubric", "iterate until it's good", "is it good enough", or when the orchestrator routes phase=grade-iterate. outcome_builder.py builds the user.define_outcome payload (rubric required, max_iterations clamped 1..20 — never unbounded); verdict_reader.py reads the grader result and recommends the next move; eval_scaffold.py generates held-back cases + a parallel run plan (capped at the 25-thread CMA ceiling). Distinct from stage-launch (first launch) and run-without-you (scheduling).

72

Quality

91%

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

The canonical home for this skill is grade-iterate in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

The body is a tight, executable grade→iterate playbook with concrete commands, an explicit verdict-driven feedback loop, and a hard-rules checklist. The main gaps are minor: a redundant Tools recap, an implicit eval-pass gate before SHIP, and reference links that point to files not bundled with the skill.

Suggestions

Bundle the referenced scripts (outcome_builder.py, verdict_reader.py, eval_scaffold.py) under scripts/ and the referenced docs under references/ so the in-body links resolve within the skill bundle.

In step 5, add an explicit checkpoint requiring the held-back eval results to pass the rubric before SHIP or promote, mirroring the verdict-read gate in step 2.

Drop or compress the Tools section (it recapitulates the workflow's script invocations) to remove the duplication and tighten token use.

DimensionReasoningScore

Conciseness

The body is lean — it skips explanations of what a rubric/grader is and goes straight to commands — but the 'Tools' section recap duplicates the script invocations already shown in the workflow. Matches 'efficient; minor instances of over-explanation that could be trimmed'; not a 5 because of that redundant recap, not a 3 because nothing is padded or condescending.

4 / 5

Actionability

Three full copy-paste bash commands with all flags and concrete example values (outcome_builder.py, verdict_reader.py, eval_scaffold.py) plus goal_state.py cover the common cases, matching the 'fully executable; copy-paste ready' anchor. Not a 4 because the commands are complete with realistic arguments rather than having gaps.

5 / 5

Workflow Clarity

Five clearly sequenced steps with explicit validation (verdict_reader gate) and feedback loops (SHARPEN/re-run, ESCALATE on no progress, ≤1-iteration flip), plus a Hard-rules checklist. Matches 'clear sequence with most checkpoints present; minor validation gaps'; the gap is that step 5 (Decide/SHIP) does not explicitly require the held-back eval to pass before shipping, which keeps it off the 5 anchor.

4 / 5

Progressive Disclosure

Well-sectioned (Workflow, Hard rules, Forcing-question library, Tools) with clearly signaled, one-level-deep reference links. Matches 'good structure; references mostly clear; minor organization gaps'; not a 5 because the referenced files (scripts/*.py and ../../references/*.md) are not present in the skill bundle, so the links do not resolve, and not a 3 because references are explicitly signaled and nothing that belongs in a separate file is inlined.

4 / 5

Total

17

/

20

Passed

Description

100%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.

The description is a strong, third-person activation spec: it states concrete capabilities, gives multiple natural trigger phrases, explicitly bounds when to use it, and disambiguates it from sibling phases. Every dimension lands at the top anchor.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Define a CMA outcome', 'read each verdict', 'decide the next move (sharpen / re-run / promote to schedule)', 'run held-back eval cases in parallel') and names the exact tools (outcome_builder.py, verdict_reader.py, eval_scaffold.py), matching the comprehensive-coverage anchor. It is not a 4 because coverage is thorough rather than having only minor gaps; it uses third-person voice with no first/second person penalty.

5 / 5

Completeness

Explicitly answers both what (define outcome, read verdicts, decide next move, run held-back eval) and when ('Use when the user says ...') with concrete trigger phrases, matching the anchor. Not a 4 because the 'when' is fully explicit with quoted triggers rather than only somewhat specific.

5 / 5

Trigger Term Quality

Gives several natural phrases a user would actually say — 'grade my agent', 'make it pass the rubric', 'iterate until it's good', 'is it good enough' — plus the orchestrator route phase=grade-iterate, giving comprehensive natural-term coverage for this domain. Not a 4 because the trigger set is broad and on-point rather than missing common variations.

5 / 5

Distinctiveness Conflict Risk

Carves a clear niche (Phase 3 grade→iterate loop) and explicitly states 'Distinct from stage-launch (first launch) and run-without-you (scheduling)' with a unique orchestrator route, minimizing overlap risk. Not a 4 because it both names a distinct niche and disambiguates the adjacent skills.

5 / 5

Total

20

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 2 suspicious

Warning

referenced_paths_exist

Referenced path issues: 6 missing

Warning

Total

13

/

16

Passed

Repository
alirezarezvani/claude-skills
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.