flutter-development
Conocimiento especializado de Flutter para desarrollo de apps financieras. Incluye Clean Architecture, BLoC, Drift, fl_chart y speech_to_text. Usar cuando se trabaje con c\u00f3digo Flutter, arquitectura de la app, o implementaci\u00f3n de features.
71
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
67%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 effectively communicates the specialized domain (Flutter for financial apps) and includes an explicit 'Use when' clause, which is good for completeness. However, it lacks concrete action verbs describing what the skill actually does (e.g., 'implements charts', 'manages state', 'handles voice input') and could benefit from more natural trigger terms that users would actually say.
Suggestions
Add concrete action verbs describing capabilities, e.g., 'Implementa gráficos financieros, gestiona estado con BLoC, persiste datos con Drift, procesa entrada de voz'
Include more natural trigger terms users might say: 'mobile app', 'charts', 'database', 'voice recognition', '.dart files', 'state management'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Flutter for financial apps) and lists specific technologies (Clean Architecture, BLoC, Drift, fl_chart, speech_to_text), but doesn't describe concrete actions - only mentions 'implementación de features' which is vague. | 2 / 3 |
Completeness | Clearly answers both what (specialized Flutter knowledge for financial apps with specific technologies) and when ('Usar cuando se trabaje con código Flutter, arquitectura de la app, o implementación de features') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Flutter', 'arquitectura', and specific library names, but missing common variations users might say like 'mobile app', 'charts', 'database', 'voice input', or file extensions like '.dart'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'financial apps' niche and specific tech stack (BLoC, Drift, fl_chart) provide some distinction, but 'código Flutter' and 'implementación de features' are broad enough to potentially conflict with general Flutter or mobile development skills. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
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 comprehensive Flutter skill with excellent actionable code examples covering Clean Architecture, BLoC, Drift, fl_chart, speech-to-text, and Gemini AI integration. The main weaknesses are its length (could benefit from splitting into separate reference files) and lack of explicit multi-step workflows with validation checkpoints for complex operations like feature implementation or database migrations.
Suggestions
Split detailed code examples (BLoC patterns, Gemini integration, Drift queries) into separate reference files and keep SKILL.md as a concise overview with links
Add explicit workflow sections with validation checkpoints, e.g., 'Adding a new feature: 1. Create domain entity → 2. Define repository interface → 3. Implement data layer → 4. **Validate**: run tests → 5. Create BLoC'
Remove explanatory text about layer responsibilities that Claude already knows (e.g., 'Entities: Objetos puros sin dependencias externas') and keep only project-specific conventions
Add a 'Common Pitfalls' or 'Validation Checklist' section for database migrations and API integration to ensure error recovery is explicit
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary explanations (e.g., explaining what each layer does when Claude knows Clean Architecture). The folder structure and code examples are valuable, but sections like 'Capas y Responsabilidades' could be trimmed since Claude understands these patterns. | 2 / 3 |
Actionability | Excellent executable code throughout - complete BLoC implementations, Drift table definitions, fl_chart configurations, Gemini integration with retry logic, and testing examples. All code is copy-paste ready with proper imports and context. | 3 / 3 |
Workflow Clarity | While the architecture layers are well-defined, there's no explicit workflow for common multi-step operations like 'adding a new feature' or 'implementing voice-to-transaction flow'. Missing validation checkpoints for database migrations and no explicit error recovery sequences. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and headers, but it's a monolithic 500+ line file. References like 'Ver: `.claude/examples/gemini_expense_parser_example.dart`' suggest external files exist, but most detailed content (full BLoC examples, complete Gemini integration) is inline rather than linked to separate reference files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%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 (887 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 | |
- Reviewed
Table of Contents
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.