dart-use-doc-examples

How to inject external code examples into Dartdoc using the {@example} directive, and how to filter those files using #hide, #region, and #endregion tags.

Quality

68%

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-doc-examples/SKILL.md

Quality

Content

82%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 concrete, executable examples and a reasonable verification step. It is efficient though slightly verbose in a few illustrative spots, and validation could be framed more explicitly.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and assumes Claude's knowledge of Dart/Dartdoc, with only minor instances that could be trimmed (e.g., the inline bad-vs-good example block restates the directive rationale).	4 / 5
Actionability	Provides copy-paste-ready, executable guidance: exact directive syntax, region-wrapped Dart code, a #hide example, and concrete path-resolution examples covering the common cases.	5 / 5
Workflow Clarity	A clear sequence runs from extracting examples to injecting, filtering via regions/#hide, and verifying with 'dart analyze' (plus optional 'dart doc' with named error signals); validation is present but lightly framed, leaving a minor gap.	4 / 5
Progressive Disclosure	Content is well-organized with a table of contents and clearly delineated sections for a single self-contained topic; no external bundle files exist or are needed, with only minor verbosity for one topic.	4 / 5
	Total	17 / 20 Passed

Description

53%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 clearly states what the skill does within a distinct Dartdoc niche, but it lacks an explicit 'when to use' trigger clause and relies on fairly technical jargon, limiting trigger quality and completeness.

Suggestions

Add a 'Use when ...' clause naming natural trigger phrases such as 'writing Dartdoc examples', 'injecting code examples into Dart documentation', or 'filtering Dartdoc example files'.

Soften the jargon with at least one user-natural synonym (e.g., 'Dart documentation examples') alongside '{@example} directive'.

Optionally list an additional concrete action (e.g., 'resolve package-root and relative example paths') to broaden capability coverage.

Dimension	Reasoning	Score
Specificity	Names the Dartdoc domain and two concrete actions ('inject external code examples ... using the {@example} directive' and 'filter those files using #hide, #region, and #endregion tags'), but coverage is limited to those two actions rather than comprehensive.	3 / 5
Completeness	The 'what' is clearly stated, but there is no 'Use when...' or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Relevant technical terms like 'Dartdoc', '{@example}', '#hide', '#region', and '#endregion' are present, but it leans on jargon and omits common phrasings or synonyms a user might naturally say.	3 / 5
Distinctiveness Conflict Risk	Targets a distinct Dartdoc-specific niche (the {@example} directive and its marker tags) with low conflict risk, with only minor overlap against general Dart documentation skills.	4 / 5
	Total	13 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: flutter/agent-plugins
Path: skills/dart-use-doc-examples/SKILL.md
Commit: 1412474

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