CtrlK
BlogDocsLog inGet started
Tessl Logo

package-search

Search Unity's package registry plus locally installed packages (Git, local, embedded sources) by query string. Returns available versions and installation status. Online mode fetches exact matches from the live registry then supplements with cached substring matches.

60

Quality

69%

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 ./Unity-MCP-Plugin/.claude/skills/package-search/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 highly actionable with complete executable examples and schemas for a single-purpose tool, but conciseness suffers from duplicated input documentation that could be consolidated.

Suggestions

Merge the '## Inputs' bullet list and the '## Input' table into a single authoritative section to eliminate duplication of query/maxResults/offlineMode.

Remove the restated result-composition sentence in the body since the output schema already defines each field, or keep only one.

Consider moving the large output JSON schema to a referenced file if this skill grows, to keep the overview lean.

DimensionReasoningScore

Conciseness

Mostly efficient with executable CLI examples and schemas, but the 'query/maxResults/offlineMode' material is duplicated across '## Inputs' and '## Input' table, and result composition is restated, adding unnecessary tokens.

3 / 5

Actionability

Fully executable, copy-paste-ready CLI invocations covering direct input, --input-file, stdin heredoc, and a troubleshooting path for a missing binary, plus complete input/output JSON schemas.

5 / 5

Workflow Clarity

The single search action is unambiguous with clearly ordered sections (Inputs, How to Call, Troubleshooting, Output); as a non-destructive single-task skill no validation feedback loop is required, though no verification of results is shown.

4 / 5

Progressive Disclosure

Well-organized sections with clear headers and inline schemas; no bundle files exist, so content stays self-contained, but the duplicated input sections slightly reduce organization quality.

4 / 5

Total

16

/

20

Passed

Description

63%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 is specific and distinct, clearly conveying what the tool does across online/offline modes, but it lacks an explicit 'Use when...' trigger clause, which caps its completeness.

Suggestions

Add an explicit trigger clause such as 'Use when searching for Unity packages by name, display name, or keyword before installing them.'

Include a few natural user-facing synonyms (e.g. 'package lookup', 'find packages') to broaden trigger term coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'Search Unity's package registry plus locally installed packages (Git, local, embedded sources)', 'Returns available versions and installation status', 'fetches exact matches from the live registry then supplements with cached substring matches' — with only minor coverage gaps.

4 / 5

Completeness

Has a clear 'what' but no explicit 'when'/'Use when...' trigger clause, and the guideline caps completeness at 3 when trigger guidance is missing.

3 / 5

Trigger Term Quality

Good keyword coverage with natural terms users would say ('Unity', 'package', 'package registry', 'installed packages', 'query string'), but a few natural variations or synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Unity Package Manager search) with distinct triggers and only minor overlap risk with closely related Unity skills.

4 / 5

Total

15

/

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
IvanMurzak/Unity-MCP
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.