CtrlK
BlogDocsLog inGet started
Tessl Logo

i18n-resource-audit

Audit M3UAndroid localization resources for missing default strings, placeholder consistency, key naming, hardcoded user text, fallback behavior, and locale safety.

66

Quality

81%

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

92%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 concise, well-structured audit skill with a clear process, explicit validation checkpoint, and well-signaled external references; the main gap is that audit steps are guidance rather than executable code.

DimensionReasoningScore

Conciseness

Lean and efficient throughout; no over-explanation of concepts Claude already knows, and every section earns its tokens.

5 / 5

Actionability

Concrete audit checks and an executable validation command, but the audit process steps are guidance rather than copy-paste-ready code, leaving minor gaps.

4 / 5

Workflow Clarity

Clear numbered process with an explicit validation checkpoint and a feedback loop ('if unavailable, state resource-risk remaining').

5 / 5

Progressive Disclosure

Under 50 lines with well-organized sections and one-level-deep references (AGENTS.md, playbook, default/locale resources); no bundle files, so the simple-skill exception applies.

5 / 5

Total

19

/

20

Passed

Description

70%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 specific, well-scoped description that lists concrete audit actions, but it omits an explicit 'Use when...' trigger clause, which caps completeness at 3.

Suggestions

Add an explicit 'Use when...' clause naming the natural triggers (e.g., when a task touches string resources, plurals, arrays, locale files, or resource key renames).

Include common synonyms/extensions users might say (e.g., 'translations', 'strings.xml', 'missing translations') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists several concrete audit actions (missing default strings, placeholder consistency, key naming, hardcoded user text, fallback behavior, locale safety), with only minor coverage gaps.

4 / 5

Completeness

Clear 'what' but no explicit 'Use when...' trigger clause, so per the rubric guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

Good natural keywords (localization, i18n, locale, strings, resources) though a few common synonyms or extensions are absent; project name M3UAndroid scopes it well.

4 / 5

Distinctiveness Conflict Risk

Scoped to M3UAndroid localization auditing with distinct triggers, giving it a clear niche and minimal conflict risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
oxyroid/M3UAndroid
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.