CtrlK
BlogDocsLog inGet started
Tessl Logo

flutter-fix-layout-issues

Fixes Flutter layout errors (overflows, unbounded constraints) using Dart and Flutter MCP tools. Use when addressing "RenderFlex overflowed", "Vertical viewport was given unbounded height", or similar layout issues.

72

Quality

90%

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

86%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 focused, actionable skill body: verbatim error signatures mapped to concrete fixes, a sequenced checklist with a validate-and-retry loop, and complete input/output Dart examples for the three common overflow cases. Only minor token inefficiency from restating Flutter layout fundamentals Claude already knows.

DimensionReasoningScore

Conciseness

The body is largely efficient — error signatures, a checklist, and code examples with little padding — but the opening 'Constraints go down. Sizes go up. Parent sets position.' paragraph and repeated inline code comments restating the fix explain Flutter mechanics Claude already knows, keeping it just below the lean 5 anchor.

4 / 5

Actionability

Provides fully executable, copy-paste-ready Dart snippets for three common cases (input error state and resolved state each), plus a conditional 'If X: wrap in Y' decision table keyed to exact error messages — concrete and covering the common cases per the 5 anchor.

5 / 5

Workflow Clarity

The 'Task Progress' checklist gives a clear sequence with an explicit validation/retry step ('Run validator -> review errors -> fix... If new layout errors appear, repeat the workflow'), matching the 4 anchor with a feedback loop; it stops short of a fully elaborated 5-style gated validate-then-proceed protocol, and the operation is iterative debugging rather than destructive/batch so the cap does not apply.

4 / 5

Progressive Disclosure

For a single-purpose skill under ~130 lines with no external references, the content is well-organized into clearly signaled sections (Diagnostics, Workflow, Examples) with a working contents list; per the simple-skills note, well-organized sections without nested references warrant a 5.

5 / 5

Total

18

/

20

Passed

Description

95%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, well-targeted description that pairs a concrete 'what' with verbatim console-error triggers users actually encounter. The only minor gap is action breadth — 'fixes' is one verb covering a family of fixes — but trigger quality and completeness are exemplary.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — 'Fixes Flutter layout errors (overflows, unbounded constraints)' using specific tooling ('Dart and Flutter MCP tools') — but the action set is narrow (essentially 'fixes' with two error categories) rather than a comprehensive multi-action list, sitting clearly above the 3 anchor but below 5.

4 / 5

Completeness

Explicitly answers both 'what' ('Fixes Flutter layout errors (overflows, unbounded constraints) using Dart and Flutter MCP tools') and 'when' ('Use when addressing "RenderFlex overflowed"...') with concrete trigger phrases, matching the 5 anchor.

5 / 5

Trigger Term Quality

Quotes exact natural error strings users would paste from a console — 'RenderFlex overflowed', 'Vertical viewport was given unbounded height' — plus 'overflows', 'unbounded constraints', and 'layout issues', giving comprehensive coverage of the real phrases developers say; not just technical jargon.

5 / 5

Distinctiveness Conflict Risk

The error-string triggers are highly specific to Flutter layout diagnosis, creating a clear niche with minimal overlap risk against other skills; a user reporting these exact errors would unambiguously want this skill.

5 / 5

Total

19

/

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.