CtrlK
BlogDocsLog inGet started
Tessl Logo

definition-of-done

Mandatory checks to run before completing any task that touches md files or dart code in this repository.

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/.agents/skills/definition-of-done/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The body is a well-structured, highly actionable definition-of-done checklist with explicit validation criteria and a status-reporting format; its only weakness is minor verbosity in the output-formatting section.

Suggestions

Trim the output-formatting examples from five to two or three and fold the CRITICAL restatement into the format spec to tighten conciseness.

Drop the opening 'Use this skill to ensure...' line since it duplicates the frontmatter description.

DimensionReasoningScore

Conciseness

The step list is lean with concrete commands, but the intro reiterates the description and the output-formatting section carries five examples plus a CRITICAL restatement that could be tightened.

2 / 3

Actionability

Every step ships a copy-paste executable command (dart format, dart analyze --fatal-infos, dart run dart_code_linter:metrics, dart test) with explicit pass criteria.

3 / 3

Workflow Clarity

Eight steps are clearly sequenced, each with an explicit validation criterion, and the [x]/[ ] reporting format provides a feedback loop; the skill is itself the verification gate so the destructive-ops cap does not apply.

3 / 3

Progressive Disclosure

Under 50 lines, self-contained with no external references needed, and organized into clearly labeled sections (Mandatory Verification Steps, Output Formatting).

3 / 3

Total

11

/

12

Passed

Description

67%

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 concise and states both purpose and trigger condition, but its action language ('checks to run') is generic and trigger-term coverage is limited.

Suggestions

Name a few concrete checks in the description (e.g. 'run dart format, analyze, and test') to lift specificity from 2 to 3.

Add a 'Use when...' clause or natural trigger phrases like 'definition of done' and 'before requesting review' to improve trigger_term_quality and distinctiveness.

DimensionReasoningScore

Specificity

Names the domain ('md files or dart code') and a general action ('Mandatory checks to run before completing any task') but does not enumerate the specific checks (format, analyze, test), so it is not comprehensive.

2 / 3

Completeness

It answers both what ('Mandatory checks to run') and when ('before completing any task that touches md files or dart code in this repository') with an explicit trigger condition in a single sentence.

3 / 3

Trigger Term Quality

Relevant keywords like 'completing any task', 'md files', and 'dart code' appear, but common natural variations such as 'definition of done', 'before review', or 'quality checks' are missing.

2 / 3

Distinctiveness Conflict Risk

Scoping to md/dart files gives it a niche, but 'Mandatory checks to run before completing any task' is a pattern that could overlap with general task-completion or QA skills.

2 / 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.