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

81%

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.

The body is highly actionable and well-structured with concrete commands, a complete config example, and workflows that include validation and feedback loops. Its only modest gap is slight conciseness padding and the absence of any split-out reference material.

Dimension	Reasoning	Score
Conciseness	Mostly lean bullet points with specific YAML keys and commands, assuming Claude's competence; minor trimmable padding such as the Contents TOC and purpose sentences like "Use this workflow to identify type-related bugs..." keep it just short of fully efficient.	4 / 5
Actionability	Fully executable guidance throughout: copy-paste-ready analysis_options.yaml, concrete CLI commands (`dart fix --dry-run`, `dart fix --apply`, `dart format .`), named MCP tool alternatives, and a runnable inline suppression example.	5 / 5
Workflow Clarity	Both workflows use numbered checkbox checklists; the fixes workflow includes explicit validation (dry-run preview, review) and a feedback loop ("Run the static analysis workflow to verify all diagnostics are resolved"), satisfying the batch-operation validation requirement.	5 / 5
Progressive Disclosure	Well-organized with a Contents TOC and clear sections (Configuration, Suppression, two Workflows, Examples) and appropriately self-contained for its length; no external references are used, which is fine but leaves it at good structure rather than the clearly-signaled-refs anchor of 5.	4 / 5
	Total	18 / 20 Passed

Description

73%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 is concrete, Dart-specific, and answers both what and when with an explicit Use-when clause. It is strong overall, with the only weakness being moderate action coverage rather than comprehensive listing.

Dimension	Reasoning	Score
Specificity	Names two concrete actions with their commands ("Execute `dart analyze` to identify warnings and errors" and "use `dart fix --apply` to automatically resolve mechanical lint issues"), matching the 1-2 concrete actions anchor; not comprehensive enough for a 4.	3 / 5
Completeness	Explicitly states both what (run dart analyze, apply dart fix) and when ("Use during development to ensure code quality and before committing changes"); the when is explicit but situational rather than trigger-phrase rich, so not a 5.	4 / 5
Trigger Term Quality	Good natural keyword coverage ("dart analyze", "lint issues", "warnings and errors", "code quality", "committing changes") that a Dart developer would say, though a few synonyms are missing so it falls short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	Tightly scoped to Dart tooling via `dart analyze` and `dart fix --apply`, giving it a clear niche with minimal overlap risk against non-Dart skills.	5 / 5
	Total	16 / 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: 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.