dart-use-primary-constructors

Help users write syntactically and semantically correct primary constructors in Dart, and migrate/use the new constructor syntax, empty-body semicolon syntax, in-body initializer list syntax, and abbreviated concise constructor syntax.

Quality

71%

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-use-primary-constructors/SKILL.md

Quality

Content

68%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 content is actionable and well-structured with executable examples and a diagnostics table, but the refactoring workflows omit explicit validation/verification steps and some prose and version info could be trimmed or relocated.

Suggestions

Add an explicit validation checkpoint to the refactoring workflows (e.g., a final step 'Run `dart analyze` / `dart fix` to verify the migrated code compiles and has no new diagnostics').

Move or condense the version-requirements block into a clearly marked compatibility/deprecated section so time-sensitive version numbers do not dilute the core guidance.

Trim the restated prose under 2.2 (the paragraph re-explaining declaring vs. regular parameters) since the preceding code example already demonstrates it.

Dimension	Reasoning	Score
Conciseness	The body is code-dense and assumes Dart competence, but contains minor prose restatement (e.g., re-explaining declaring vs. regular parameters after the code example) and a version-numbers section that is time-sensitive and not placed in a deprecated/old-patterns section.	4 / 5
Actionability	Concrete, executable before/after Dart examples and an error/lint table with specific resolutions provide mostly copy-paste-ready guidance covering common cases, with only minor gaps.	4 / 5
Workflow Clarity	Workflow 5.1 and 5.2 provide a clear numbered sequence with before/after code, but lack an explicit validation checkpoint (e.g., 'run dart analyze' to confirm the refactor compiles); since refactoring user code is a modifying operation, workflow clarity is capped at 3.	3 / 5
Progressive Disclosure	No bundle files exist; the single file is organized into well-labeled sections (Overview, Syntax Reference, Semantics, Diagnostics, Workflows) and is appropriately self-contained for a focused single-feature skill, with only minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

75%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, distinct, and lists concrete capabilities with natural trigger terms, but it omits an explicit 'when to use' clause, which caps completeness. It is written in appropriate third-person voice.

Suggestions

Add an explicit 'Use when...' clause stating when to invoke this skill (e.g., when the user is writing or refactoring Dart classes with primary constructors or migrating to Dart 3.13+ constructor syntax).

Include a few more natural trigger synonyms such as 'declaring parameters' or 'concise constructor' to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'write syntactically and semantically correct primary constructors' plus migrate/use of four named syntax variants (new constructor, empty-body semicolon, in-body initializer list, abbreviated concise) — giving comprehensive coverage.	5 / 5
Completeness	The 'what' is clear and specific, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Natural terms 'primary constructors', 'Dart', and 'constructor syntax' appear and would be said by users, but synonym/file-extension coverage is limited for this narrow technical domain.	4 / 5
Distinctiveness Conflict Risk	'Primary constructors in Dart' is a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 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-use-primary-constructors/SKILL.md
Commit: c3c71cf

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