CtrlK
BlogDocsLog inGet started
Tessl Logo

valid

Reference fixture for dart_skills_lint. Demonstrates a SKILL.md that passes every default rule: hyphen-lowercase name matching the parent directory, a properly sized description, and no other frontmatter fields that would trigger the disallowed-field check.

63

Quality

76%

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 ./tool/dart_skills_lint/example/skills/valid/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise, actionable, and well-organized for a simple single-purpose fixture skill, with a concrete command and a built-in expected-output verification step.

DimensionReasoningScore

Conciseness

The body is lean and efficient with no padding or explanation of concepts Claude already knows, matching the every-token-earns-its-place anchor.

3 / 3

Actionability

It provides a complete, copy-paste-ready command plus expected output, fitting the fully-executable anchor rather than pseudocode.

3 / 3

Workflow Clarity

It is a simple single-step skill with an unambiguous action and an explicit expected-output checkpoint, qualifying for the simple-skill exception to score 3.

3 / 3

Progressive Disclosure

Under 50 lines with no external references needed and well-organized sections, meeting the small-skill exception that allows a score of 3 from organization alone.

3 / 3

Total

12

/

12

Passed

Description

52%

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 is specific and occupies a clear niche, but it is written for linter tooling rather than end users: it lacks natural trigger terms and any explicit 'when to use' guidance.

Suggestions

Add an explicit 'Use when...' clause so the 'when to use' trigger is stated rather than implied.

Replace linter-internal jargon ('disallowed-field check', 'hyphen-lowercase name matching the parent directory') with terms a user would naturally say when needing the skill.

DimensionReasoningScore

Specificity

Lists several specific concrete checks (hyphen-lowercase name, properly sized description, disallowed-field check), matching the multiple-specific-actions anchor rather than the 'some actions' level.

3 / 3

Completeness

Clearly states what the skill is (a lint fixture) but provides no explicit 'Use when...' trigger, so per the guidelines the missing-when caps completeness at 2 rather than 3.

2 / 3

Trigger Term Quality

Terms like 'disallowed-field check' and 'hyphen-lowercase name matching the parent directory' are linter-internal jargon a user would not naturally say, with no common natural-language variations present.

1 / 3

Distinctiveness Conflict Risk

It targets a clear, narrow niche (a dart_skills_lint validation fixture) and is unlikely to trigger for unrelated skills, fitting the distinct-niche anchor.

3 / 3

Total

9

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
flutter/agent-plugins
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.