CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

audit-dependencies

Optimize plugin size and security by removing unused dependencies and updating outdated libraries.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/audit-dependencies/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a concise, well-sequenced IntelliJ plugin dependency-audit workflow with concrete verification commands at both ends, and it appropriately fits in a single short file. Its main weakness is that the central audit steps (identifying unused dependencies, checking for newer versions) describe goals without giving the concrete method or commands to accomplish them.

Suggestions

Add a concrete technique for step 2, e.g., "Run `./gradlew dependencies` and grep the source for imports of each library (`grep -r 'import <group>' src/`) to confirm it is unused before removing it."

Make step 4 executable by specifying how to check versions, e.g., the Versions plugin (`./gradlew dependencyUpdates`) or checking Maven Central for the latest stable release.

Add a feedback loop after removal: "If `./gradlew buildPlugin` or tests fail, restore the removed dependency from the diff and re-run before proceeding to version updates."

DimensionReasoningScore

Conciseness

The body is a lean, bulleted workflow with no concept explanations Claude would already know, satisfying the efficiency anchors; the only trimmable padding is that the description sentence is restated twice ("You are tasked with optimizing..." and the Objective section). Not a 5 because that duplicated restatement and the slightly wordy step 6 are tokens that could be cut.

4 / 5

Actionability

Verification steps give executable commands (`./gradlew test`, `./gradlew verifyPlugin`, `./gradlew buildPlugin`) and name concrete artifacts (`build.gradle` dependencies block, `<depends>` tags, `lib/` jars), but the core audit steps give no method — "Identify libraries that might no longer be used" and "Check for newer stable versions" lack the specific commands or search technique to execute them. This matches anchor 3 (concrete guidance present but key details missing) rather than 4, where gaps would be minor.

3 / 5

Workflow Clarity

A clear 7-step sequence with a baseline checkpoint (run tests before changes) and a final verification pass (buildPlugin, testClasses, test, verifyPlugin, plus manual test steps) covers most checkpoints. Not a 5 because there is no error-recovery feedback loop (e.g., what to do if verifyPlugin fails after a removal) and no validation between removing dependencies and updating versions, leaving minor validation gaps typical of anchor 4.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external reference files, and the content is organized into clearly labeled, well-ordered sections (Baseline, Audit, Check, Update, Remove, Verify, Report). Per the rubric's guidance for short single-purpose skills, this earns a 5 on well-organized sections alone; there are no references to verify and no nested or buried content.

5 / 5

Total

16

/

20

Passed

Description

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

The description states a clear, concrete purpose with two specific actions and mostly distinct trigger terms, but it entirely lacks a "when to use" clause, which limits discoverability. Adding explicit trigger guidance and ecosystem keywords would raise completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g., "Use when auditing an IntelliJ plugin's build.gradle, shrinking plugin distribution size, or when the user mentions unused or outdated dependencies."

Include natural user phrasings and synonyms such as "audit dependencies", "update libraries", "dependency cleanup", and "gradle" to broaden trigger-term coverage.

Mention the concrete artifacts involved (build.gradle dependencies block, plugin.xml <depends> tags, lib/ jars) to sharpen distinctiveness against generic dependency-management skills.

DimensionReasoningScore

Specificity

"removing unused dependencies and updating outdated libraries" names the domain (plugin size/security) and exactly two concrete actions, matching the anchor for 1-2 concrete actions without comprehensive coverage. Not a 4 because there is no third action or detail (e.g., auditing build files, checking plugin.xml) stated explicitly.

3 / 5

Completeness

The "what" is clear (remove unused dependencies, update outdated libraries to optimize plugin size and security), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the "what" is concrete rather than vague.

3 / 5

Trigger Term Quality

Phrases like "unused dependencies", "outdated libraries", and "plugin size" are relevant keywords users might say, but common variations such as "audit dependencies", "update libraries", "build.gradle", or "gradle" are missing. It is above anchor 2 (which expects only generic keywords) but clearly below the good coverage of anchor 4.

3 / 5

Distinctiveness Conflict Risk

The plugin/dependency-management niche is fairly distinct with targeted trigger terms ("plugin size", "unused dependencies"), with only minor overlap risk against generic dependency-update or code-cleanup skills. Not a 5 because the description lacks ecosystem-specific markers (e.g., IntelliJ/Gradle) that would fully separate it from similar build-tooling skills.

4 / 5

Total

13

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

flutter/flutter-intellij

Path

.agents/skills/audit-dependencies/SKILL.md

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.