CtrlK
BlogDocsLog inGet started
Tessl Logo

audit-dependencies

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

56

Quality

62%

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 well-structured, mostly actionable instruction-only workflow with explicit validation checkpoints, weakened mainly by redundant restatements of the objective and a couple of under-specified steps.

Suggestions

Remove the duplicate objective statement (drop either the opening "You are tasked with…" line or the ## Objective section) to cut redundancy.

Specify how to check for newer stable versions (e.g., a Gradle Versions Plugin command or Maven Central lookup) and how to check <depends> against actual API usage.

Add an explicit error-recovery loop in step 6 (e.g., "If verifyPlugin fails, review build.gradle/plugin.xml changes, fix, and re-run ./gradlew verifyPlugin before proceeding").

DimensionReasoningScore

Conciseness

The objective is stated three times (description, opening "You are tasked with…", and the ## Objective section) and baseline commands (./gradlew test, verifyPlugin) recur in step 6, so it could be tightened despite no concept over-explanation.

3 / 5

Actionability

Concrete commands (./gradlew buildPlugin, verifyPlugin, testClasses) and specific files (build.gradle dependencies block, plugin.xml <depends> tags, lib/*.jar) are given, but steps like "Check for newer stable versions" lack an executable command.

4 / 5

Workflow Clarity

A clear 7-step sequence with explicit validation checkpoints (baseline in step 1, verify in step 6), though the error-recovery feedback loop (what to do if verify fails) is only implicit rather than stated.

4 / 5

Progressive Disclosure

Under 50 lines with no bundle files and no need for external references, organized into clear numbered sections — meets the simple-skill exception for a top score on progressive disclosure.

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 clearly states what the skill does using third person and two concrete actions, but lacks any explicit trigger/"Use when" guidance and has limited keyword coverage.

Suggestions

Add a "Use when…" clause naming natural user triggers (e.g., "Use when auditing a plugin's dependencies, reducing plugin size, or updating outdated libraries in build.gradle").

Include synonyms and concrete artifacts users mention (deps, build.gradle, plugin.xml, .jar files) to improve trigger-term coverage.

Mention the JetBrains/IntelliJ plugin context to sharpen distinctiveness versus generic dependency-cleanup skills.

DimensionReasoningScore

Specificity

Quotes "removing unused dependencies and updating outdated libraries" plus domain "plugin size and security" — names the domain and two concrete actions, but coverage is not comprehensive.

3 / 5

Completeness

The "what" is clear (optimize plugin size/security via dependency cleanup) but there is no "Use when…" clause, which per guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like "unused dependencies" and "outdated libraries" are relevant but no synonyms (deps, build.gradle, Maven) or file extensions are included, so common variations are missing.

3 / 5

Distinctiveness Conflict Risk

The "plugin size and security" framing is a fairly distinct niche, with only minor overlap risk against general dependency-cleanup 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
flutter/flutter-intellij
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.