flutter-expert

Master Flutter development with Dart 3, advanced widgets, and multi-platform deployment. Handles state management, animations, testing, and performance optimization for mobile, web, desktop, and embedded platforms. Use PROACTIVELY for Flutter architecture, UI implementation, or cross-platform features.

Quality

55%

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

35%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 verbose persona/capability catalog that spends most of its tokens enumerating technologies Claude already knows, with no executable examples and no progressive disclosure into reference files. It functions as a role description rather than actionable skill guidance.

Suggestions

Replace the capability enumeration with a few concrete, copy-paste-ready code patterns or commands for common Flutter tasks to raise actionability.

Move the long library/architecture catalogs into separate reference files (e.g., references/state-management.md, references/platform-channels.md) and link to them from a lean overview to improve conciseness and progressive disclosure.

Add explicit validation/verification checkpoints to the Response Approach workflow (e.g., 'run flutter analyze', 'run widget tests, fix failures, re-run') so multi-step work has feedback loops.

Dimension	Reasoning	Score
Conciseness	The ~190-line body is a long enumeration of library names and capability bullets (Riverpod, Bloc, GetX, Dio, etc.) much of which Claude already knows; it is noticeably padded with no code and minimal earned tokens, below the midpoint.	2 / 5
Actionability	Guidance is almost entirely abstract ('Apply relevant best practices and validate outcomes', 'Provide actionable steps and verification') with no executable code or commands; it lists technologies but gives only minimal concrete guidance on what to do.	2 / 5
Workflow Clarity	The 8-step Response Approach provides a rough sequence, but steps are high-level with no explicit validation checkpoints or feedback loops, matching the 'steps listed but checkpoints missing' anchor.	3 / 5
Progressive Disclosure	Headers give the document structure, but the large capability/knowledge lists that would belong in separate reference files are all inlined in a single SKILL.md with no external references or navigation pointers.	3 / 5
	Total	10 / 20 Passed

Description

75%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 is specific, mostly concise, and answers both what and when with explicit trigger guidance in third-person voice. It is a solid, well-targeted description that falls just short of the top anchor due to less granular action detail and missing synonym/extension coverage.

Suggestions

Add concrete trigger synonyms and file types users mention (e.g., '.dart', 'pubspec', 'widget tree', 'Flutter web') to lift trigger_term_quality.

Tighten the 'what' into a comma-separated list of discrete actions (e.g., 'Build, test, optimize, and deploy Flutter apps') to push specificity toward 5.

Dimension	Reasoning	Score
Specificity	Names the Flutter/Dart domain plus several concrete actions (state management, animations, testing, performance optimization, multi-platform deployment), with only minor coverage gaps; it stops short of the comprehensive, fine-grained action list of a 5.	4 / 5
Completeness	Both 'what' (handles state management, animations, testing, performance) and 'when' ('Use PROACTIVELY for Flutter architecture, UI implementation, or cross-platform features') are present and explicit; the 'when' could be more specific with concrete trigger phrases, keeping it just below 5.	4 / 5
Trigger Term Quality	Covers natural terms users would say (Flutter architecture, UI implementation, cross-platform features, state management) with good keyword coverage, though it lacks synonyms and file extensions that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	The Flutter/Dart niche is clearly distinct with specific triggers, but 'cross-platform features' and generic UI terms create minor overlap risk with other mobile/cross-platform skills.	4 / 5
	Total	16 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/flutter-expert/SKILL.md
Commit: 3eff4af

Reviewed: about 4 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.