dart-resolve-package-conflicts

Workflow for fixing package version conflicts. Use this when `pub get` fails due to incompatible package versions.

Quality

80%

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-resolve-package-conflicts/SKILL.md

Quality

Content

85%

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

A tight, highly actionable skill body with concrete commands, complete before/after examples, and well-sequenced workflows that include validation feedback loops and a destructive-operation guard. The only mild weakness is a touch of conceptual explanation in Core Concepts that Claude already knows.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes competence (no definitions of Dart, semver, or libraries), but the 'Core Concepts' opening paragraph explains version-lock rationale and lockfile purpose that Claude largely already knows, fitting 'mostly efficient but includes some unnecessary explanation'.	2 / 3
Actionability	Concrete, executable commands appear throughout (`dart pub outdated`, `dart pub upgrade --tighten`, `dart pub get`) with specific edits ('change `^0.11.0` to `^0.12.1`') and complete input/output examples for both pubspec.yaml and pubspec.lock, matching 'fully executable code/commands; copy-paste ready'.	3 / 3
Workflow Clarity	Three workflows use sequenced task-progress checklists with explicit feedback loops (`dart analyze` -> review errors -> fix, `dart test` -> review failures -> fix, `dart pub deps` -> verify) and a critical 'NEVER delete pubspec.lock' guard, matching 'clear sequence with explicit validation steps; feedback loops for error recovery'.	3 / 3
Progressive Disclosure	A self-contained, well-organized SKILL.md with a Contents navigation and clear section headers; no bundle files exist so the single-file structure is appropriate, and there is no monolithic wall of text or nested references, meeting the top anchor for skills needing no external files.	3 / 3
	Total	11 / 12 Passed

Description

75%

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 clear, third-person description that explicitly answers both what it does and when to use it, with a well-scoped niche that won't conflict with other skills. It is held back only by a single high-level action verb and slightly limited trigger-term variation.

Suggestions

Add one or two concrete actions beyond 'fixing' (e.g., 'identifies the conflicting package, edits pubspec.yaml constraints, and surgically updates pubspec.lock') to reach the specificity top anchor.

Broaden trigger terms with natural phrasings users actually say, such as 'dependency conflict', 'version solver failure', or 'pubspec constraint error'.

Dimension	Reasoning	Score
Specificity	Names the domain and a single action ('fixing package version conflicts') but does not enumerate multiple concrete actions, matching the 'names domain and some actions but not comprehensive' anchor rather than the score-3 'lists multiple specific concrete actions'.	2 / 3
Completeness	It states what the skill does ('fixing package version conflicts') and provides an explicit 'Use this when...' trigger ('when `pub get` fails due to incompatible package versions'), satisfying both halves as required for the top anchor; it is not capped at 2 since the trigger clause is present.	3 / 3
Trigger Term Quality	Relevant natural terms appear ('pub get fails', 'incompatible package versions', 'package version conflicts') but common variations like 'dependency conflict' or 'pubspec' are missing, fitting 'some relevant keywords but missing common variations' below the broad score-3 coverage.	2 / 3
Distinctiveness Conflict Risk	The Dart/`pub` package-conflict niche with a `pub get` failure trigger is clearly distinct and unlikely to fire for unrelated skills, matching 'clear niche with distinct triggers; unlikely to conflict'.	3 / 3
	Total	10 / 12 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-resolve-package-conflicts/SKILL.md
Commit: 8aaa41d

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