flutter-expert

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

Quality

35%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/flutter-expert/SKILL.md

Quality

Content

21%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/capability dump: heavily padded with concepts Claude already knows, no executable code or commands, and an abstract workflow lacking validation. Its one reference is buried and dangling, and content that should live in separate files is inlined.

Suggestions

Cut the Capabilities, Behavioral Traits, Knowledge Base, and Example Interactions lists down to a concise overview; move detail into reference files that actually exist.

Add concrete, copy-paste-ready code examples for the most common Flutter tasks (project scaffolding, a Riverpod provider, a platform channel, a widget test).

Turn the 'Response Approach' into a real workflow with explicit validation checkpoints (e.g. run `flutter analyze`, `flutter test`, build for target platform) and fix or remove the dangling `resources/implementation-playbook.md` reference.

Dimension	Reasoning	Score
Conciseness	The ~195-line body is a padded enumeration of capabilities, behavioral traits, and a knowledge base of concepts Claude already knows (Material Design 3, Riverpod, Bloc, Clean Architecture), matching 'Noticeably verbose; several unnecessary ... padded sections'; it is not 1 because it lists rather than explains basic concepts, and not 3 because the bulk is unnecessary padding.	2 / 5
Actionability	The body contains no executable code or commands and only describes capabilities ('Widget composition patterns', 'Clean Architecture with well-defined layer separation') rather than instructing, matching 'Entirely vague or abstract; no concrete code or commands; only describes rather than instructs'; the generic 'Instructions' and 'Response Approach' do not raise it to 2.	1 / 5
Workflow Clarity	The 8-step 'Response Approach' is a rough sequence ('Analyze requirements', 'Recommend state management') but steps are abstract, poorly defined, and lack any validation checkpoints, matching 'Rough sequence present but many gaps; steps poorly defined; validation absent'; it is not 3 because no checkpoint or concrete step definition is present.	2 / 5
Progressive Disclosure	Section headers provide structure, but large capability/knowledge lists that belong in separate files are inlined, and the only reference (`resources/implementation-playbook.md`) is buried in 'Instructions' and points to a non-existent file, matching 'Some structure but could be better organized; references present but not clearly signaled; content that should be separate is inline'.	3 / 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) but relies on an aspirational verb and omits any explicit 'Use when' trigger guidance, capping completeness at 3. Concrete actions and natural trigger synonyms are thin.

Suggestions

Replace the aspirational 'Master Flutter development with...' with concrete actions, e.g. 'Build, test, and deploy Flutter apps across mobile, web, and desktop using Dart 3.'

Add an explicit trigger clause: 'Use when building or debugging Flutter apps, writing Dart 3 code, or deploying to multiple platforms.'

Include natural synonyms and file extensions users say, such as cross-platform, mobile app, .dart, and pubspec.

Dimension	Reasoning	Score
Specificity	The phrase "Master Flutter development with Dart 3, advanced widgets, and multi-platform deployment" names the domain and topics but uses the aspirational verb "Master" rather than concrete actions (e.g. extract, build, deploy), matching the anchor 'Names the domain but actions are minimal or generic'; it does not reach 3 because no 1-2 concrete actions are stated.	2 / 5
Completeness	It states a clear 'what' (master Flutter/Dart 3 with advanced widgets and multi-platform deployment) but includes no 'Use when...' clause or explicit trigger guidance, so per the rubric cap completeness cannot exceed 3; it is not 2 because the 'what' is concrete.	3 / 5
Trigger Term Quality	"Flutter development", "Dart 3", "advanced widgets", and "multi-platform deployment" are relevant natural terms, but coverage omits common variations/synonyms (e.g. cross-platform, mobile app, .dart, pubspec), matching 'Some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	Flutter/Dart 3 is a clear, distinct niche with minimal overlap risk, matching 'Mostly distinct; minor overlap risk'; it is not 5 because 'Master Flutter development' is broad and lacks the tightly scoped triggers of the 5-anchor example.	4 / 5
	Total	12 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/agentic-awesome-skills
Path: skills/flutter-expert/SKILL.md
Commit: b1aebac

Reviewed: ~18 hours ago

Table of Contents

Discovery Implementation Validation

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.