audit-dependencies

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

Quality

73%

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

Fix and improve this skill with Tessl

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

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concise and highly actionable, with concrete Gradle commands and well-organized sections. The only notable gap is the absence of an explicit error-recovery feedback loop for the destructive dependency-removal steps.

Suggestions

Add an explicit feedback loop for the verify step, e.g. 'If tests fail, revert the offending dependency change and re-run ./gradlew test before proceeding.'

Clarify the abstract audit step ('Identify libraries that might no longer be used') with a concrete method, such as grepping for imports or using a dependency-analysis Gradle plugin.

Make the post-change recovery path explicit rather than leaving 'If needed, add logging statements' as a soft suggestion.

Dimension	Reasoning	Score
Conciseness	The body is lean and free of concept explanations Claude already knows, with every step and command earning its place, matching the 'lean and efficient' anchor.	3 / 3
Actionability	It provides fully executable commands throughout ('./gradlew test', './gradlew verifyPlugin', './gradlew buildPlugin') plus specific file targets ('build.gradle', 'plugin.xml', 'lib/'), making it copy-paste ready.	3 / 3
Workflow Clarity	The 7-step sequence has validation checkpoints (baseline tests before, verify tests after), but the destructive batch context needs an explicit fix-and-revalidate feedback loop that is only implied here, capping it at 2.	2 / 3
Progressive Disclosure	At roughly 35 lines with no external references needed and clear section organization (Objective, numbered Workflow Instructions, Report & Review), it meets the simple-skill allowance for a top score.	3 / 3
	Total	11 / 12 Passed

Description

60%

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 is specific and action-oriented, clearly conveying what the skill does. Its main weaknesses are the missing 'Use when...' trigger clause and limited natural-language trigger terms, which cap completeness and distinctiveness at 2.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to audit or clean up plugin dependencies, reduce plugin size, or update outdated libraries.'

Incorporate natural trigger terms a user would actually say, such as 'audit dependencies', 'clean up build.gradle', or 'plugin is too large'.

Mention the IntelliJ/Gradle plugin context explicitly to reduce overlap with generic dependency-management skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('removing unused dependencies', 'updating outdated libraries', 'Optimize plugin size and security'), matching the multi-action anchor rather than the partial 'some actions' anchor at level 2.	3 / 3
Completeness	It clearly states what the skill does but has no 'Use when...' or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	Domain terms like 'unused dependencies' and 'outdated libraries' are relevant but lack common natural variations a user would say (e.g. 'audit my dependencies', 'clean up build.gradle'), and the natural 'audit' trigger from the skill name is absent.	2 / 3
Distinctiveness Conflict Risk	The plugin/Gradle domain gives it some specificity, but without explicit trigger context it could overlap with general build or dependency-management skills, matching the 'somewhat specific but could overlap' anchor.	2 / 3
	Total	9 / 12 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: flutter/flutter-intellij
Path: .agents/skills/audit-dependencies/SKILL.md
Commit: 21aaf0b

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