flutter-dart-code-review

Library-agnostic Flutter/Dart code review checklist covering widget best practices, state management patterns (BLoC, Riverpod, Provider, GetX, MobX, Signals), Dart idioms, performance, accessibility, security, and clean architecture. Use when reviewing Flutter or Dart code, whatever state management library the project uses.

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

The canonical home for this skill is tdg-personal/flutter-dart-code-review

Quality

Content

78%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 comprehensive, well-organized, and highly actionable review checklist with concrete rules, widgets, and commands. Main weaknesses are the monolithic single-file structure with no progressive disclosure and some redundant bullets across sections.

Suggestions

Split bulk reference material (the state-management quick-reference table, §10 package review, and per-library guidance) into one-level-deep reference files under references/ and link to them from SKILL.md to improve progressive disclosure.

De-duplicate recurring checks (print/logging, strict analyzer settings, deep-link validation, subscription disposal) so each appears once in its most relevant section.

Tighten the opening paragraph, which restates the frontmatter description, and consider adding a brief 'how to run this review' sequencing note with an explicit validation checkpoint at the end.

Dimension	Reasoning	Score
Conciseness	The body is a dense, mostly lean checklist that assumes Claude's competence (no basic concept explanations), but the intro paragraph restates the description and several bullets recur across sections (print/logging in §1 and §2, strict analyzer in §1/§2/§15, deep-link validation in §8 and §11).	4 / 5
Actionability	It names concrete, executable artifacts throughout — specific lint rules (prefer_const_constructors, unawaited_futures), exact analyzer settings (strict-casts: true), specific widgets (RepaintBoundary, MediaQuery.sizeOf(context)), commands (flutter pub outdated, flutter analyze), and one full sealed-class code example — giving actionable coverage of the common review cases.	5 / 5
Workflow Clarity	The 15 numbered sections provide a clear review sequence and the checklist items themselves act as validation, but there are no explicit validation checkpoints or fix-and-retry feedback loops (which the 5 anchor calls for).	4 / 5
Progressive Disclosure	Structure is good (numbered sections, headers, subsections) and navigable, but the skill is a ~430-line monolith with no bundle or reference files at all, and bulk material like the state-management quick-reference table, package-review detail, and per-library guidance could be split into one-level-deep reference files.	3 / 5
	Total	16 / 20 Passed

Description

87%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, well-scoped description that clearly states what the skill does and when to use it, with concrete trigger phrasing and a distinct Flutter/Dart niche. Minor gains possible by adding file-extension triggers like '.dart'.

Dimension	Reasoning	Score
Specificity	The description names the domain and lists several concrete coverage areas (widget best practices, state management patterns, Dart idioms, performance, accessibility, security, clean architecture) plus six specific libraries, which is comprehensive but framed as a single 'code review checklist' action rather than multiple discrete actions.	4 / 5
Completeness	It explicitly answers both what ('Library-agnostic Flutter/Dart code review checklist covering...') and when ('Use when reviewing Flutter or Dart code, whatever state management library the project uses') with concrete trigger phrases.	5 / 5
Trigger Term Quality	It includes natural terms users say ('Flutter', 'Dart', 'code review', 'reviewing Flutter or Dart code') and named libraries (BLoC, Riverpod, Provider, GetX, MobX, Signals), but omits common variations like the '.dart' file extension and 'widget'.	4 / 5
Distinctiveness Conflict Risk	It carves a clear Flutter/Dart code-review niche with distinct triggers and minimal overlap risk with non-Flutter skills.	5 / 5
	Total	18 / 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: affaan-m/ECC
Path: skills/flutter-dart-code-review/SKILL.md
Commit: 06c5e11

Reviewed: 3 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.