Tessl • The package manager for agent skills

SkillPublic

android-resources

Organize Android strings, drawables, fonts, themes, localization, and concrete resource-backed Compose values such as MaterialTheme colors. Use for resource declarations and their direct UI lookup; defer design-system token architecture, network image loading, lint-rule configuration, and general Compose implementation.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%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 compact, well-structured standards skill with concrete API-level guidance and correct one-level progressive disclosure to a real reference file. Its weaknesses are minor: duplicated bullets, a misplaced plurals item under Assets/Drawables, and two grammatical errors that blur two key rules.

Suggestions

Fix the broken sentences: "All UI text must in strings.xml" (Strings & Localization) and "must defined in strings.xml" (Anti-Patterns).

Remove the duplicate "Plurals" bullet from the Assets / Drawables section, or move it into Strings & Localization next to the related formatting guidance.

Rewrite the Anti-Patterns section to add value beyond the Implementation Guidelines rather than restating the format-args and strings.xml rules verbatim.

Dimension	Reasoning	Score
Conciseness	The body is a lean bullet-style standard with no padding or explanation of concepts Claude already knows, but it has trimmable redundancy: a misplaced "Plurals" bullet under Assets/Drawables duplicates the Strings section, and both Anti-Patterns restate guideline bullets verbatim.	4 / 5
Actionability	Guidance names concrete, executable APIs ("stringResource(R.string.*)", "context.getString(R.string.id, args)", "resources.getQuantityString(R.plurals.items, count, count)", "Configuration.UI_MODE_NIGHT") with only minor gaps; full code examples are appropriately delegated to references/implementation.md, which exists and matches the link.	4 / 5
Workflow Clarity	As a single-purpose standards skill with no destructive or batch operations, no validation checkpoints are required, but grammatical breaks ("All UI text must in strings.xml", "must defined in strings.xml") and the misplaced plurals bullet introduce minor ambiguity that keeps it below an unambiguous 5.	4 / 5
Progressive Disclosure	The body is under 50 lines with well-organized sections (Strings & Localization, Assets/Drawables, Anti-Patterns, References) and a single clearly-signaled, one-level-deep reference to references/implementation.md that actually exists and holds the detailed XML/Compose examples.	5 / 5
	Total	17 / 20 Passed

Description

78%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 strong description that names a comprehensive, specific set of targets and includes an explicit use-for clause plus unusually good boundary deferral language. Its main weaknesses are the single generic action verb and an abstract rather than natural-language trigger phrasing.

Suggestions

Lead with more varied concrete actions (e.g., "Define, organize, and look up Android strings...") instead of the single verb "Organize".

Add natural trigger phrases users would say, such as "strings.xml", "translations", "dark mode", or "stringResource", to the use-for clause.

Dimension	Reasoning	Score
Specificity	"Organize Android strings, drawables, fonts, themes, localization, and concrete resource-backed Compose values such as MaterialTheme colors" lists several specific, concrete targets with only minor gaps, though a single generic action verb ("Organize") carries the whole list, falling short of the multiple distinct actions in the anchor 5 example.	4 / 5
Completeness	Both what ("Organize Android strings, drawables, fonts, themes, localization...") and when ("Use for resource declarations and their direct UI lookup") are answered explicitly, but the when-clause is phrased abstractly rather than with concrete user-facing trigger phrases as in the anchor 5 example.	4 / 5
Trigger Term Quality	Natural terms like "Android", "strings", "drawables", "themes", "localization", and "Compose" are present, but common variations users would actually say ("strings.xml", "translations", "dark mode", "stringResource", "R.string") are missing.	4 / 5
Distinctiveness Conflict Risk	The description carves out a clear niche and actively disambiguates with "defer design-system token architecture, network image loading, lint-rule configuration, and general Compose implementation", minimizing conflict with adjacent Compose and design-system skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 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	14 / 16 Passed

Repository: HoangNguyen0403/agent-skills-standard
Path: skills/android/android-resources/SKILL.md
Revision: 4bb4994

Reviewed: 20 days ago

Discovery Implementation Validation

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.

android-resources

Table of Contents

Is this your skill?