check-downstream-consumers

Validates an in-progress PR or feature branch of dart_skills_lint against known downstream ecosystem consumers. Use when assessing breaking changes across external repositories during PR evaluation, testing migrations against the changelog, or determining necessary backwards compatibility shims.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

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 thorough, actionable workflow document with strong sequencing, validation checkpoints, and concrete commands for a destructive downstream-evaluation process. Mild verbosity from repeated commit-prohibition constraints and a missing referenced resource file are the only notable weaknesses.

Suggestions

Consolidate the 'Do Not Commit' constraint into the opening callout and reference it once rather than restating it in Step 3, Pathway B, and Section 4.

Provide the referenced resources/known_consumers.md (or a references/ bundle file) so the signaled navigation target actually exists.

Tighten the 'Discovering Local Checkouts' sub-list, which reads as procedural padding around a single 'ask before unbounded find' rule.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands and specific paths earning their place, but the 'Do Not Commit' constraint is restated across the callout, Step 3, Pathway B, and Section 4, and the local-checkout discovery prose is somewhat padded.	4 / 5
Actionability	Provides copy-paste-ready commands (`git status`, `dart test`, `flutter pub get`, `dart analyze --fatal-infos`, `git restore .`), an exact YAML snippet, and specific file paths with clearly-marked placeholders for variable values.	5 / 5
Workflow Clarity	A clear four-section numbered sequence with explicit validation checkpoints (verify tests pass, confirm public boundary resolution, re-run migrated suite), feedback loops via Pathway A/B and an iteration loop, and a cleanup step — properly guarding the destructive/batch downstream edits.	5 / 5
Progressive Disclosure	Well-organized into clearly headed sections with a one-level-deep, clearly signaled reference to resources/known_consumers.md, but no references/scripts/assets bundle exists and the referenced file is absent from the bundle, leaving a minor organization gap.	4 / 5
	Total	18 / 20 Passed

Description

92%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, third-person description that clearly states capability and trigger conditions with concrete, domain-specific actions. The only minor gap is trigger-term breadth leaning toward internal jargon rather than user-natural synonyms.

Dimension	Reasoning	Score
Specificity	Names the domain and lists multiple concrete actions — 'Validates an in-progress PR or feature branch', 'assessing breaking changes', 'testing migrations against the changelog', 'determining necessary backwards compatibility shims' — for comprehensive coverage.	5 / 5
Completeness	Explicitly answers both what ('Validates an in-progress PR or feature branch ... against known downstream ecosystem consumers') and when via a concrete 'Use when ...' clause listing PR evaluation, migration testing, and shim determination.	5 / 5
Trigger Term Quality	Includes natural terms a Dart-ecosystem reviewer would say ('PR', 'feature branch', 'breaking changes', 'changelog', 'migrations', 'backwards compatibility shims') but stays somewhat jargon-bound to dart_skills_lint, missing a few common synonyms.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — dart_skills_lint downstream-consumer validation during PR review — with distinct triggers and minimal overlap risk against generic linting or PR-review skills.	5 / 5
	Total	19 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
relative_links	Relative link issues: 2 missing	Warning

	Total	13 / 16 Passed

Repository: flutter/agent-plugins
Path: tool/dart_skills_lint/.agents/skills/check-downstream-consumers/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.