update-dependencies

Use this skill to update Android library dependencies via refreshVersions. Invoke when the user asks to update, bump, or refresh dependencies or a specific library version, asks what updates are available, or hands over a dependency-update task from the Asana backlog. Covers running refreshVersions, judging which bumps are safe, handling libraries blocked by the project's Kotlin version, running the E2E suite, and the PR/Asana conventions for the change.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

76%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 well-organized, highly actionable project-specific process skill with concrete commands and IDs throughout. The main weakness is workflow clarity: as a batch operation it lacks an explicit failure-feedback loop and presents its workflow as topical sections rather than an enumerated sequence with checkpoints.

Suggestions

Add an explicit feedback loop for the E2E validation step — e.g. 'If the E2E run fails, revert the offending bump in versions.properties, re-run refreshVersions, and re-trigger the workflow before opening the PR.'

Consider presenting the high-level process as a short numbered checklist (refreshVersions → classify → Kotlin check → E2E validate → PR → Asana) at the top, with the current sections as elaboration, so the sequence and checkpoints are explicit.

Optionally move the Library Classification list and PR Conventions into a reference file under references/ to keep SKILL.md as a leaner overview, since the body is over 50 lines and all content is currently inline.

Dimension	Reasoning	Score
Conciseness	Mostly lean and assumes Claude's competence (no explaining what Gradle/KSP/AGP are), with a few framing sentences ('This is the most important judgement when evaluating a library update') and the quoted engineer dialogue that could be tightened slightly.	4 / 5
Actionability	Provides copy-paste-ready commands ('./gradlew refreshVersions', "sed -i '' '/^##/d' versions.properties", 'gh workflow run 223981529 --repo duckduckgo/Android --ref <branch>') plus concrete workflow IDs, task GIDs, and URLs covering the common cases.	5 / 5
Workflow Clarity	Sections are logically ordered (refreshVersions → Kotlin check → classify → test → PR → Asana) and a validation step exists (E2E suite), but for a batch operation there is no explicit feedback loop ('if E2E fails → revert/investigate') and checkpoints are implicit rather than enumerated, capping this at 3 per the batch-operation rule.	3 / 5
Progressive Disclosure	No bundle files exist, and the >50-line body is entirely inline, but it is well-organized with clear section headers and external references (Asana task, E2E workflow) are clearly signaled; minor organization gap is that the library-classification list and PR conventions could live in separate reference files.	4 / 5
	Total	16 / 20 Passed

Description

92%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, specific description that clearly states what the skill does and when to invoke it, with concrete trigger phrases and a well-scoped niche. The only gap is slightly less-than-comprehensive trigger-term coverage (missing 'upgrade' and file-type mentions).

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'running refreshVersions, judging which bumps are safe, handling libraries blocked by the project's Kotlin version, running the E2E suite, and the PR/Asana conventions' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (update Android library dependencies via refreshVersions, with the listed sub-tasks) and 'when' via a concrete 'Invoke when the user asks to...' trigger clause with multiple specific trigger phrases.	5 / 5
Trigger Term Quality	Includes natural synonyms users would say ('update, bump, or refresh dependencies', 'specific library version', 'what updates are available', Asana backlog handoff), but omits common synonyms like 'upgrade' and has no file-extension triggers; good but not comprehensive.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Android library dependency updates via refreshVersions tied to a specific project's Asana/E2E workflow) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: duckduckgo/Android
Path: .claude/skills/update-dependencies/SKILL.md
Commit: 7809186

Reviewed: 6 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.