CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

airflow-translations

Add or update translations for the Apache Airflow UI. Guides through setting up locales, scaffolding translation files, translating with locale-specific guidelines, and validating results. Use when working with i18n tasks in airflow-core/src/airflow/ui/public/i18n/locales/.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

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 highly actionable, well-sequenced skill body built almost entirely from project-specific commands and conventions, with explicit validation checkpoints. Its weaknesses are minor: repeated statements of the locale-guideline-precedence rule and locale guideline files that are referenced but absent from the bundle.

Suggestions

State the locale-guideline precedence rule once (e.g., in 'Locale-Specific Guidelines') and reference it from the other sections instead of repeating it in 'Translating', 'Updating an Existing Translation', and the 'General Translation Rules' intro.

Ensure the referenced locales/*.md guideline files are actually included in the skill bundle (locales/ar.md through locales/zh-CN.md are linked in the table but not present), or note where they live so navigation does not break.

DimensionReasoningScore

Conciseness

Nearly all content is Airflow-specific knowledge Claude would not have (breeze commands, config file locations, plural-suffix setup, 'TODO: translate:' stub format), but the locale-guideline-precedence rule is repeated in at least four places ('Translating', 'Updating an Existing Translation', 'General Translation Rules', and 'Locale-Specific Guidelines'), which is trimmable redundancy. This fits 'efficient; minor instances of over-explanation that could be trimmed' rather than 'every token earns its place'.

4 / 5

Actionability

Fully executable throughout: 'mkdir -p airflow-core/src/airflow/ui/public/i18n/locales/<locale>/', exact config snippets per file, 'breeze ui check-translation-completeness --language <locale> --add-missing', the '--json' machine-readable variant, and 'prek run --from-ref main --hook-stage pre-commit'. The '<locale>' parameterization is appropriate and the scaffolded JSON example shows the exact expected output.

5 / 5

Workflow Clarity

Clear two-branch sequence (new vs. existing locale) with an explicit validation section stating expected outcomes ('0 missing, 0 TODOs, 0 unused, and 100% coverage'), a machine-readable check, and a feedback loop in the update path (check completeness → '--add-missing' / '--remove-unused' → re-validate). The destructive '--remove-unused' step is guarded by the completeness check, so the missing-validation cap does not apply.

5 / 5

Progressive Disclosure

The split is well designed: global rules stay inline while 20 per-locale guidelines are pointed to one level deep via a clearly signaled table. However, none of the referenced files (locales/ar.md ... locales/zh-TW.md) exist in the evaluated bundle — the only files present are SKILL.md, config.json, and rubrics — so navigation cannot be verified, which is more than the 'minor organization gaps' of a top score but better than unorganized or buried references.

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 description: concrete, third-person, with an explicit 'Use when' clause tied to a specific repository path. Trigger coverage is good but could add synonyms like 'localization' or 'l10n'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Add or update translations for the Apache Airflow UI' plus 'setting up locales, scaffolding translation files, translating with locale-specific guidelines, and validating results' — comprehensively covering both the add and update workflows.

5 / 5

Completeness

Explicitly answers both what ('Add or update translations... Guides through setting up locales, scaffolding... and validating results') and when ('Use when working with i18n tasks in airflow-core/src/airflow/ui/public/i18n/locales/'), with a concrete path-based trigger phrase.

5 / 5

Trigger Term Quality

Includes strong natural terms such as 'translations', 'i18n', 'locales', and 'Apache Airflow UI', which users would plausibly say. A few natural synonyms like 'localization', 'l10n', or language-specific phrasings are missing, matching the 'good coverage, a few natural terms missing' anchor rather than the comprehensive one.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — Apache Airflow UI translations — anchored by a repo-specific path trigger, so overlap with other skills is minimal. The description is in third person ('Guides through'), so no voice penalty applies.

5 / 5

Total

19

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 20 missing

Warning

Total

15

/

16

Passed

Repository

apache/airflow

Path

.agents/skills/airflow-translations/SKILL.md

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.