flutter-expert

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

1.11x

Quality

35%

Does it follow best practices?

Impact

77%

1.11x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/flutter-expert/SKILL.md

The canonical home for this skill is flutter-expert in sickn33/agentic-awesome-skills

Quality

Content

17%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 content is a verbose capability catalog that restates Flutter/Dart knowledge Claude already has, with no executable guidance, a generic high-level workflow, and a broken single reference. It needs concrete code, tightened prose, and real progressive-disclosure structure.

Suggestions

Add concrete, copy-paste-ready code examples for the common cases (e.g. a Riverpod provider, a platform channel, a widget test) instead of only listing capabilities.

Move the large capability/architecture/platform catalogs into separate reference files under references/ and link to them one level deep, fixing the dangling `resources/implementation-playbook.md` path.

Replace the generic Instructions and high-level Response Approach with a concrete, sequenced workflow with explicit validation checkpoints (e.g. analyze -> implement -> run flutter test -> profile in DevTools).

Dimension	Reasoning	Score
Conciseness	The ~190-line body is a padded catalog of capabilities, behavioral traits, and knowledge topics (e.g. 'Null safety mastery', 'Widget composition patterns') that Claude already knows, with several sections restating familiar Flutter/Dart concepts.	2 / 5
Actionability	There is no executable code or concrete commands anywhere; the body only describes capabilities ('Impeller rendering engine optimization', 'Widget rebuilds minimization with const constructors') and the Instructions are generic ('Apply relevant best practices and validate outcomes'), with the single reference path being broken.	1 / 5
Workflow Clarity	The 'Response Approach' section lists an 8-step rough sequence, but the steps are high-level and abstract ('Analyze requirements for optimal Flutter architecture') with many gaps and no validation checkpoints.	2 / 5
Progressive Disclosure	Nearly all content is inlined in one monolithic file — the large capability catalogs clearly belong in separate reference files — and the only reference (`resources/implementation-playbook.md`) does not exist, making it a dangling, broken pointer.	2 / 5
	Total	7 / 20 Passed

Description

53%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 clearly identifies a specific Flutter/Dart niche but is abstract rather than action-oriented and lacks an explicit 'Use when' trigger clause. It is distinct enough but would benefit from concrete actions and trigger phrases.

Suggestions

Replace the abstract verb 'Master' with concrete actions, e.g. 'Build, optimize, and deploy Flutter apps across mobile, web, and desktop.'

Add an explicit 'Use when' clause naming natural trigger phrases such as 'Flutter app', 'Dart 3', 'cross-platform', and platform names (iOS/Android).

Include common synonyms or file extensions users would say (e.g. 'Flutter', 'Dart', '.dart') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Flutter development') and several areas ('Dart 3, advanced widgets, and multi-platform deployment'), but 'Master' is an abstract verb and the rest are topics rather than concrete actions like build, deploy, or optimize.	3 / 5
Completeness	It gives a clear 'what' (master Flutter development with Dart 3, advanced widgets, multi-platform deployment) but has no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	'Flutter development' and 'Dart 3' are reasonably natural keywords, but common variations a user would actually say ('Flutter app', platform names like iOS/Android, 'cross-platform', '.dart') are missing.	3 / 5
Distinctiveness Conflict Risk	The Flutter/Dart 3 multi-platform niche is mostly distinct with clear triggers, with only minor overlap risk against a generic Dart or mobile-development skill.	4 / 5
	Total	13 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/flutter-expert/SKILL.md
Commit: 57c135b

Reviewed: 3 days 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.