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.
76
95%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Find Package Skill
Some SDK packages in this monorepo have package-specific skills — tribal knowledge (architecture, data flows, type mappings, pitfalls) that prevents common mistakes. Before modifying any SDK package, check whether a skill exists for it using the steps below.
How to Discover Package Skills
-
Determine the package directory. If you already know the file path you're modifying, extract the package directory from it (e.g., a file at
sdk/search/Azure.Search.Documents/src/SearchClient.csbelongs to the package atsdk/search/Azure.Search.Documents/). If you only have a package name, search for a matching directory undersdk/or use.github/CODEOWNERSpath patterns to resolve the service area. -
Check for a
.github/skills/directory inside the package directory. For example, check whethersdk/search/Azure.Search.Documents/.github/skills/exists. -
If it exists, read every
SKILL.mdfound under that directory. If areferences/subdirectory exists next to aSKILL.md, read all files in it too for additional context. -
If no
.github/skills/directory exists for the package, no package-specific skill has been created yet — proceed normally.
- Repository
- Azure/azure-sdk-for-net
- Commit
0afb185
- Last updated
- First committed
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.