CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dart-tooling

Use when diagnosing package dependency conflicts, running build_runner, or managing Dart SDK tooling commands.

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 dense, highly actionable Dart tooling skill with strong sequenced workflows, explicit validation checkpoints, and feedback loops. Its only weak spots are minor verbosity and a single-file structure that could offload some reference material.

Suggestions

Trim the brief rationale sentences (e.g. 'Transition test assertions... for more readable output' and the Git LFS elaboration) to lean out the body.

Consider moving the dart pub outdated column reference and the Git LFS note into a separate reference file to better fit progressive disclosure for a skill over 50 lines.

DimensionReasoningScore

Conciseness

Mostly commands, tables, and bullets with minimal concept-padding, but a few rationale sentences (e.g. the checks migration intro and the Git LFS elaboration) could be trimmed.

4 / 5

Actionability

Fully executable, copy-paste-ready commands throughout (dart analyze, dart fix --apply, dart pub upgrade --tighten, dart pub add dev:checks) plus concrete checks examples and a yaml override block covering the common cases.

5 / 5

Workflow Clarity

Each workflow is clearly sequenced with explicit verification: the Static Analysis flow ends in a Verify step, upgrading deps has analyze→fix and test→fix feedback loops, and the destructive lockfile removal warns against full deletion and verifies via dart pub deps.

5 / 5

Progressive Disclosure

Well-organized with a TOC and clear section headers and all content appropriately inline for a self-contained skill, but it exceeds 50 lines as a single dense file with no references, so a couple of sections (the pub outdated table, the Git LFS note) could be split into reference files.

4 / 5

Total

18

/

20

Passed

Description

67%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 concise, mostly specific Dart tooling description with an explicit trigger clause and a clear niche. It loses points for missing common trigger-term variations and for merging the 'what' and 'when' into one clause.

Suggestions

Add common trigger terms users actually say, e.g. 'pub get', 'pubspec', 'dart pub', 'dart analyze', so the skill surfaces for those phrasings.

Separate the capability statement from the trigger clause (e.g. 'Diagnose Dart package dependency conflicts, run build_runner, and manage Dart SDK tooling. Use when...') to explicitly answer both 'what' and 'when'.

Tighten the generic 'managing Dart SDK tooling commands' into specific concrete actions to reduce overlap risk and raise specificity.

DimensionReasoningScore

Specificity

Names several concrete actions ('diagnosing package dependency conflicts', 'running build_runner', 'managing Dart SDK tooling commands'); two are specific while the third is a generic catch-all, leaving minor gaps versus comprehensive coverage.

4 / 5

Completeness

An explicit 'Use when...' clause supplies the 'when' with three concrete triggers, and the named actions state the 'what', but the two are merged into a single clause rather than cleanly separated.

4 / 5

Trigger Term Quality

Contains relevant natural terms ('package dependency conflicts', 'build_runner') but misses common variations users say such as 'pub get', 'pubspec', 'dart pub', or 'dart analyze'.

3 / 5

Distinctiveness Conflict Risk

The Dart-specific niche and concrete triggers make it mostly distinct, though the broad phrase 'managing Dart SDK tooling commands' introduces minor overlap risk with related Dart skills.

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

dhruvanbhalara/skills

Path

skills/dart/dart-tooling/SKILL.md

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.