dart-logic-patterns
Apply efficient algorithms, data structures, and Dart 3 pattern matching for clean business logic. Use when implementing search, sorting, debouncing, memoization, or exhaustive control flow in domain layers.
58
67%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/dart/dart-logic-patterns/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly communicates both what it does and when to use it. It uses third person voice, lists specific concrete capabilities, and includes natural trigger terms that developers would use. The Dart 3 specificity and focus on domain-layer algorithmic patterns make it distinctly identifiable among other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: search, sorting, debouncing, memoization, exhaustive control flow, and mentions specific technologies like Dart 3 pattern matching. | 3 / 3 |
Completeness | Clearly answers both 'what' (apply efficient algorithms, data structures, and Dart 3 pattern matching for clean business logic) and 'when' (explicit 'Use when' clause listing specific triggers: implementing search, sorting, debouncing, memoization, or exhaustive control flow in domain layers). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'search', 'sorting', 'debouncing', 'memoization', 'pattern matching', 'algorithms', 'data structures', 'business logic', 'domain layers'. These are terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of Dart 3 specificity, pattern matching, and the particular set of algorithmic concerns (debouncing, memoization, exhaustive control flow) creates a clear niche that is unlikely to conflict with other skills like general Dart UI skills or generic algorithm skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a high-level cheat sheet of concepts Claude already understands rather than actionable guidance for implementing algorithms in Dart/Flutter. It lacks any concrete code examples, which is a critical gap for a skill about algorithms and Dart 3 pattern matching. The content would benefit significantly from executable Dart code snippets demonstrating each pattern.
Suggestions
Add executable Dart 3 code examples for each pattern, especially switch expressions with exhaustive pattern matching, debouncing with Timer, and memoization implementations.
Remove explanations of basic concepts Claude already knows (what Big O is, what a Map/Set/List does) and replace with Dart-specific implementation details and gotchas.
Add a concrete example showing a before/after refactoring from nested if-else to Dart 3 sealed class + switch expression pattern matching.
Include a brief workflow or decision tree for choosing the right pattern (e.g., 'If caching pure function results → memoization; if delaying user input → debouncing') with concrete code for each path.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes explanations of concepts Claude already knows well (Big O notation, what Maps/Sets/Lists are, what debouncing/throttling mean). These descriptions add little value for an LLM that understands these fundamentals. | 2 / 3 |
Actionability | The skill is almost entirely descriptive with no executable code, no concrete examples, and no copy-paste ready snippets. Statements like 'Use switch expressions and exhaustive pattern matching' and 'Use for sorted lists' are vague directions rather than actionable instructions. A skill about algorithms and Dart 3 pattern matching should include actual code examples. | 1 / 3 |
Workflow Clarity | The content is organized into logical categories (Complexity Analysis, Logic Patterns, Search & Sort, Business Logic Organization), but there are no sequenced steps, no validation checkpoints, and no guidance on when or how to apply these patterns in a workflow. For a skill covering multiple patterns, some workflow guidance on selection and application would be expected. | 2 / 3 |
Progressive Disclosure | The content is organized into clear sections with headers, which is good. However, there are no references to external files for deeper dives, and some sections (like Pattern Matching or Memoization) could benefit from linking to detailed examples. No bundle files are provided, so there's no progressive structure beyond the single file. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
- Repository
- dhruvanbhalara/skills
- Commit
b2a9b39
- 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.