project-gradle-central-deps

在 DevUtils 工程（仓库布局契约 DEPS_ROOT=file/gradle、DEPS_MANIFEST=file/deps）中新增或引用 Gradle 依赖时，先查 {DEPS_ROOT}/config.gradle、config_kotlin.gradle、 config_androidx.gradle 与 config_libs.gradle 是否已有坐标；按官方/非官方规则写入对应文件分组，并在 {DEPS_MANIFEST}/deps_android.gradle 或 deps_project.gradle 中按现有风格引用。在用户要求添加 AndroidX、CameraX、Kotlin、Jetpack、第三方 Maven 依赖或修改 deps 清单时使用。

Quality

85%

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

70%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, clearly sequenced dependency-management workflow with explicit checkpoints and a self-check list. It is strong on workflow clarity but leans instructive rather than executable and repeats some path tables.

Suggestions

Add one concrete before/after code snippet showing an added coordinate line in config_androidx.gradle and its reference line in deps_android.gradle, so guidance is copy-paste ready.

De-duplicate the file-location tables (the contract table and the section-1 lookup table overlap); keep one and reference it to tighten conciseness.

Tighten judgment-laden phrases like '与现有条目风格一致' by giving one or two concrete examples of the expected style to improve actionability.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and table-driven with no padding about basic Gradle concepts, but the file-location and grouping tables repeat across sections (contract table, section 1 table) and some prose could be tightened.	2 / 3
Actionability	Gives concrete file paths, variable names, and naming conventions (api deps_kotlin.<key>, kapt usage), but offers no executable code/commands and leaves several decisions to 'follow existing style', so it is instructive rather than copy-paste ready.	2 / 3
Workflow Clarity	Clear numbered 5-step sequence (check existence -> decide file/grouping -> add entry with comments -> reference in manifest -> self-check) with an explicit validation/self-check checklist and a dedup enforcement checkpoint.	3 / 3
Progressive Disclosure	Well-organized single-file overview with one-level-deep external references (AndroidX version pages, sibling upgrade skill); no nested reference chains and clear section navigation.	3 / 3
	Total	10 / 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 specific, well-triggered description that clearly states both the capability and when to use it, grounded in a concrete repo layout contract. It is verbose for a description but every phrase carries load.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: query four config files for existing coordinates, write coordinates into grouped files per official/third-party rules, and reference them in deps_*.gradle following existing style.	3 / 3
Completeness	Clearly answers both what (centralized Gradle dependency add/reference workflow across config and deps files) and when ('在用户要求添加 AndroidX、CameraX、Kotlin、Jetpack、第三方 Maven 依赖或修改 deps 清单时使用').	3 / 3
Trigger Term Quality	Explicitly enumerates natural trigger terms users would say: AndroidX, CameraX, Kotlin, Jetpack, third-party Maven dependencies, and modifying the deps manifest.	3 / 3
Distinctiveness Conflict Risk	Scoped to a specific repo-layout contract (DEPS_ROOT/DEPS_MANIFEST) and a distinct dependency-management niche, making conflict with unrelated skills unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: afkT/DevUtils
Path: .cursor/skills/project-gradle-central-deps/SKILL.md
Commit: 3fa9400

Reviewed: 12 days ago

Table of Contents

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.