CtrlK
BlogDocsLog inGet started
Tessl Logo

flutter-add-widget-test

Implement a component-level test using `WidgetTester` to verify UI rendering and user interactions (tapping, scrolling, entering text). Use when validating that a specific widget displays correct data and responds to events as expected.

74

Quality

92%

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

100%

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

The body is well-structured, actionable, and concise, with a sequenced workflow that includes an explicit feedback loop and a complete runnable example. Minor redundancy between the workflow steps and the interaction-patterns section is the only tightening opportunity.

DimensionReasoningScore

Conciseness

Lean and efficient: it assumes Flutter competence, avoids explaining basics, and every section (components, workflow, interaction patterns, runnable example) earns its place without concept-fluff.

3 / 3

Actionability

Provides fully executable Dart code, specific API calls (tester.pumpWidget, tester.tap, tester.enterText, pumpAndSettle), and a concrete run command, all copy-paste ready.

3 / 3

Workflow Clarity

A clear 9-step sequenced checklist with an explicit feedback loop in Step 9 ('Review test output -> identify failing matchers -> adjust -> re-run until passing'), matching the clear-sequence-with-feedback anchor.

3 / 3

Progressive Disclosure

A single self-contained file organized with a table of contents and well-delineated sections; no external references are needed at this scope, so one-level structure is appropriate.

3 / 3

Total

12

/

12

Passed

Description

85%

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, specific description with an explicit use-when trigger and a clear Flutter widget-testing niche. Its main gap is trigger-term coverage — it leans on the technical 'WidgetTester'/'component-level test' phrasing and omits the common natural terms 'Flutter' and 'widget test'.

Suggestions

Add natural trigger terms users actually say, e.g. 'Use when writing Flutter widget tests, testing a widget, or validating widget rendering and interactions'.

Include the word 'Flutter' explicitly so the description matches how users reference this ecosystem.

Consider mentioning 'testWidgets' or 'flutter test' as additional recognizable keywords.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'verify UI rendering and user interactions (tapping, scrolling, entering text)' — matching the multi-action anchor rather than the single-domain anchor at 2.

3 / 3

Completeness

Explicitly states what it does and provides an explicit 'Use when validating...' trigger clause, satisfying both the what and the when.

3 / 3

Trigger Term Quality

Includes relevant terms ('WidgetTester', 'widget', interaction verbs) but omits common natural variations a user would say, notably 'Flutter' and the phrase 'widget test', so it does not reach full coverage.

2 / 3

Distinctiveness Conflict Risk

Targets a clear niche (Flutter component-level widget tests with WidgetTester) with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

11

/

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.