CtrlK
BlogDocsLog inGet started
Tessl Logo

android-xml-resource

统一 Android XML 资源命名:layout、drawable、mipmap、color、values、id 的前缀与 snake_case 规则;把颜色/圆角/描边/状态编码进文件名(bg_、border_、text_color_…_selector)。 生成 selector 与 ColorStateList 时多状态写入单个文件、内联 shape、默认项放最后、按真实颜色 hex 命名(如 text_color_333333_ffffff_selector)。在用户要求命名或重命名资源文件、生成 selector / state color / shape / ripple / layer-list drawable、整理布局 id、 规范 colors/dimens/styles 命名时使用。

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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

A well-structured, token-efficient body that loads only project-specific conventions Claude would not know, gives executable XML patterns, and routes full tables to a single one-level reference. Its pre-generation checklist and decision flow provide clear validation for the naming task.

DimensionReasoningScore

Conciseness

The body is dense and project-specific (custom naming grammar, single-file selector rules) without explaining concepts Claude already knows; full prefix tables are offloaded to reference.md and inline content is summaries plus the core patterns, so every token earns its place rather than being padded.

3 / 3

Actionability

Provides copy-paste-ready executable XML (full background-selector with inline shape, full ColorStateList), a concrete filename grammar (bg_<color1>[_<color2>]..._<suffix>), and worked examples like text_color_333333_ffffff_selector — fully actionable, not pseudocode.

3 / 3

Workflow Clarity

Sequences use → hard constraints → naming rules → state single-file → "何时不建文件" decision flow → a pre-generation self-check checklist that acts as an explicit validation checkpoint; validation is present (so not capped at 2) even though, for a naming skill, the loop is a one-shot checklist rather than a rebuild-retry cycle.

3 / 3

Progressive Disclosure

SKILL.md is an overview with well-signaled one-level-deep links to references/reference.md (verified to exist, with real anchors like #drawable-命名两族 and #配置限定符顺序); detail is appropriately split out rather than nested or inlined.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

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, concrete description with an explicit third-person "use when" clause, multiple specific actions, and natural trigger terms anchored to a distinct Android-resource-naming niche. It avoids fluff and over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: "统一 Android XML 资源命名", "把颜色/圆角/描边/状态编码进文件名", "生成 selector 与 ColorStateList 时多状态写入单个文件、内联 shape、默认项放最后", "整理布局 id、规范 colors/dimens/styles 命名" — matching the "lists multiple specific concrete actions" anchor, not the level-2 single-domain anchor.

3 / 3

Completeness

Explicitly answers both what (unify naming across layout/drawable/mipmap/color/values/id with prefix and snake_case rules) and when ("在用户要求...时使用"), so it is not capped at 2 like a description missing a Use-when clause.

3 / 3

Trigger Term Quality

The when-clause names natural trigger phrases an Android dev would actually say — "命名或重命名资源文件", "生成 selector / state color / shape / ripple / layer-list drawable", "整理布局 id", "规范 colors/dimens/styles 命名" — giving good coverage rather than the sparse level-2 set.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (Android XML resource naming with a value-encoding filename grammar) and its triggers (selector/ColorStateList/shape generation, id tidying) are unlikely to fire for unrelated skills, matching the distinct-niche anchor.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
afkT/DevUtils
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.