flutter-project-starter

Scaffold a production-ready Flutter 3.27+ app with Dart 3.6+, Material 3, BLoC or Riverpod for state management, go_router for navigation, platform channels, freezed for models, and Hive/Isar for local storage.

Quality

73%

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 ./mobile/flutter-project-starter/SKILL.md

Quality

Content

72%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 highly actionable with executable code and commands, but the scaffold workflow lacks an explicit validation checkpoint and no content is offloaded to reference files. Adding a verify step and splitting detailed examples into reference files would improve the score.

Suggestions

Add an explicit validation step at the end of the Scaffold Command workflow, e.g. 'After codegen, verify: flutter analyze && flutter test', to provide a feedback loop for the batch setup.

Move detailed per-file code examples (theme, router, BLoC, repository, platform channel) into reference files under references/ and keep SKILL.md as an overview with signaled links.

Trim Integration Notes prose that restates library capabilities Claude already knows to improve conciseness.

Dimension	Reasoning	Score
Conciseness	Mostly efficient code with little concept-padding, but the ~660-line body includes full code listings and prose (Key Conventions, Integration Notes) that could be trimmed slightly; minor over-explanation.	4 / 5
Actionability	Fully executable copy-paste code and specific commands throughout ('flutter pub add ...', 'dart run build_runner build --delete-conflicting-outputs'), with complete examples covering the common cases.	5 / 5
Workflow Clarity	The scaffold command section sequences setup, but the batch scaffold + codegen workflow has no inline validation checkpoint (e.g. 'flutter analyze'/'flutter test' as a verify step); per the feedback-loops guidance, a batch operation without validation caps workflow clarity at 3.	3 / 5
Progressive Disclosure	All content is inline in a single long file with good section headers but no bundle/reference files exist to offload detailed code listings, so it is not split across files one level deep.	3 / 5
	Total	15 / 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, technically precise, and clearly distinct, but it omits an explicit 'Use when...' trigger clause, which caps completeness. Adding a concrete usage-trigger sentence would raise it.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when scaffolding a new production Flutter app or when the user asks to set up a Flutter project with BLoC/Riverpod, go_router, and freezed.'

Include a few broader synonyms users might say ('Flutter app', 'mobile app project', 'Dart project') to widen natural trigger coverage.

Keep the third-person voice (already correct) but tighten the version list into the prerequisites rather than the trigger phrase.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions and technologies ('Scaffold a production-ready Flutter 3.27+ app', 'BLoC or Riverpod for state management', 'go_router for navigation', 'freezed for models', 'Hive/Isar for local storage'), giving comprehensive coverage of the scaffold.	5 / 5
Completeness	Has a clear 'what' but no explicit 'Use when...' trigger clause; per the guidelines, a missing explicit trigger guidance caps completeness at 3.	3 / 5
Trigger Term Quality	Natural stack terms a Flutter developer would say are present (Flutter, BLoC/Riverpod, go_router, freezed, Hive/Isar), but it lacks broader synonyms or generic phrases like 'mobile app' or 'build app'.	4 / 5
Distinctiveness Conflict Risk	Clearly niche and Flutter-specific with named technologies, minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (672 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: achreftlili/deep-dev-skills
Path: mobile/flutter-project-starter/SKILL.md
Commit: 181fcbc

Reviewed: 1 day 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.