CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dart-migrate-to-checks-package

Use when migrating test assertions from legacy package:matcher expect() syntax to package:checks fluent assertions.

Quality

78%

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

Fix and improve this skill with Tessl

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

Quality

Content

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

A highly actionable, well-structured migration guide with executable code covering the common assertion cases and a clear validation-backed workflow. Its chief weaknesses are mild verbosity in the motivational 'Why Migrate' section and a monolithic layout with no progressive disclosure to separate reference files.

Suggestions

Trim or remove the 'Why Migrate' benefit bullets, since a user invoking this skill has already decided to migrate; lead with the dependency setup and mapping table instead.

Add an explicit error-recovery loop to the workflow (e.g. 'If dart analyze reports type mismatches, fix them and re-run before executing tests') to reach the top workflow-clarity anchor.

Consider moving the lengthy worked Examples into a separate reference file (e.g. references/migration-examples.md) referenced from the body, to improve progressive disclosure now that the skill exceeds 50 lines.

DimensionReasoningScore

Conciseness

The body is mostly efficient code and a mapping table, but the 'Why Migrate' benefit bullets ('Fluent API', 'Type Safety', 'Descriptive Diagnostics') and some descriptive prose in the async section explain value the user/Claude already knows, matching the 'mostly efficient but includes some unnecessary explanation' anchor rather than the lean score-4 anchor.

3 / 5

Actionability

Provides fully executable, copy-paste-ready guidance — `dart pub add dev:checks`, real imports, a complete legacy→modern mapping table, cascade/Stream/Future/exception examples, and a full migration comparison — covering the common cases, matching the top anchor.

5 / 5

Workflow Clarity

The migration checklist is a clear sequenced workflow with explicit validation checkpoints ('Validate compiler checks: Run dart analyze', 'Execute tests: Run dart test'), matching the 'clear sequence with most checkpoints' anchor; it stops short of 5 because there is no explicit error-recovery feedback loop (e.g. 'if analyze fails, fix and re-run').

4 / 5

Progressive Disclosure

Well-organized with a table of contents and clearly headed sections, but the skill is monolithic — all content is inline with no references to separate files, and at ~130 lines it exceeds the under-50-line simple-skill exception that would otherwise allow a 5, so it sits at the 'good structure, minor organization gaps' anchor.

4 / 5

Total

16

/

20

Passed

Description

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

A concise, third-person trigger description that clearly states a specific Dart migration task with concrete trigger terms and minimal conflict risk. Its main weakness is fusing the 'what' and 'when' into one clause and naming only a single action, which limits specificity and completeness from reaching the top anchors.

Suggestions

Separate the 'what' from the 'when' (e.g. 'Migrate test assertions from package:matcher expect() syntax to package:checks fluent assertions. Use when converting Dart tests from matcher to checks, or when the user mentions expect(), matcher, or checks.')

Add synonym trigger terms such as 'convert' or 'refactor' alongside 'migrating' to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

Names the domain (test assertions) and one concrete action ('migrating test assertions from legacy package:matcher expect() syntax to package:checks fluent assertions') with precise from/to identifiers, but lists only a single action rather than several, matching the '1-2 concrete actions' anchor rather than the 'several specific actions' anchor above.

3 / 5

Completeness

The 'Use when...' clause explicitly supplies the trigger and embeds the 'what' (migrate matcher→checks), answering both what and when with a concrete trigger phrase; however the two are fused into a single clause without multiple trigger phrasings, so it does not reach the cleanly separated score-5 anchor.

4 / 5

Trigger Term Quality

Includes natural terms a Dart user would actually say — 'matcher', 'expect()', 'package:checks', 'migrating test assertions' — giving good keyword coverage, though synonyms like 'convert' or 'refactor' are absent, keeping it just below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Dart package:matcher → package:checks migration) with distinct technical triggers, making it unlikely to fire for unrelated skills and matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

dhruvanbhalara/skills

Path

skills/dart/dart-migrate-to-checks-package/SKILL.md

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.