dart-build-cli-app

Entrypoint structure, exit codes, cross-platform scripts. Use when building command line utilities, scripts, or applications.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/dart-build-cli-app/SKILL.md

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.

The body is highly actionable and well-structured with explicit validation checkpoints in its workflow checklists; the main gap is mild verbosity in a few framing sentences and the absence of any external reference files.

Dimension	Reasoning	Score
Conciseness	Mostly lean bullet points with concrete commands and no beginner-concept padding; a few framing phrases like "Leverage the `io` and `stack_trace` packages to build robust, production-ready CLI tools" could be trimmed.	4 / 5
Actionability	Fully executable guidance throughout — specific commands (`dart create -t cli`, `dart compile exe ...`), named APIs (`ExitCode.success.code`, `Chain.capture()`), and two complete copy-paste Dart code examples covering common cases.	5 / 5
Workflow Clarity	The Workflows section provides sequenced checklists with explicit "Run validator ->" checkpoints and a fail-fast/non-zero-exit feedback loop for error recovery, matching the anchor for explicit validation steps.	5 / 5
Progressive Disclosure	A TOC, clear section headers, and a collapsible `<details>` block for cross-compilation give good navigation; no external bundle files exist, but all content is inline rather than split into reference files, so it is not a 5.	4 / 5
	Total	18 / 20 Passed

Description

61%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 a clear "Use when" trigger and natural keywords, but the "what" is a topic list rather than concrete actions and it omits "Dart", limiting specificity and distinctiveness.

Suggestions

Lead with concrete actions (e.g., "Scaffolds, parses arguments, compiles, and tests Dart CLI apps") instead of a topic list.

Add "Dart" and "CLI" to the trigger phrases so it surfaces for Dart-specific requests and avoids overlap with other languages' CLI skills.

Tighten the "when" clause to reference Dart-specific triggers like "dart create", "dart compile", or the `args` package.

Dimension	Reasoning	Score
Specificity	Names domains ("Entrypoint structure, exit codes, cross-platform scripts") but actions are minimal/generic — the only verb is the implied "building", with no concrete actions like "scaffold", "parse", or "compile".	2 / 5
Completeness	Both a "what" (entrypoint structure, exit codes, cross-platform scripts) and an explicit "Use when..." trigger are present; the "what" is a topic list rather than concrete actions, so it is not a 5.	4 / 5
Trigger Term Quality	"command line utilities, scripts, or applications" are natural user phrases, but "Dart" and the "CLI" abbreviation are missing, leaving a few common terms out.	4 / 5
Distinctiveness Conflict Risk	"building command line utilities, scripts, or applications" is fairly broad and, without mentioning Dart, could overlap with CLI-building skills for other languages.	3 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: flutter/agent-plugins
Path: skills/dart-build-cli-app/SKILL.md
Commit: 1412474

Reviewed: 3 hours ago

Table of Contents

Discovery Implementation Validation

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.