android-resources
Organize strings, drawables, and Localization resources on Android. Use when managing Android resources, drawables, or adding localization support. (triggers: strings.xml, **/*Screen.kt, stringResource, plurals, R.string)
84
80%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/android/android-resources/SKILL.mdQuality
Discovery
89%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 solid skill description with excellent trigger terms and completeness. The explicit 'Use when...' clause and parenthetical trigger list make it highly actionable for skill selection. The main weakness is that the 'what' portion could be more specific about the concrete actions performed beyond just 'organize'.
Suggestions
Replace the vague verb 'Organize' with more specific actions like 'Create, extract, rename, and restructure strings, drawables, and localization resources on Android' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Android resources) and some actions ('organize strings, drawables, and Localization resources'), but the actions are somewhat general—'organize' is vague and doesn't specify concrete operations like creating, extracting, renaming, or refactoring resources. | 2 / 3 |
Completeness | Clearly answers both 'what' (organize strings, drawables, and localization resources on Android) and 'when' (explicit 'Use when...' clause with triggers for managing Android resources, drawables, or adding localization support, plus specific trigger terms). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms that users would actually use: 'strings.xml', 'stringResource', 'plurals', 'R.string', 'drawables', 'localization', and the file pattern '**/*Screen.kt'. These cover both file-based and code-based triggers well. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Android resource management with distinct triggers like 'strings.xml', 'R.string', 'stringResource', and 'plurals' that are unlikely to conflict with other skills. The Android-specific file patterns and resource terminology create a clear niche. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a reasonable conventions/standards skill that covers Android resource management with specific API references and clear organization. Its main weaknesses are the lack of executable code examples (XML snippets, Compose examples) and some redundancy between the Implementation Guidelines and Anti-Patterns sections. The misplacement of the Plurals bullet under Assets/Drawables rather than Strings is a minor organizational issue.
Suggestions
Add concrete, copy-paste ready code examples: a strings.xml snippet with format args and plurals, and a Compose snippet using stringResource(R.string.*, args).
Move the 'Plurals' bullet from Assets/Drawables to the Strings & Localization section where it logically belongs.
Remove the Anti-Patterns section or consolidate it into the Implementation Guidelines, since both points are already covered above — this would improve conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but has some redundancy — the 'No String Concatenation' and 'No Hardcoded UI Text' anti-patterns repeat guidance already stated in the Implementation Guidelines section. The 'Plurals' bullet under Assets/Drawables seems misplaced and partially duplicates the Strings section. | 2 / 3 |
Actionability | Provides specific API calls and patterns (stringResource, getQuantityString, format args) but lacks executable code examples. The guidance is concrete enough to follow but would benefit from copy-paste ready XML snippets and Compose code blocks showing correct usage. | 2 / 3 |
Workflow Clarity | This is a standards/conventions skill rather than a multi-step process, so there's no workflow to sequence. The single-purpose guidance is clearly organized into logical sections (Strings, Assets, Anti-Patterns) making it unambiguous what to do. | 3 / 3 |
Progressive Disclosure | The skill is appropriately concise as an overview with a clear one-level-deep reference to 'references/implementation.md' for XML structure details. Content is well-split between the overview here and detailed implementation elsewhere. | 3 / 3 |
Total | 10 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
19a1140
- 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.