flutter-expert
tessl install github:jeffallan/claude-skills --skill flutter-expertUse when building cross-platform applications with Flutter 3+ and Dart. Invoke for widget development, Riverpod/Bloc state management, GoRouter navigation, platform-specific implementations, performance optimization.
Review Score
70%
Validation Score
12/16
Implementation Score
42%
Activation Score
100%
Generated
Validation
Total
12/16Score
Passed| Criteria | Score |
|---|---|
metadata_version | 'metadata' field is not a dictionary |
license_field | 'license' field is missing |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata |
body_examples | No examples detected (no code fences and no 'Example' wording) |
Implementation
Suggestions 4
Score
42%Overall Assessment
This skill has strong organizational structure with good progressive disclosure through its reference table, but critically lacks actionable code examples. The constraints are useful but abstract - they tell Claude what to do without showing how. The workflow is clear but missing validation steps important for mobile development.
Suggestions
- Add executable Dart code examples for key patterns: a const-optimized widget, a Riverpod provider definition, and a GoRouter configuration snippet
- Include a concrete example showing the difference between correct (Consumer/ConsumerWidget) and incorrect (setState) state management approaches
- Add validation checkpoints to the workflow, such as 'Run flutter analyze after Setup' and 'Verify hot reload works after State changes'
- Remove the Role Definition section - Claude doesn't need persona framing about years of experience
| Dimension | Score | Reasoning |
|---|---|---|
Conciseness | 2/3 | The skill is reasonably efficient but includes some unnecessary content like the 'Role Definition' section explaining experience years and the 'Related Skills' section. The core workflow and constraints are appropriately brief. |
Actionability | 1/3 | The skill lacks any concrete, executable code examples. It describes what to do ('Use const constructors', 'Implement proper keys') but provides no actual Flutter/Dart code snippets that Claude could reference or adapt. |
Workflow Clarity | 2/3 | The 5-step core workflow provides a clear sequence but lacks validation checkpoints or feedback loops. For a framework involving builds and state management, there's no guidance on verifying each step succeeded before proceeding. |
Progressive Disclosure | 3/3 | Excellent structure with a clear overview and well-organized reference table pointing to specific topic files. The 'Load When' column provides clear signals for when to access each reference, and references are one level deep. |
Activation
Score
100%Overall Assessment
This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities, uses natural developer terminology, explicitly states both what it does and when to use it, and has clear distinctive triggers that prevent conflicts with other skills.
| Dimension | Score | Reasoning |
|---|---|---|
Specificity | 3/3 | Lists multiple specific concrete actions: 'widget development, Riverpod/Bloc state management, GoRouter navigation, platform-specific implementations, performance optimization' - these are concrete, actionable capabilities. |
Completeness | 3/3 | Explicitly answers both what ('widget development, Riverpod/Bloc state management, GoRouter navigation...') and when ('Use when building cross-platform applications with Flutter 3+ and Dart. Invoke for...'). |
Trigger Term Quality | 3/3 | Excellent coverage of natural terms users would say: 'Flutter', 'Dart', 'widget', 'Riverpod', 'Bloc', 'GoRouter', 'cross-platform' - these are exactly the keywords developers would use when seeking Flutter help. |
Distinctiveness Conflict Risk | 3/3 | Highly distinctive with Flutter/Dart-specific terminology (Riverpod, Bloc, GoRouter) that clearly separates it from other mobile development or general programming skills. |