CtrlK
BlogDocsLog inGet started
Tessl Logo

flutter-expert

Master Flutter development with Dart 3, advanced widgets, and multi-platform deployment.

38

Quality

36%

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/flutter-expert/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

25%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 body is a persona prompt — an exhaustive catalogue of Flutter ecosystem capabilities, behavioral traits, and knowledge areas — rather than operational guidance. It contains no executable examples, its only reference points to a nonexistent file, and its workflow steps are generic placeholders.

Suggestions

Replace the capability/behavioral/knowledge catalogues with a short overview plus concrete, executable examples (e.g., a Riverpod provider skeleton, a platform-channel snippet, a golden-test command) for the most common tasks.

Create the referenced bundle files or fix the path: 'resources/implementation-playbook.md' does not exist; either supply it under a real directory (e.g., references/implementation-playbook.md) and update the link, or remove the reference.

Rewrite the Instructions/Response Approach sections into a concrete sequenced workflow with explicit validation checkpoints (e.g., 'run flutter analyze and widget tests before presenting changes'), cutting the ~150 lines of ecosystem enumeration that Claude already knows.

DimensionReasoningScore

Conciseness

The body spends ~150 lines enumerating Flutter/Dart ecosystem knowledge Claude already has ('Riverpod 2.x', 'Bloc/Cubit', 'GetIt, Injectable', 'Impeller rendering engine optimization'), which is padding rather than new information; it is not 1 because it lists capabilities instead of explaining basic concepts at length.

2 / 5

Actionability

There is no executable code or command anywhere in the body; guidance is limited to high-level hints like 'Apply relevant best practices and validate outcomes' and 'Recommend state management solution based on complexity', plus a pointer to 'resources/implementation-playbook.md' which does not exist in the bundle — matching 'minimal concrete guidance; high-level hints but missing the specific steps to execute'.

2 / 5

Workflow Clarity

A rough sequence exists ('Clarify goals, constraints, and required inputs' → 'Apply relevant best practices and validate outcomes' → 'Provide actionable steps and verification'), but the steps are generic template language with no concrete commands or explicit validation checkpoints, matching 'rough sequence present but many gaps; validation absent'.

2 / 5

Progressive Disclosure

The single reference 'resources/implementation-playbook.md' is a dangling path (no resources/, references/, scripts/, or assets/ directories exist in the bundle), and ~150 lines of capability lists that clearly belong in separate reference files are inlined in SKILL.md, matching 'minimal structure; content that clearly belongs in separate files is inlined'.

2 / 5

Total

8

/

20

Passed

Description

48%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 identifies a clear niche (Flutter/Dart 3 development) but reads as a topic summary rather than a capability statement: it lists no concrete actions and provides no 'when to use' trigger guidance. Adding explicit use-when phrasing and 1-2 concrete actions would raise it substantially.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g., 'Use when building, debugging, or deploying Flutter apps, or when the user mentions Flutter, Dart, widgets, or app stores.'

Replace the aspirational 'Master Flutter development' with concrete actions, e.g., 'Architect Flutter apps, optimize widget performance, integrate platform channels, and deploy to iOS, Android, web, and desktop.'

Include common user phrasings and synonyms such as 'cross-platform app', 'state management (Riverpod, Bloc)', and '.dart files' to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('Master Flutter development with Dart 3, advanced widgets, and multi-platform deployment') but 'Master' is aspirational and the remaining items are topic labels, not concrete actions — matching 'names the domain but actions are minimal or generic' rather than the 3 anchor, which requires 1-2 explicit actions.

2 / 5

Completeness

The 'what' is stated reasonably clearly (Flutter development with Dart 3, advanced widgets, multi-platform deployment), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines; it is not 2 because the 'what' is not vague.

3 / 5

Trigger Term Quality

'Flutter development', 'Dart 3', 'widgets', and 'deployment' are natural terms users would say, but common variations are missing (e.g., 'Flutter app', 'iOS/Android app', 'state management', 'cross-platform'), matching 'some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

Flutter with Dart 3 is a clear niche with distinct triggers and minimal conflict risk against unrelated skills; only minor overlap risk exists with a generic Dart or mobile-development skill, matching 'mostly distinct; minor overlap risk with closely related skills'.

4 / 5

Total

12

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
sickn33/agentic-awesome-skills
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.