CtrlK
BlogDocsLog inGet started
Tessl Logo

dart-add-unit-test

Write and organize unit tests for functions, methods, and classes using `package:test`. Use when creating new logic or fixing bugs to ensure code remains correct and regression-free.

70

Quality

86%

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

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.

A tight, highly actionable skill body with executable examples, specific commands, and a workflow checklist that includes a feedback loop. The only modest improvement is optional splitting of the longer examples into reference files.

Suggestions

Consider moving the full Mockito example into a references/ file and keeping a compact snippet inline to reduce body length.

Tighten a few explanatory clauses (e.g., 'to maintain predictability') to push conciseness toward a 5.

DimensionReasoningScore

Conciseness

Efficient and assumes Claude's competence (no basic-concept padding), with only minor phrasing that could be trimmed (e.g., 'to maintain predictability').

4 / 5

Actionability

Fully executable guidance: copy-paste-ready Dart examples plus specific commands ('dart test', 'flutter test integration_test') covering grouping, setup, async, and Mockito mocking.

5 / 5

Workflow Clarity

The Test Implementation Workflow is a numbered checklist with an explicit feedback loop (run -> review stack trace -> fix -> re-run until passing), satisfying the validation-checkpoint requirement.

5 / 5

Progressive Disclosure

Well-organized single-file skill with a Contents nav and clear section headers; no bundle files are needed or referenced, though the two full code examples could arguably live in a separate references file.

4 / 5

Total

18

/

20

Passed

Description

83%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 strong, third-person description that clearly states both the capability and the usage trigger with concrete, domain-specific language. Minor gains are available by adding a few more synonyms and a sharper niche signal.

Suggestions

Add a couple of natural synonyms (e.g., 'test coverage', 'testing') to broaden trigger-term coverage.

Reinforce the Dart/Flutter niche earlier in the sentence to further reduce overlap with language-agnostic testing skills.

DimensionReasoningScore

Specificity

Names the domain (Dart/Flutter unit tests) and several concrete actions ('Write and organize unit tests for functions, methods, and classes using `package:test`'), with only minor coverage gaps (e.g., no mention of grouping or assertions).

4 / 5

Completeness

Explicitly answers both what ('Write and organize unit tests for functions, methods, and classes using `package:test`') and when ('Use when creating new logic or fixing bugs to ensure code remains correct and regression-free') with a concrete trigger clause.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('unit tests', 'fixing bugs', 'creating new logic', 'regression-free'); a few common synonyms like 'test coverage' or 'testing' are absent.

4 / 5

Distinctiveness Conflict Risk

The `package:test` reference pins it clearly to the Dart/Flutter niche with minimal conflict risk, though 'unit tests' alone is broad enough to overlap with general testing skills.

4 / 5

Total

17

/

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.