dart-run-static-analysis

Execute `dart analyze` to identify warnings and errors, and use `dart fix --apply` to automatically resolve mechanical lint issues. Use during development to ensure code quality and before committing changes.

Quality

83%

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

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.

A well-structured, highly actionable skill body: concrete commands, complete examples, and checklisted workflows with proper dry-run and re-verification validation for the batch fix operation. The only notable inefficiency is mild duplication between the Analysis Configuration bullets and the YAML example.

Dimension	Reasoning	Score
Conciseness	The body uses compact, fact-dense bullets with no prose padding, but the Examples section re-states rules already covered in 'Analysis Configuration' and the suppression section explains ignore-comment syntax Claude largely knows, fitting anchor 4 (efficient with minor over-explanation that could be trimmed) rather than anchor 5's every-token-earns-its-place.	4 / 5
Actionability	Commands are copy-paste ready throughout ('dart analyze <target_directory>', 'dart fix --dry-run', 'dart fix --apply', 'dart format .', '--fatal-infos') and the two complete code examples (analysis_options.yaml and inline suppression) cover the common cases, matching anchor 5.	5 / 5
Workflow Clarity	Both workflows use explicit Task Progress checklists, and the batch-fix workflow includes a dry-run preview, a review-before-apply checkpoint, and a re-verification loop (step 6 re-runs analysis), matching anchor 5's explicit validation steps and feedback loops; the destructive/batch cap does not apply since validation is present.	5 / 5
Progressive Disclosure	The ~100-line body is self-contained, well-sectioned, and fronted by a Contents TOC, but it exceeds the under-50-line simple-skill exception and includes no bundle references to split content across, fitting anchor 4 (good structure, most content appropriately placed, minor organization gaps) rather than anchor 5's reference-based navigation.	4 / 5
	Total	18 / 20 Passed

Description

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

A strong description with two concrete, tool-named actions and an explicit 'when' clause. Its main weaknesses are modest action coverage and missing common trigger synonyms like 'static analysis' or 'linting'.

Suggestions

Add natural trigger synonyms such as 'static analysis', 'run the analyzer', or 'linting' so the description matches how users actually phrase the request.

Broaden action coverage slightly (e.g., mention configuring the analyzer via analysis_options.yaml or formatting with `dart format`) to move from two actions toward comprehensive coverage.

Tighten the 'when' clause by leading with the most concrete triggers (e.g., 'Use when Dart code has analyzer warnings, lints, or errors, or before committing changes').

Dimension	Reasoning	Score
Specificity	Lists two fully concrete, tool-level actions ('Execute `dart analyze` to identify warnings and errors', 'use `dart fix --apply` to automatically resolve mechanical lint issues'), but coverage stops at two actions with minor gaps (e.g., no formatting or config validation), matching anchor 4 rather than the comprehensive multi-action anchor 5.	4 / 5
Completeness	Both 'what' (two named commands) and 'when' ('Use during development to ensure code quality and before committing changes') are explicit, but 'during development to ensure code quality' is somewhat generic alongside the concrete commit trigger, fitting anchor 4 ('when could be more explicit or specific') rather than anchor 5's fully concrete trigger phrases.	4 / 5
Trigger Term Quality	Natural phrases like 'dart analyze', 'warnings and errors', 'lint issues', and 'before committing changes' are present, but common variations such as 'static analysis', 'analyzer', or 'linting' are missing, matching anchor 4 (good coverage, a few natural terms missing) rather than anchor 5's synonym breadth.	4 / 5
Distinctiveness Conflict Risk	The 'dart analyze' / 'dart fix --apply' pairing carves out a clear niche with distinct tool-specific triggers, giving minimal conflict risk with other skills, which matches anchor 5.	5 / 5
	Total	17 / 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-run-static-analysis/SKILL.md
Commit: 8da8c54

Reviewed: 5 days 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.