android-resources
Organize strings, drawables, and localization resources in Android projects. Use when managing Android resources, plurals, or adding multi-language support.
81
78%
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
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 clearly identifies its niche (Android resource management), lists specific concrete capabilities, and provides explicit 'Use when' trigger guidance with natural keywords. It follows the third-person voice convention and is concise without being vague. Minor improvement could include mentioning file types like strings.xml or res/ directory for additional trigger coverage.
| 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 strong natural keywords users would say: 'strings', 'drawables', 'localization', 'Android resources', 'plurals', 'multi-language support'. These cover common terms Android developers use when dealing with resource management. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Android resource management with distinct triggers like 'drawables', 'plurals', 'localization resources', and 'Android projects'. Unlikely to conflict with general coding skills or other platform-specific skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%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 standards-oriented skill that covers key Android resource management patterns concisely with appropriate progressive disclosure. Its main weaknesses are the lack of executable code examples (XML snippets, Compose usage) and some redundancy between the guidelines and anti-patterns sections. Adding concrete examples and removing duplication would significantly improve it.
Suggestions
Add concrete XML snippets showing a properly formatted strings.xml entry with format args and a plurals definition, making the guidance copy-paste ready.
Add a brief Compose code example showing `stringResource(R.string.greeting, userName)` usage to make the Compose guidance actionable.
Remove the Anti-Patterns section or consolidate it, as both anti-patterns are already covered in the Implementation Guidelines — 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 Strings & Localization section. The 'Plurals' bullet is oddly placed under Assets/Drawables. Overall reasonably tight but could be tightened. | 2 / 3 |
Actionability | Provides specific API calls and patterns (e.g., `context.getString(R.string.id, args)`, `resources.getQuantityString(...)`) which is helpful, but lacks executable code examples showing complete usage in context. The guidance is concrete but not copy-paste ready — no XML snippets for strings.xml, no Compose code examples. | 2 / 3 |
Workflow Clarity | This is more of a standards/guidelines skill than a multi-step workflow, so explicit sequencing is less critical. However, there's no guidance on how to add a new language, no process for verifying localization completeness, and no validation steps for ensuring resource parity with iOS. For a standards skill, the organization is adequate but lacks verification guidance. | 2 / 3 |
Progressive Disclosure | The skill is concise with a clear overview structure and a single well-signaled reference to implementation details in a separate file. Content is appropriately split — high-level standards here, XML structure details in references/implementation.md. One level deep, clearly navigable. | 3 / 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
4c72e76
- 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.