dart-migrate-to-checks-package

Replace the usage of `expect` and similar functions from `package:matcher` to `package:checks` equivalents.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/dart-migrate-to-checks-package/SKILL.md

Quality

Content

85%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 thorough, executable migration guide with concrete commands, code examples, and a validated workflow with feedback loops. Its main weakness is progressive disclosure: a large reference is monolithically inlined rather than split into separate files.

Suggestions

Split the large matcher-to-checks mapping table and the 'Writing Custom Expectations' section into separate reference files (e.g. MAPPING.md, CUSTOM.md) linked from the overview.

Tighten verbose pitfall introductions; lead with the before/after code and keep rationale to one line.

Fix the malformed code fragment at the sync throws example (`check(() => triggerSync")`) which would not compile as written.

Dimension	Reasoning	Score
Conciseness	Largely efficient and avoids explaining concepts Claude already knows, but some prose-heavy intros and verbose pitfall explanations could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready executable commands (`dart pub add dev:checks`, `dart analyze`, `dart test`) and complete before/after Dart examples covering the common migration cases.	5 / 5
Workflow Clarity	Four-step workflow has explicit validation checkpoints (compiler-as-verifier, `dart analyze`, `dart test`) with a documented feedback loop for diagnosing failures.	5 / 5
Progressive Disclosure	Has clear section structure and a TOC, but a substantial reference (mapping table, custom-expectations guide) is inlined into a 530-line file with no external file splitting or one-level-deep references.	3 / 5
	Total	17 / 20 Passed

Description

57%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 sharply targeted to a distinct niche with concrete source/target packages, but it states only the 'what' and lacks an explicit 'when to use' trigger clause and natural user phrasings. Completeness is capped at 3 by the missing 'Use when...' guidance.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when migrating a Dart test suite to package:checks or modernizing legacy expect() assertions.'

Include natural user trigger phrases such as 'migrate tests to checks', 'modernize test assertions', or 'use package:checks' alongside the technical symbols.

Expand 'similar functions' into concrete specifics like 'expect, expectLater, and matcher functions' to raise specificity beyond a single named action.

Dimension	Reasoning	Score
Specificity	Names a concrete action ('Replace') and concrete source/target symbols (`expect`, `package:matcher`, `package:checks`), but covers only one action with the vague hand-wave 'similar functions' rather than multiple specific actions.	3 / 5
Completeness	Clearly states the 'what' (replace expect/matcher with checks equivalents) but has no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Includes relevant technical keywords (`expect`, `package:matcher`, `package:checks`) but omits the natural user phrasings like 'migrate tests to checks' or 'modernize test assertions' that appear only in the body.	3 / 5
Distinctiveness Conflict Risk	Targets a uniquely specific niche (matcher-to-checks migration) with technical triggers no other skill would match, giving minimal conflict risk.	5 / 5
	Total	14 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (529 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: flutter/agent-plugins
Path: skills/dart-migrate-to-checks-package/SKILL.md
Commit: 864cf87

Reviewed: ~9 hours ago

Table of Contents

Discovery Implementation Validation

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.