A utility to identify and load package-specific guidelines (tribal knowledge) before modifying code within the Azure SDK monorepo.
Install
mkdir -p .claude/skills/find-package-skill && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10126" && unzip -o skill.zip -d .claude/skills/find-package-skill && rm skill.zipInstalls to .claude/skills/find-package-skill
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
**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.Key capabilities
- →Discover package-specific skills
- →Locate architectural constraints
- →Find hidden documentation
- →Identify tribal knowledge
- →Prepare for SDK modifications
How it works
It checks for package-specific .github/skills/ directories to surface domain knowledge before modifying SDK code.
Inputs & outputs
When to use find-package-skill
- →Preparing to fix a bug in an SDK package
- →Identifying architectural constraints for a library
- →Locating hidden documentation in a monorepo
About this skill
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.
When not to use it
- →General repository searches
Limitations
- →Requires package-specific skills to be documented
How it compares
It prevents common mistakes by surfacing hidden, package-specific architectural constraints that are not obvious from the code alone.
Compared to similar skills
find-package-skill side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| find-package-skill (this skill) | 0 | 4mo | No flags | Beginner |
| deepwiki-rs | 25 | 9mo | Review | Intermediate |
| python-code-style | 9 | 6mo | Review | Intermediate |
| code-review-excellence | 19 | 5mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by Azure
View all by Azure →You might also like
deepwiki-rs
sopaco
AI-powered Rust documentation generation engine for comprehensive codebase analysis, C4 architecture diagrams, and automated technical documentation. Use when Claude needs to analyze source code, understand software architecture, generate technical specs, or create professional documentation from any programming language.
python-code-style
wshobson
Python code style, linting, formatting, naming conventions, and documentation standards. Use when writing new code, reviewing style, configuring linters, writing docstrings, or establishing project standards.
code-review-excellence
wshobson
Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.
code-walk-thru
pchalasani
Use this when user wants you to walk through (code or text) files in a EDITOR to either explain how some code works, or to show the user what changes you made, etc. You would typically use this repeatedly to show the user your changes or code files one by one, sometimes with specific line-numbers. This way the user is easily able to follow along in their favorite EDITOR as you point at various files possibly at specific line numbers within those files.
cookbook-audit
anthropics
Audit an Anthropic Cookbook notebook based on a rubric. Use whenever a notebook review or audit is requested.
schema-markup
davila7
When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," or "breadcrumb schema." For broader SEO issues, see seo-audit.