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.

64

Quality

77%

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%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 content is a tight, well-structured fixture description that provides an executable command and expected output with no padding. As a simple, single-purpose skill it fully meets the conciseness, actionability, workflow-clarity, and progressive-disclosure bars.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence ('This skill exists so the linter has a known-good fixture to validate against. It deliberately does nothing useful'); every line earns its place with no padding, matching the anchor-5 example.

5 / 5

Actionability

It gives a fully executable, copy-paste-ready command ('dart run dart_skills_lint --skill ./example/skills/valid') plus the expected output, covering the single common case at anchor 5.

5 / 5

Workflow Clarity

This is a simple single-purpose skill under 50 lines with one unambiguous action (run the lint command, expect 'Skill is valid.' and exit 0); the simple-skill exception applies and no destructive/batch validation cap is triggered.

5 / 5

Progressive Disclosure

Under 50 lines with no need for external references and a well-organized single heading, command block, and expected-output line; the simple-skill guideline allows a score of 5, and no bundle files exist to require deeper structure.

5 / 5

Total

20

/

20

Passed

Description

55%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 clearly conveys a narrow, distinct purpose as a linter reference fixture but is written for the tool rather than for user-facing triggers: it lacks any 'Use when' guidance and relies on technical jargon. Completeness and trigger-term quality are the weak points.

Suggestions

Add an explicit trigger clause, e.g. 'Use when validating dart_skills_lint rules against a known-good SKILL.md fixture.'

Include natural-language synonyms alongside the jargon so users can surface the skill without knowing the internal term 'disallowed-field check'.

Reframe the capability statement as actions ('Validates a SKILL.md against dart_skills_lint default rules') rather than only describing what the fixture demonstrates.

DimensionReasoningScore

Specificity

Names the domain and several concrete specifics ('hyphen-lowercase name matching the parent directory', 'properly sized description', 'no other frontmatter fields that would trigger the disallowed-field check'); sits at anchor 4 rather than 5 because it describes validation rules rather than a comprehensive set of capability actions.

4 / 5

Completeness

It has a clear 'what' (a reference fixture passing lint rules) but no 'Use when...' or equivalent trigger guidance, so per the rubric a missing 'when' clause caps completeness at 3; not 4 because there is no 'when' at all.

3 / 5

Trigger Term Quality

Terms are tool-specific jargon ('dart_skills_lint', 'SKILL.md', 'frontmatter', 'disallowed-field check') with no natural synonyms or variations a user would commonly say; matches anchor 2 (a couple of generic keywords, missing natural phrases) and is below 3 due to thin, jargon-only coverage.

2 / 5

Distinctiveness Conflict Risk

It occupies a clear, narrow niche (an internal lint fixture) with distinct triggers and minimal conflict risk against other skills, matching the anchor-5 example of a clear niche.

5 / 5

Total

14

/

20

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.