CtrlK
BlogDocsLog inGet started
Tessl Logo

flutter-setup-localization

Add `flutter_localizations` and `intl` dependencies, enable "generate true" in `pubspec.yaml`, and create an `l10n.yaml` configuration file. Use when initializing localization support for a new Flutter project.

74

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The skill body is lean, highly actionable, and clearly sequenced with an explicit feedback loop for ARB error recovery. It is well-organized with a TOC and needs no external references given its scope.

DimensionReasoningScore

Conciseness

The body is lean and code/command-driven with short framing sentences; the brief Core Concepts paragraph is tight rather than padded, and every section earns its place without over-explaining concepts Claude already knows.

3 / 3

Actionability

Provides fully executable, copy-paste-ready guidance: shell commands (flutter pub add), yaml configs, and a complete Dart widget implementation, matching the anchor for fully executable code/commands.

3 / 3

Workflow Clarity

Setup and implementation workflows are sequenced with a tracked checklist, numbered steps, and an explicit feedback loop (Run validator -> review terminal output for ARB syntax errors -> fix missing commas or mismatched placeholders -> re-run flutter pub get).

3 / 3

Progressive Disclosure

Well-organized single-file skill with a Contents TOC and clearly delineated sections; no bundle files exist and no nested references are present, so the self-contained structure navigates cleanly.

3 / 3

Total

12

/

12

Passed

Description

85%

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 and complete with an explicit Use-when trigger and a clear Flutter-localization niche. Its main weakness is trigger-term coverage, which omits common synonyms like i18n/l10n/translations that users may say.

Suggestions

Broaden the Use-when clause to include natural synonyms users say, e.g. "Use when initializing localization, internationalization (i18n/l10n), or multi-language/translation support for a new Flutter project."

Keep the concrete actions as written — they already anchor specificity well.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — adding flutter_localizations and intl dependencies, enabling generate true in pubspec.yaml, and creating an l10n.yaml file — matching the anchor for several specific concrete actions rather than merely naming a domain.

3 / 3

Completeness

Explicitly states what it does (add deps, enable generate, create l10n.yaml) and when to use it via "Use when initializing localization support for a new Flutter project", satisfying both what and when with an explicit trigger.

3 / 3

Trigger Term Quality

"localization support" and "new Flutter project" are relevant natural terms, but common variations users say (i18n, l10n, translations, multilingual) are missing, fitting the anchor for some relevant keywords but missing common variations.

2 / 3

Distinctiveness Conflict Risk

The Flutter localization-setup niche with package and file specifics (flutter_localizations, intl, l10n.yaml) is distinct and unlikely to trigger for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
flutter/agent-plugins
Reviewed

Table of Contents

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.