OpenParable
Skip to content
← Back to skills

Find Package Skill

Development
find-package-skill

Find Package Skill is an Agent Skill for development published in the Azure/azure-sdk-for-net repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

**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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Azure/azure-sdk-for-net/blob/HEAD/.github/skills/find-package-skill/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/find-package-skill, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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

  1. 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.cs belongs to the package at sdk/search/Azure.Search.Documents/). If you only have a package name, search for a matching directory under sdk/ or use .github/CODEOWNERS path patterns to resolve the service area.

  2. Check for a .github/skills/ directory inside the package directory. For example, check whether sdk/search/Azure.Search.Documents/.github/skills/ exists.

  3. If it exists, read every SKILL.md found under that directory. If a references/ subdirectory exists next to a SKILL.md, read all files in it too for additional context.

  4. If no .github/skills/ directory exists for the package, no package-specific skill has been created yet — proceed normally.