android-resources
Organize strings, drawables, and localization resources in Android projects. Use when managing Android resources, plurals, or adding multi-language support.
66
81%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that concisely covers specific Android resource management capabilities, includes natural trigger terms developers would use, and clearly separates the 'what' from the 'when'. It uses proper third-person voice and is distinct enough to avoid conflicts with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Organize strings, drawables, and localization resources in Android projects.' These are concrete, domain-specific resource types rather than vague abstractions. | 3 / 3 |
Completeness | Clearly answers both what ('Organize strings, drawables, and localization resources in Android projects') and when ('Use when managing Android resources, plurals, or adding multi-language support') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'strings', 'drawables', 'localization', 'Android resources', 'plurals', 'multi-language support'. These cover common terms developers use when working with Android resource management. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Android resource management with distinct triggers like 'drawables', 'plurals', 'localization', and 'Android resources'. Unlikely to conflict with general coding skills or other platform-specific skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a competent but somewhat redundant Android resources standards skill. Its strengths are clear organization and specific API references, but it suffers from duplicated guidance (plurals mentioned twice, anti-patterns repeating earlier points) and lacks executable code examples that would make it truly actionable. The referenced implementation.md file is missing from the bundle, weakening the progressive disclosure.
Suggestions
Add complete, executable XML and Kotlin/Compose code examples — e.g., a full strings.xml entry with plurals and the corresponding Compose code using stringResource()
Remove the duplicated plurals guidance from the Assets/Drawables section and consolidate anti-patterns that repeat earlier guidelines
Provide the referenced `references/implementation.md` bundle file or remove the reference if it doesn't exist
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but has some redundancy — plurals guidance appears in both 'Strings & Localization' and 'Assets / Drawables' sections, and the anti-patterns section repeats points already made in the implementation guidelines (no concatenation, no hardcoded text). | 2 / 3 |
Actionability | Provides specific API calls and patterns (e.g., `context.getString(R.string.id, args)`, `resources.getQuantityString(...)`) but lacks executable code examples showing complete usage in context. The guidance is concrete but not copy-paste ready — no full XML snippets for strings.xml entries or Compose usage examples. | 2 / 3 |
Workflow Clarity | This is a standards/conventions skill rather than a multi-step workflow, so there are no destructive or batch operations requiring validation checkpoints. The single-purpose guidance is clearly organized into logical sections (strings, assets, anti-patterns) making it unambiguous what to do. | 3 / 3 |
Progressive Disclosure | References an external file `references/implementation.md` for XML structure details, which is good progressive disclosure, but no bundle files are provided to support this reference. The content is reasonably organized but the anti-patterns section duplicates inline content rather than adding new value. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
556618c
- 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.