CtrlK
BlogDocsLog inGet started
Tessl Logo

dart-collect-coverage

Collect coverage using the coverage packge and create an LCOV report

58

Quality

67%

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-collect-coverage/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 strong, executable guide: concrete commands with correct flags, sequenced checklists, and an explicit validation feedback loop. The only real waste is the generic Testing Fundamentals section, and slightly heavy inline examples that could move to a reference file as the skill grows.

DimensionReasoningScore

Conciseness

The workflows are command-first and tight, but the "Testing Fundamentals" section explains standard test taxonomy (unit/widget/integration, package:test vs flutter_test) that Claude already knows and that is tangential to coverage collection.

3 / 5

Actionability

Every step ships copy-paste-ready commands with real flags (e.g. "dart run coverage:test_with_coverage", "collect_coverage --wait-paused --uri=... --resume-isolates") plus complete pubspec.yaml and Dart ignore-directive examples covering the common cases.

5 / 5

Workflow Clarity

Both workflows are sequentially numbered with "Task Progress Checklist" items and an explicit "Run validator -> review errors -> fix" feedback loop that verifies coverage/coverage.json and coverage/lcov.info with remediation guidance.

5 / 5

Progressive Disclosure

Clean structure with a contents list and two clearly-scoped workflows; at ~135 lines the Examples section (pubspec and ignore-directive samples) could be split into a reference file, which is the minor gap keeping it from a 5.

4 / 5

Total

17

/

20

Passed

Description

53%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 states a concrete, mostly distinct capability but is thin: it lacks any trigger guidance, omits the Dart/Flutter context, misses common user phrasings like "test coverage", and contains a typo ("packge"). It sits at the midpoint of the scale.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for test or code coverage, an LCOV report, or coverage exclusions in a Dart or Flutter project."

Fix the typo "packge" → "package" and mention the Dart/Flutter ecosystem so the description matches the body and reduces conflict risk with other tooling.

Broaden trigger terms to include natural variations users say: "test coverage", "code coverage", "coverage report", "lcov".

DimensionReasoningScore

Specificity

"Collect coverage" and "create an LCOV report" name the domain plus two concrete actions, matching the anchor for a non-comprehensive but concrete description; it does not list several specific actions, so it is not a 4.

3 / 5

Completeness

The description has a clear "what" (collect coverage, create an LCOV report) but no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"coverage", "coverage package", and "LCOV" are relevant keywords, but the natural phrases users would actually say — "test coverage", "code coverage", "Dart", "Flutter" — are missing.

3 / 5

Distinctiveness Conflict Risk

The "coverage package" plus "LCOV report" pairing is a distinct niche with minor overlap risk; without "Dart/Flutter" named, generic "coverage" tooling in other ecosystems could still collide, so it is not a 5.

4 / 5

Total

13

/

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
flutter/agent-plugins
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.