CtrlK
BlogDocsLog inGet started
Tessl Logo

dart-logic-patterns

Use when organizing business logic, implementing algorithmic workflows, or applying Dart data structures and pattern matching.

56

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/dart/dart-logic-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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.

A compact, well-structured Dart logic reference that is easy to navigate. It over-explains a few basics and would be more actionable with short code examples for the named patterns.

Suggestions

Trim basic explanations of well-known concepts (e.g. what Map/Set/List do, the Big-O definition) to respect token budget and assume Claude's competence.

Add small executable Dart snippets for the highest-value patterns (e.g. a switch-expression with exhaustive matching, a memoization example using package:memoize) to lift actionability.

Optionally split guidance into a quick-reference vs. detailed-patterns structure if more examples are added, preserving the current lean overview.

DimensionReasoningScore

Conciseness

Mostly efficient bullet points, but lines like "`Map`: Fast key-based lookups" and "Understand the cost of your operations" explain basic data-structure and Big-O concepts Claude already knows, fitting the 'mostly efficient with some unnecessary explanation' anchor.

3 / 5

Actionability

Points to concrete APIs and packages ("Use Dart's built-in `list.sort()`", "Use `package:memoize`", "switch expressions and exhaustive pattern matching") but provides no executable examples, leaving the guidance incomplete despite being an instruction-oriented skill.

3 / 5

Workflow Clarity

Content is organized into clear thematic sections but presents a catalog of patterns rather than a sequenced process, and the multi-topic scope means the simple-skill exception does not raise it above 3.

3 / 5

Progressive Disclosure

At ~26 lines with no external references needed, the four well-organized sections (Complexity, Logic Patterns, Search & Sort, Business Logic) satisfy the under-50-line exception for progressive disclosure.

5 / 5

Total

14

/

20

Passed

Description

70%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.

A solid, third-person description with an explicit trigger clause and Dart-specific terms. It would benefit from separating concrete capabilities from the trigger phrasing and adding a few more natural synonyms.

DimensionReasoningScore

Specificity

Names the domain and several actions ("organizing business logic, implementing algorithmic workflows, or applying Dart data structures and pattern matching"), but the verbs are generic and coverage is not comprehensive, matching the 'names domain and 1-2 concrete actions' anchor.

3 / 5

Completeness

An explicit "Use when..." clause gives a clear trigger, and the listed actions convey what the skill does, but the 'what' is blended into the trigger rather than stated as distinct capabilities, so it is not a full 5.

4 / 5

Trigger Term Quality

Includes natural Dart-specific terms a user would say ("business logic", "pattern matching", "Dart data structures", "algorithmic workflows") with good coverage; a few common synonyms (e.g. "algorithms", "sorting") are missing, so it sits just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

The Dart-specific framing ("Dart data structures and pattern matching") carves a distinct niche with minimal conflict risk, though the broad "business logic" phrasing could overlap slightly with a general Dart or architecture skill.

4 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
dhruvanbhalara/skills
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.