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 命名时使用。

75

Quality

93%

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

86%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.

Well-structured, actionable body with concrete XML paradigms and a real reference split. It loses a little to mild intro padding and the absence of an explicit error-recovery loop, but is otherwise strong.

Suggestions

Tighten the intro sentence and drop the '本 Skill 自包含,不依赖任何外部文档' line—just link the reference; the self-containment is implied.

Add an explicit post-generation validate step (e.g. 'run aapt/gradle resource check; if naming violations surface, fix and re-run') to turn the self-check list into a feedback loop.

Fold the '何时不建文件' decision rules into a compact table so the choose-reuse-vs-create path is scannable alongside the self-check list.

DimensionReasoningScore

Conciseness

Mostly efficient—rule lists, syntax templates, and XML paradigms with no padding about concepts Claude already knows—though the intro line and '本 Skill 自包含' phrasing are mild trim opportunities that keep it just short of lean.

4 / 5

Actionability

Provides copy-paste-ready selector and ColorStateList XML paradigms, concrete filename grammar (bg_<color>[_r<radius>]…_suffix), explicit prefix families, and a decision table for when not to create a file—fully executable guidance covering common cases.

5 / 5

Workflow Clarity

Clear logical sequence (when-to-use → hard constraints → naming rules → drawable families → single-file integration → when-not-to-create → self-check) with a pre-generation checklist as a validation checkpoint, but no explicit validate→fix→retry feedback loop.

4 / 5

Progressive Disclosure

SKILL.md is an overview that keeps key paradigms inline and pushes full prefix tables, qualifier ordering, examples and anti-examples to references/reference.md via clearly signaled one-level-deep links (verified to resolve to real anchors).

5 / 5

Total

18

/

20

Passed

Description

100%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 high-quality description: third-person, concrete, and comprehensive, with an explicit 'Use when…' clause and rich natural trigger terms. It cleanly separates what the skill does from when to invoke it.

DimensionReasoningScore

Specificity

Lists multiple concrete actions—prefix/snake_case rules, encoding color/radius/stroke/state into filenames, single-file selectors with inline shape and default-last ordering, real-hex naming (e.g. text_color_333333_ffffff_selector)—giving comprehensive coverage rather than vague abstraction.

5 / 5

Completeness

Explicitly answers 'what' (unify naming, encode attributes into filenames, generate single-file multi-state resources) and 'when' ('在用户要求命名或重命名资源文件、生成…时使用') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Covers natural Android terms and synonyms users actually say—layout/drawable/mipmap/color/values/id, selector, ColorStateList, state color, shape, ripple, layer-list, colors/dimens/styles—so trigger surface is broad.

5 / 5

Distinctiveness Conflict Risk

Scoped tightly to Android XML resource naming with distinctive triggers (selector/ColorStateList/shape/ripple/layer-list), giving a clear niche with minimal overlap risk against other skills.

5 / 5

Total

20

/

20

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.