CtrlK
BlogDocsLog inGet started
Tessl Logo

dart

Dart integration. Manage data, records, and automate workflows. Use when the user wants to interact with Dart data.

56

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

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

The body is highly actionable with complete, executable CLI commands and a clear state-driven connection workflow. Its main weakness is a misleading opening paragraph that conflates the Dart programming language with the itsdart.com app and points to the wrong official docs.

Suggestions

Remove or replace the opening 'Dart is a client-optimized programming language...' paragraph and the dart.dev/guides link, which describe the wrong Dart and restate knowledge Claude already has.

Label the workflow steps consistently so the 'skip to Step 2' reference resolves to an actual numbered step.

Consider moving the connection-state handling and proxy options table into a reference file to keep SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

Mostly efficient CLI documentation, but the opening paragraph ('Dart is a client-optimized programming language... developed by Google') explains a concept Claude already knows and is unrelated to the itsdart.com integration, adding unnecessary padding.

3 / 5

Actionability

Copy-paste-ready commands cover the full common workflow — install, login (incl. headless), connection ensure, polling, action list/run, and proxy — with explicit flags and JSON examples.

5 / 5

Workflow Clarity

The connection flow has explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a polling feedback loop, but 'skip to Step 2' references a step that is never labeled, leaving a minor sequencing gap.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with no nested references and a single external docs link, though everything is inlined in one file with no bundle files to offload the longer state-handling and proxy-option material.

4 / 5

Total

16

/

20

Passed

Description

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

The description includes both a what and an explicit Use-when clause, but its actions are generic and its single keyword 'Dart' carries high collision risk with the Dart programming language. It is adequate but unspecific.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'Search, create, and update Dart tasks and records' instead of 'Manage data, records, and automate workflows'.

Disambiguate from the programming language, e.g. 'Use when the user wants to manage tasks or records in the Dart app (itsdart.com)'.

Add natural trigger phrases users would actually say, such as 'Dart tasks', 'Dart to-dos', or 'my Dart board'.

DimensionReasoningScore

Specificity

Names the Dart domain but the listed actions ('Manage data, records, and automate workflows') are generic verbs with no concrete operations, fitting the minimal/generic-actions anchor rather than the comprehensive one.

2 / 5

Completeness

It states what ('Manage data, records, and automate workflows') and has an explicit 'Use when the user wants to interact with Dart data' clause, but the 'when' is generic rather than a concrete trigger phrase.

4 / 5

Trigger Term Quality

The only natural keyword is 'Dart' (repeated as 'Dart data'); it has a relevant term but misses common variations or phrases a user would actually say, matching the some-relevant-keywords-but-missing-synonyms anchor.

3 / 5

Distinctiveness Conflict Risk

'Dart' names a specific app yet collides heavily with the well-known Dart programming language, so a user saying 'Dart' could plausibly trigger the wrong skill, fitting the somewhat-specific-but-still-overlap anchor.

3 / 5

Total

12

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-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.