CtrlK
BlogDocsLog inGet started
Tessl Logo

dart-collect-coverage

Collect coverage using the coverage packge and create an LCOV report

59

Quality

68%

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

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable commands and well-sequenced workflows including explicit validation feedback loops. It is held back by a slightly redundant test-fundamentals section and a single-file, all-inline structure that leaves no room for progressive disclosure.

Suggestions

Trim or remove the 'Testing Fundamentals' definitions of unit/component/integration tests, which Claude already knows.

Consider splitting the 'Advanced Manual Coverage Collection' workflow and the Examples into separate reference files linked from a concise overview.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands and code, but the 'Testing Fundamentals' section defines unit/component/integration tests that Claude already knows; not 3 due to that unnecessary explanation, not 1 because it avoids concept padding elsewhere.

2 / 3

Actionability

Provides fully executable commands (e.g., 'dart pub add dev:coverage', 'dart run coverage:test_with_coverage') and complete YAML/Dart examples that are copy-paste ready; matches the highest anchor.

3 / 3

Workflow Clarity

Both workflows use numbered steps, task-progress checklists, and an explicit 'Feedback Loop: Validate Output' with verify→fix guidance; matches the anchor for clear sequence with validation checkpoints.

3 / 3

Progressive Disclosure

Well-organized with a TOC and clear sections, but all ~130 lines are inline with no bundle files or one-level-deep references, and the advanced manual workflow and examples could be split out; not 3 because content is not appropriately split.

2 / 3

Total

10

/

12

Passed

Description

60%

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 concise and names concrete actions, but it omits any "when to use" trigger guidance and the typo ("packge") plus missing common terms (test coverage, Dart/Flutter) weaken trigger quality and distinctiveness.

Suggestions

Add a 'Use when...' clause stating when to invoke the skill (e.g., 'Use when adding test coverage to a Dart or Flutter project').

Include common natural terms like 'test coverage', 'Dart', and 'Flutter' so users' phrasing matches the trigger.

Fix the typo 'packge' → 'package' in the description.

DimensionReasoningScore

Specificity

Names two concrete actions — "Collect coverage" and "create an LCOV report" — matching the anchor that lists multiple specific concrete actions; not score 2 because it goes beyond naming only a domain.

3 / 3

Completeness

Clearly states what the skill does but lacks any "Use when..." or equivalent explicit trigger guidance, capping completeness at 2 per the rubric; not 1 because the "what" is explicit.

2 / 3

Trigger Term Quality

Contains relevant keywords ("coverage", "LCOV report") but omits common variations a user would say such as "test coverage", "Dart", or "Flutter"; not 3 because coverage of natural terms is incomplete.

2 / 3

Distinctiveness Conflict Risk

The coverage/LCOV niche is fairly specific, but without Dart/Flutter framing it could overlap with other coverage tooling; not 3 because distinct triggers are not stated.

2 / 3

Total

9

/

12

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.

Validation15 / 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.