Routing table present

Skill coverage summary correct

rewrite-intro out-of-scope determination

generate-bibliography routing gap determination

fix-heading-hierarchy routing gap determination

citation-generator description rewrite

markdown-formatter description rewrite

Minimal rewrite principle

Rewrites presented together

Scored eval data cited

SKILL.md not modified

Explicit approval request

Trade-off discussion

Risk assessment per recommendation

Grouped presentation

All key issues addressed

Priority summary present

Current score per recommendation

Retry count contradiction found

Auth failure contradiction found

All three files referenced

File attribution per contradiction

Auth contradiction despite scope

Verbatim quotes included

Bucket A: idempotency key

Bucket B: webhook signature

Bucket C: HTTP status codes

Bucket B: currency precision

Bucket D: API version pinning

Bucket D highest priority

Bucket B diagnosis present

Bucket C action suggested

Bucket A no-action

80% threshold applied

Overall summary table

Per-scenario breakdown

Per-criterion table

Correct symbol thresholds

Baseline interpretation

Universal Failure identified

Capability Gradient identified

Regression identified

Fix before publish recommendation

eval-improve mentioned

Re-run offer

Skill count detection command

Activation eval run first

Scored eval follows activation

Routing-clean gate explained

Skip activation condition stated

Correct eval run command format

--solver=activation flag used

Tile path used consistently

REFERENCE.md not recreated

No REFERENCE.md changes proposed

SKILL.md produced

Use when clause added

Inline duplication removed

REFERENCE.md linked

Core examples retained

SKILL.md shorter

Change log documents SKILL.md changes

Change log explains why

Regression identified

Regression is highest priority

High baseline warning present

Scenario regeneration suggested

Tile is actively hurting

Per-criterion regression analysis

Correct prioritization order

Lists all bundle files

Identifies referenced files

Identifies orphaned files

TRANSACTIONS.md recommendation

PERFORMANCE.md recommendation

SECURITY.md recommendation

LEGACY_EXAMPLES.md recommendation

DRAFT_REPLICATION.md recommendation

Bloat reduction framing

Clear routing signals emphasis

Link vs remove justification

Python via ast.parse

Python error identified

JavaScript via node --check

Command flag validation

File reference check

Broken reference identified

Validation before application

Per-check pass/fail

Fix suggestions

Overall before/after format

Percentage delta shown

Per-dimension breakdown

Arrow notation or equivalent

Dimension change labelled

Dimensions impact explained

Correct overall scores

Completeness improvement noted

Actionability improvement noted

Conciseness unchanged noted

Robustness improvement noted

Code syntax check included

Python syntax error found

Command flags check included

File references check included

File reference passes

Use when clause check included

Use when clause fails

Known concepts check included

Known concepts issue found

Readiness summary

Excludes .tessl cache

.tessl/tiles warning

Scenario existence check

Scenario generation guidance

Login verification

No --workspace flag

Default model names

Model subset confirmation

Time estimate provided

Run count option

Critical issues first

High before Medium/Low

Summary with priorities

Expected improvement in summary

Dimension score included

Before/after examples

Impact stated per recommendation

Educational WHY included

All four issues addressed

Approval framing

Identifies good references

Explains why good

Identifies poor references

Explains why poor

Token efficiency framing

Routing gate test

Improves CONFIGURATION.md

Improves GUIDE.md

Improves EXAMPLES.md

Improves ADVANCED.md or REFERENCE.md

Questions blind split recommendation

Linking over inlining

Reference file identified

Severity mappings removed

Flag tables removed

Template list removed

SKILL.md substantially shorter

Core examples preserved

Before/after shown

WHY explained

REFERENCE.md not modified

All redundant criteria identified

Options presented per criterion

Useful criteria preserved

Weight redistribution correct

80% threshold applied

Non-redundant scores unchanged

Below-threshold excluded

Removal option named explicitly

Contradicting clause identified

Contradiction mechanism explained

Remove/clarify approach taken

Specific text targeted

No compensating additions

Other sections preserved

Pre-review list intact

Uses --strategy merge

Does NOT use --strategy replace

Correct base command

Output directory specified

Verification step present

Run ID or --last used

Existing scenarios preserved

identifies_scenario_1_acceptable

detects_answer_leakage

explains_leakage_impact

detects_double_counting

detects_free_point_criterion

proposes_specific_fixes

no_false_positives_scenario_1

Completeness weight correct

Conciseness weight correct

Actionability weight correct

Use when clause highest impact

Use when quantified

Revised description includes Use when

Executable code recommended

Known concepts flagged

High-impact first ordering

Dimension coverage

Correct base command

--agent flag format

All three default models

Sequential execution

Run ID capture

Model-to-ID mapping

Monitoring URL output

Polls with tessl eval view

Retry on failure

Waits for all to complete

No --workspace flag

Explicit retry intervals

Rubric language used

HMAC section unchanged

TLS section unchanged

Observability section unchanged

Processing section unchanged

Retry section only changed

Concise addition

Max retry count preserved

Fast acknowledgement preserved

tessl skill review command

Review before changes

Review after changes

Validation before apply

Python ast.parse validation

node --check JS validation

Command --help flag validation

File reference validation

Before/after score output

Script accepts SKILL.md path

Phases are ordered

tessl tile lint command used

Tile path argument provided

Lint run after each change set

Token cost ballooning flagged

Move to docs recommended

Docs vs rules distinction

Does NOT recommend rules for heavy content