dart-fix-runtime-errors

Uses get_runtime_errors and lsp to fetch an active stack trace, locate the failing line, apply a fix, and verify resolution via hot_reload.

Quality

70%

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-fix-runtime-errors/SKILL.md

Quality

Content

81%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 a well-structured, highly actionable guide to resolving Dart static analysis errors, with executable commands, complete code examples, and a workflow that includes an explicit validation feedback loop. Its main weakness is mild over-explanation of basics and a complete mismatch with the frontmatter description, which promises a runtime-error workflow that the body does not deliver.

Dimension	Reasoning	Score
Conciseness	Section intros like 'Enforce Dart's sound type system to prevent runtime invalid states' and 'Distinguish between recoverable exceptions and unrecoverable errors' restate concepts Claude already knows, but the bulk is tight bullets and executable code, so it is mostly efficient with some trimmable explanation.	3 / 5
Actionability	Fully executable commands ('dart analyze . --fatal-infos', 'dart fix --apply', 'dart test') plus complete input/output code examples and concrete conditional logic per error type make this copy-paste ready and cover the common cases.	5 / 5
Workflow Clarity	The four-step workflow has a progress checklist and an explicit Step 4 feedback loop ('If dart analyze reports errors: Return to Step 3'), providing validation checkpoints and error-recovery guidance for the batch 'dart fix --apply' operation.	5 / 5
Progressive Disclosure	A Contents TOC and clearly separated Core Concepts, Workflows, and Examples sections give good structure with no nested references, but everything is inlined in a ~160-line single file rather than splitting the examples/reference material into separate files.	4 / 5
	Total	17 / 20 Passed

Description

58%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 specific and uses correct third-person voice, but it omits any explicit 'Use when...' trigger guidance, capping completeness, and leans on internal tool names rather than natural user phrases. It also describes a runtime-error workflow (get_runtime_errors/lsp/hot_reload) that does not match the body, which is actually about static analysis errors.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user hits a Dart runtime error, shares a stack trace, or asks to fix a failing line at runtime.'

Replace or supplement tool jargon (get_runtime_errors, lsp, hot_reload) with natural terms users actually say, like 'runtime error', 'stack trace', 'crash', and 'failing line'.

Reconcile the description with the body: either retarget the body to runtime errors (using get_runtime_errors/lsp/hot_reload) or rewrite the description to describe static-analysis resolution (dart analyze/dart fix).

Dimension	Reasoning	Score
Specificity	Quotes 'fetch an active stack trace, locate the failing line, apply a fix, and verify resolution via hot_reload' — four concrete actions with named tools, but 'apply a fix' is generic, so it sits at 'several specific actions; minor gaps' rather than comprehensive.	4 / 5
Completeness	The 'what' is clear (fetch stack trace, locate line, fix, verify), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	'runtime errors' and 'stack trace' are natural user phrases, but 'get_runtime_errors', 'lsp', and 'hot_reload' are tool/jargon names rather than things users say, and common synonyms are missing.	3 / 5
Distinctiveness Conflict Risk	Naming Dart-specific tooling (get_runtime_errors, lsp, hot_reload) and a runtime-error niche makes it mostly distinct, with only minor overlap risk against a generic Dart-fixing or static-analysis skill.	4 / 5
	Total	14 / 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-fix-runtime-errors/SKILL.md
Commit: c3c71cf

Reviewed: about 23 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.