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

57%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./mobile/flutter-project-starter/SKILL.md

Quality

Content

64%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a highly actionable Flutter scaffold skill with excellent, production-ready code examples covering the full stack from routing to testing. However, it's verbose for a skill file—the comprehensive examples would be better served by progressive disclosure into separate reference files. The workflow lacks explicit validation checkpoints for the code generation and build steps.

Suggestions

Add validation checkpoints after key steps: verify `flutter pub get` succeeded, check `build_runner` output for errors, validate generated files exist before proceeding

Split detailed code examples (BLoC patterns, repository implementations, tests) into separate reference files like PATTERNS.md or EXAMPLES.md, keeping SKILL.md as a concise overview

Add a troubleshooting section or error recovery guidance for common failures (build_runner conflicts, missing generated files, platform-specific setup issues)

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but includes some redundancy and could be tightened. The extensive code examples are valuable but some sections (like the full BLoC test example and multiple model examples) add length without proportional value for a scaffold skill.	2 / 3
Actionability	Excellent actionability with fully executable code examples throughout. The scaffold command, project structure, and all code patterns are copy-paste ready with complete, working implementations including imports and proper Dart syntax.	3 / 3
Workflow Clarity	The scaffold command sequence is clear, but lacks explicit validation checkpoints. No verification steps after running build_runner, no checks for successful dependency installation, and no guidance on what to do if code generation fails.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections, but everything is in one monolithic file. The extensive code examples for BLoC, repositories, and tests could be split into separate reference files, with SKILL.md providing just the essential scaffold and structure overview.	2 / 3
	Total	9 / 12 Passed

Description

50%

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 excels at technical specificity with concrete technologies and version numbers, making it highly distinctive. However, it critically lacks any 'Use when...' guidance, which would help Claude know when to select this skill. The trigger terms are heavily technical and may miss users who describe their needs in more natural language.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user wants to create a new Flutter app, start a mobile project, or mentions Flutter scaffolding/boilerplate.'

Include natural language trigger terms such as 'mobile app', 'cross-platform app', 'iOS and Android app', or 'new Flutter project' to capture users who don't use technical jargon.

Consider adding context about what 'production-ready' means (e.g., 'with proper architecture, testing setup, and CI/CD configuration') to clarify the skill's scope.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions and technologies: 'Scaffold a production-ready Flutter 3.27+ app' with specific tools including 'Material 3, BLoC or Riverpod for state management, go_router for navigation, platform channels, freezed for models, and Hive/Isar for local storage.'	3 / 3
Completeness	Describes WHAT it does (scaffold a Flutter app with specific technologies) but completely lacks any 'Use when...' clause or explicit trigger guidance for WHEN Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant technical keywords like 'Flutter', 'Dart', 'BLoC', 'Riverpod', 'go_router', 'freezed', 'Hive', 'Isar' that developers would use, but missing common natural language variations like 'mobile app', 'cross-platform', 'iOS', 'Android', or simpler terms users might say.	2 / 3
Distinctiveness Conflict Risk	Highly distinctive with specific version numbers (Flutter 3.27+, Dart 3.6+) and a unique combination of technologies (BLoC/Riverpod, go_router, freezed, Hive/Isar) that clearly defines its niche and is unlikely to conflict with other skills.	3 / 3
	Total	9 / 12 Passed

Validation

81%

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 — 9 / 11 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	9 / 11 Passed

Repository: achreftlili/deep-dev-skills
Commit: 181fcbc

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