CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/flutter-testing

Authors Flutter tests across the three-layer pyramid - unit (`flutter test`), widget (`testWidgets` + `WidgetTester`), integration (`integration_test` on simulator/emulator/device). Picks the right layer per change, mocks via `mockito` + `build_runner`, LCOV coverage, CI with the Flutter Action. Use when the app is Flutter and the team wants its first-party stack. For React Native use detox-testing; for black-box cross-platform use appium-testing; for YAML-declarative flows use maestro-flows.

75

Quality

94%

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

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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-sequenced testing skill whose code and tables are copy-paste ready and whose structure is easy to navigate. The only weakness is mild verbosity where the Overview restates the testing-pyramid concept Claude already knows.

Suggestions

Trim or collapse the Overview blockquote that re-defines unit/widget/integration tests; reference the pyramid by name and link the docs rather than re-explaining each layer.

Consider moving the full CI workflow yaml (Step 7) and/or the Anti-patterns table into a reference file so SKILL.md stays a tighter overview, improving progressive disclosure for a skill this long.

DimensionReasoningScore

Conciseness

Mostly lean and code-heavy, but the Overview blockquote re-explains what unit/widget/integration tests are ('single function / method / class; mocked dependencies; quick') — a concept Claude already knows — so it could be tightened, matching the 'mostly efficient but includes some unnecessary explanation' anchor.

2 / 3

Actionability

Every step ships copy-paste-ready, executable material — a pubspec.yaml block, runnable Dart test files, bash commands (`flutter test --coverage`), a Mockito example, and a full CI workflow yaml — matching the 'fully executable code/commands' anchor.

3 / 3

Workflow Clarity

A clear Install→Unit→Widget→Integration→Mocks→Coverage→CI sequence where running the tests is itself the validation checkpoint; the operations are non-destructive, so the missing-validation cap does not apply, and the Anti-patterns table supplies explicit error-avoidance guidance.

3 / 3

Progressive Disclosure

No bundle files exist, so the single SKILL.md is judged on its own organization: well-labeled sections (Overview, When to use, Steps 1–7, Anti-patterns, Limitations, References) with one-level-deep, clearly signaled references (the [ft] doc link and sibling skills like lcov-analysis), yielding easy navigation rather than a monolithic wall of text.

3 / 3

Total

11

/

12

Passed

Description

100%

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 concretely states capabilities, gives an explicit use-when trigger, and actively disambiguates from sibling testing skills. It earns the top anchor on all four dimensions.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Authors Flutter tests across the three-layer pyramid', 'Picks the right layer per change', 'mocks via mockito + build_runner', 'LCOV coverage', 'CI with the Flutter Action' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what ('Authors Flutter tests across the three-layer pyramid...') and when ('Use when the app is Flutter and the team wants its first-party stack'), with an explicit 'Use when' trigger clause.

3 / 3

Trigger Term Quality

Natural terms a user would say are well covered — 'Flutter tests', 'app is Flutter', 'Flutter' — alongside the concrete tooling keywords; not merely technical jargon.

3 / 3

Distinctiveness Conflict Risk

Clear Flutter-testing niche, and it explicitly routes conflicting cases elsewhere — 'For React Native use detox-testing; for black-box cross-platform use appium-testing; for YAML-declarative flows use maestro-flows' — making wrong-skill triggers unlikely.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents