CtrlK
BlogDocsLog inGet started
Tessl Logo

android-resources

Organize strings, drawables, and localization resources in Android projects. Use when managing Android resources, plurals, or adding multi-language support.

60

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

70%

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

The body is a well-organized, appropriately split standards overview that points cleanly to a single real reference file. The main weaknesses are minor internal redundancy and the absence of complete code examples in the body itself.

Suggestions

De-duplicate the plurals guidance: cover resources.getQuantityString once (e.g., in Strings & Localization) rather than restating it in Assets / Drawables, and remove the concatenation anti-pattern that repeats the Formatting bullet.

Add one short copy-paste code block in the body (e.g., a strings.xml snippet with a plural) so core guidance is executable without opening the reference.

Rename the reference link from the generic "XML Structure" to something matching implementation.md's actual content (strings, plurals, Compose usage, vector assets) to improve navigability.

DimensionReasoningScore

Conciseness

The bullets are lean and assume Claude's competence, but plurals guidance is duplicated ("Strings & Localization" and "Assets / Drawables" sections) and the "No String Concatenation" anti-pattern repeats the formatting bullet, so not every token earns its place.

2 / 3

Actionability

Concrete API references appear inline (stringResource, context.getString(...), resources.getQuantityString(...), values-night/), but the body lacks complete executable code blocks, deferring full copy-paste examples to the reference file.

2 / 3

Workflow Clarity

This is a simple standards skill under 50 lines with clear, well-organized sections (Strings & Localization, Assets / Drawables, Anti-Patterns, References) and no destructive multi-step workflow requiring validation checkpoints, so the simple-skills exception applies.

3 / 3

Progressive Disclosure

The body is a concise overview that signals one clearly labeled, one-level-deep reference ([XML Structure](references/implementation.md)), and that file exists in the bundle, matching the well-structured one-level-deep anchor.

3 / 3

Total

10

/

12

Passed

Description

75%

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 communicates a focused Android-resources niche with explicit what-and-when guidance. It is held back only by a single generic action verb and slightly incomplete trigger-term coverage.

DimensionReasoningScore

Specificity

"Organize strings, drawables, and localization resources" names the domain and concrete resource types but relies on a single generic verb ("Organize") rather than enumerating multiple distinct actions, matching the "names domain and some actions" anchor rather than the multi-action level 3.

2 / 3

Completeness

It states what ("Organize strings, drawables, and localization resources in Android projects") and explicitly when ("Use when managing Android resources, plurals, or adding multi-language support"), satisfying both halves with an explicit trigger clause.

3 / 3

Trigger Term Quality

Trigger terms "Android resources, plurals, or adding multi-language support" are relevant and natural, but common user phrasings such as "translate", "add a language", or "strings.xml" are missing, so coverage is partial rather than comprehensive.

2 / 3

Distinctiveness Conflict Risk

The Android-specific framing (strings.xml, drawables, plurals, localization) carves a clear niche with distinct triggers unlikely to fire for non-Android skills.

3 / 3

Total

10

/

12

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

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
HoangNguyen0403/agent-skills-standard
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.