CtrlK
BlogDocsLog inGet started
Tessl Logo

find-package-skill

**UTILITY SKILL** — Must be consulted before making any changes to packages under sdk/. Discovers and loads package-specific domain knowledge that prevents common mistakes. WHEN: add feature to package; fix bug in package; modify package code; regenerate from typespec; change client library.

65

Quality

78%

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 ./.github/skills/find-package-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 concise, well-organized instruction skill that clearly sequences a simple discovery workflow with concrete example paths and an explicit fallback. It could be slightly tighter in its intro and offer more copy-paste-ready commands, but it is strong overall.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, with a brief justified intro and direct numbered steps; the opening sentence explaining 'tribal knowledge (architecture, data flows, type mappings, pitfalls)' is mild over-explanation that could be trimmed, keeping it just below 5.

4 / 5

Actionability

Steps give concrete, executable guidance with specific example paths ('sdk/search/Azure.Search.Documents/.github/skills/'), but instructions like 'search for a matching directory' rely on Claude to construct the command rather than being copy-paste ready, so it does not reach 5.

4 / 5

Workflow Clarity

A clear four-step numbered sequence with an explicit if-exists/if-not-exists branch handling the missing-skill case; this is a non-destructive discovery workflow so the destructive-cap and checkpoint expectations do not apply, but the absence of any validation checkpoint holds it at 4 rather than 5.

4 / 5

Progressive Disclosure

Under 50 lines with no bundle files and no need for external references, the body is well-organized into a clear intro plus a 'How to Discover Package Skills' section with numbered steps, meeting the simple-skill exception for a top score.

5 / 5

Total

17

/

20

Passed

Description

78%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 well-structured utility-skill description with clear what/when guidance, third-person voice, and concrete trigger phrases. It is slightly limited by listing only two core actions and using fairly generic task triggers.

DimensionReasoningScore

Specificity

Names the domain ('packages under sdk/') and two concrete actions ('Discovers and loads package-specific domain knowledge'), matching the anchor for 1-2 concrete actions without comprehensive coverage; not enough distinct actions to reach 4.

3 / 5

Completeness

It explicitly states what ('Discovers and loads package-specific domain knowledge that prevents common mistakes') and an explicit 'WHEN:' list of concrete trigger phrases, matching the anchor that requires both with concrete triggers.

5 / 5

Trigger Term Quality

The 'WHEN:' clause lists several natural developer phrases ('add feature to package; fix bug in package; modify package code; regenerate from typespec; change client library') giving good coverage, though it lacks synonyms/extension variants that would push it to 5.

4 / 5

Distinctiveness Conflict Risk

Scoped to 'packages under sdk/' with task-specific triggers, giving it a clear niche with minimal conflict risk; some triggers like 'fix bug in package' are generic enough to risk minor overlap, keeping it just below 5.

4 / 5

Total

16

/

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
Azure/azure-sdk-for-net
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.