CtrlK
BlogDocsLog inGet started
Tessl Logo

android-version-platform-adapt

依据 Android 官方「版本」文档完成平台适配:按版本号 N 抓取行为变更(所有应用、 targetSdk=N)、changes/features 子页与探索新功能/API;归纳影响项并落地到 Manifest/Gradle/工具类封装。在用户要求 Android 版本适配、行为变更排查、 targetSdk 升级、新 API 封装或对照 developer.android.com/about/versions 时使用。

74

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%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, highly actionable workflow with clear sequencing, validation checkpoints, and proper one-level-deep reference splitting. The main weakness is minor redundancy between inline URL examples and the reference file.

Suggestions

Remove the "Android 17 固定示例" URL list (or collapse to one example) since the URL 模板 table already covers them, cutting duplicate tokens.

Keep the bash scan command in one place — reference it from §4 instead of duplicating the full loop in both SKILL.md and reference.md.

Replace the literal {N} in the inline curl command with ${N} (as in reference.md) so the snippet is directly executable without manual substitution.

DimensionReasoningScore

Conciseness

Mostly efficient and free of concept explanations Claude already knows, but the "Android 17 固定示例" block re-lists URLs already given by the template table, and the §4 scan command plus checklist partially duplicate content also in reference.md — it could be tightened.

2 / 3

Actionability

Provides copy-paste-ready URL templates, an executable bash link-scan loop, a concrete WebFetch/WebSearch retry policy, and a fill-in 适配摘要 markdown template — fully executable guidance.

3 / 3

Workflow Clarity

Multi-step process is clearly sequenced (0→1→2→3→4) with explicit checkpoints — "先读再写", fetch-fail→WebSearch+retry, and "凡未读过...补读后再更新摘要" — plus a copyable checklist.

3 / 3

Progressive Disclosure

SKILL.md is an overview that pushes detailed Android 17 scan results and repo-discovery guidance to references/reference.md via clearly signaled, section-anchored, one-level-deep links; the bundle structure matches the references.

3 / 3

Total

11

/

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, third-person description that names concrete actions, gives explicit use-when triggers, and carves out a distinct niche. It avoids vague fluff and over-claims while staying concise.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "抓取行为变更(所有应用、targetSdk=N)", "changes/features 子页与探索新功能/API", "归纳影响项并落地到 Manifest/Gradle/工具类封装" — rather than vague language.

3 / 3

Completeness

Explicitly states both what it does (官方文档驱动的平台适配流程) and when to use it ("在用户要求...时使用"), with explicit triggers; not merely implied.

3 / 3

Trigger Term Quality

Covers natural terms an Android developer would say — "Android 版本适配", "行为变更排查", "targetSdk 升级", "新 API 封装", "developer.android.com/about/versions" — with good breadth.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche — official-doc-driven Android version/platform adaptation — with triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

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.