CtrlK
BlogDocsLog inGet started
Tessl Logo

dart-collect-coverage

Collect coverage using the coverage packge and create an LCOV report

60

Quality

71%

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

88%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 content is highly actionable with copy-paste-ready commands and two well-sequenced workflows that include an explicit validation feedback loop. It is lean with only minor over-explanation and is well-structured as a single self-contained file.

DimensionReasoningScore

Conciseness

The body is mostly efficient with direct commands and minimal preamble, but contains minor over-explanation ('Do not add it to standard dependencies', the Testing Fundamentals taxonomy) that could be trimmed, fitting the 'efficient with minor over-explanation' anchor rather than fully lean.

4 / 5

Actionability

Fully executable, copy-paste-ready commands cover the common cases including the standard vs Flutter variant, the workspace directory note, and optional branch/function flags, matching the 'fully executable, specific examples cover common cases' anchor.

5 / 5

Workflow Clarity

Both workflows are clearly sequenced with numbered task-progress checklists, and the primary workflow ends in an explicit validation feedback loop ('Run validator -> review errors -> fix') with concrete success criteria, matching the top anchor.

5 / 5

Progressive Disclosure

No bundle files exist (references/scripts/assets absent) and the single self-contained file is well-organized with a TOC and clear sections; structure is good with no nested references, though it is longer than the under-50-line simple-skill exception, so it sits at 4 rather than 5.

4 / 5

Total

18

/

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 clearly states what the skill does but omits any when-to-use trigger guidance and lacks common synonyms, leaving it at the midpoint across most dimensions. It is distinct enough as a niche but would benefit from explicit trigger phrasing.

Suggestions

Add a 'Use when...' clause naming natural triggers, e.g. 'Use when the user asks for Dart or Flutter test/code coverage, LCOV reports, or coverage configuration.'

Include common synonyms and specifics such as 'Dart', 'Flutter', 'test coverage', and 'code coverage' to broaden natural keyword coverage.

Fix the typo 'packge' -> 'package' in the description.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ("Collect coverage using the coverage package" and "create an LCOV report"), matching the 1-2 concrete actions anchor; it does not enumerate several actions so it is not a 4.

3 / 5

Completeness

The what is clear (collect coverage, create an LCOV report) but there is no 'Use when...' clause or equivalent trigger guidance, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant terms (coverage, LCOV, coverage package) appear but common natural variations (test coverage, code coverage, Dart/Flutter) and file extensions are missing, fitting the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The coverage-package-plus-LCOV niche is fairly distinct with low overlap risk, though it omits the Dart/Flutter framing that would make triggers fully unambiguous; mostly distinct with minor overlap risk fits a 4 better than a 3.

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.

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.