CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

oma-translation

Translate or revise localized UI strings and prose while preserving meaning, terminology, placeholders, and structure.

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/oma-translation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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 dense, well-engineered process skill: explicit validation checkpoints, feedback loops, and scope guards for batch and diff-sync work, with concrete file paths and config hooks throughout. Its main costs are organizational redundancy across the Scheduling/Structural Flow/Logical Operations scaffolding and the absence of any worked example.

Suggestions

Collapse the redundant scaffolding: merge Goal/Intent signature/When-to use into one section, and let the References section carry what Dependencies currently repeats, saving ~20-30 lines.

Add one short worked example per mode (a placeholder-preserving UI-string translation and one evidence-backed review finding) to make the abstract rules concrete for the most common cases.

Flatten the style-skill indirection by naming the resolved skill directly in the References section (e.g. which `humanizer`/`humanize-korean` entry point `resources/style-skills.md` dispatches to).

DimensionReasoningScore

Conciseness

Individual lines are lean and imperative with zero padding about concepts Claude already knows, but the same information recurs across scaffolding sections — the Goal/Intent signature/When-to-use trio overlaps, the Canonical workflow path restates profile loading and style-route resolution from Structural Flow, and References repeats Dependencies. Mostly efficient but with organizational redundancy that could be tightened; not 4 because the duplication appears in several places rather than minor instances.

3 / 5

Actionability

For an instruction-only skill the guidance is highly concrete: exact resource paths, the BCP 47 subtag rule with a per-language profile table, `translation_voice` values from `.agents/oma-config.yaml`, an explicit protected-token list, and a failure/recovery table with named fallbacks. Not 5 because there are no worked examples (e.g. a placeholder-preserving translation or a sample review finding) to make the rules copy-paste concrete for common cases.

4 / 5

Workflow Clarity

The Canonical workflow path gives a clear 5-step sequence, Verification is an explicit always-run checklist plus a rubric check for substantive content, and the failure-and-recovery table provides feedback loops (placeholder mismatch → "Revise before emitting or applying a patch"; style skill unavailable → named fallback plus mandatory reporting). Batch and diff-sync work — the risky operations here — each carry their own validation and scope rules, so no cap applies.

5 / 5

Progressive Disclosure

A dedicated References section lists nine resources, each with an explicit load condition ("load for substantive content or review", "only when adding a profile", per-language profile table), which is well-signaled and mostly one level deep. Not 5 because the prose-style route is a genuine two-level hop (SKILL.md → `resources/style-skills.md` → resolved external style skill) and no bundle files were provided to verify the referenced paths exist; not 3 because the overview/references split itself is clean and easy to navigate.

4 / 5

Total

16

/

20

Passed

Description

66%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 concise, third-person description with a concrete action/scope statement and a clear preservation contract, but no explicit 'use when' trigger guidance, which caps its completeness and weakens trigger-term coverage. Adding a trigger clause naming localization, locale files, and translation review would lift it to the top band.

Suggestions

Append an explicit trigger clause, e.g. "Use when translating or reviewing locale files, UI strings, or documentation between languages, or when the user mentions localization, i18n, or a target locale."

Include natural synonyms users actually say — "localization", "i18n", "locale files", "review a translation" — to improve trigger-term coverage.

Mention the review/diff-sync output modes (e.g. "emit evidence-backed review findings or update target files after source changes") to close the coverage gap in what the skill does.

DimensionReasoningScore

Specificity

"Translate or revise localized UI strings and prose" names two concrete actions with clear objects, and "preserving meaning, terminology, placeholders, and structure" specifies an explicit preservation contract — denser than the anchor-3 example. Not 5 because several supported capabilities (review findings, glossary/style-guide creation, diff-sync of locale files) are absent, which is more than 'comprehensive coverage'.

4 / 5

Completeness

The 'what' is clear (translate/revise localized strings and prose with named invariants), but there is no 'Use when...' clause or equivalent explicit trigger guidance — the target domain only weakly implies 'when'. Per the judging guidelines, a missing explicit trigger clause caps completeness at 3; it earns the full 3 because the 'what' half is concrete and unambiguous.

3 / 5

Trigger Term Quality

Natural terms users would say are present: "Translate", "localized", "UI strings", "prose", "revise". Not 5 because common synonyms and trigger phrases like "localization", "i18n/l10n", "locale files", or "review a translation" are missing.

4 / 5

Distinctiveness Conflict Risk

"localized UI strings", "terminology", and "placeholders" anchor the description firmly in the translation niche with minimal conflict risk. Not 5 because "revise... prose" overlaps with general prose-editing/style skills and, without any 'when' triggers, the boundary with those skills is implicit rather than distinct.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

first-fluke/oh-my-agent

Path

.agents/skills/oma-translation/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.