Owners Agent Skill

Query and modify CODEOWNERS ownership, service labels, and package associations in Azure SDK repositories. **UTILITY SKILL**. FOR SINGLE OPERATIONS: view, add, or remove owners and labels. WHEN: \"code owners\", \"view codeowners\", \"add package owner\", \"remove package owner\", \"add label\", \"remove label\", \"codeowners blocked PR\", \"who owns this package\", \"create service label\", \"update codeowners cache\", \"unblock release\". INVOKES: azsdk_engsys_codeowner_view, azsdk_engsys_codeowner_add_package_owner, azsdk_engsys_codeowner_add_label_owner, azsdk_check_service_label, azsdk_create_service_label, azsdk_engsys_codeowner_update_cache, azsdk_engsys_codeowner_check_package.

4k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

6033

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/Azure/azure-sdk-for-net --skill owners

What comes with it

15 127 bytes besides the instruction

eval.yaml

references/operations-reference.md

references/owners-and-labels.md

references/troubleshooting.md

tasks/labels-create-service-label-001.yaml

tasks/owners-add-001.yaml

tasks/owners-add-label-owner-001.yaml

tasks/owners-add-package-label-001.yaml

tasks/owners-label-001.yaml

tasks/owners-negative-001.yaml

tasks/owners-remove-label-owner-001.yaml

tasks/owners-remove-pkg-label-001.yaml

tasks/owners-remove-pkg-owner-001.yaml

tasks/owners-unblock-pr-001.yaml

tasks/owners-view-001.yaml

The instruction itself

7 sections, as written by the author

Owners

Requires: azure-sdk-mcp server

Tools

| Tool | Purpose |

|------|---------|

| azsdk_engsys_codeowner_view | Query by user, label, package, path |

| azsdk_engsys_codeowner_add_* | Add owners/labels (details) |

| azsdk_engsys_codeowner_remove_* | Remove owners/labels |

| azsdk_check_service_label | Check if service label exists |

| azsdk_create_service_label | Create service label |

| azsdk_engsys_codeowner_check_package | Check if a package has sufficient owners, labels, and service owners |

| azsdk_engsys_codeowner_update_cache | Run the CODEOWNERS cache update pipeline to propagate changes |

CLI fallback: azsdk config codeowners CLI when MCP is unavailable.

Repository Resolution

Infer repo from workspace in Azure/azure-sdk-for-* repos. Otherwise, ask.

Workflow

Query — azsdk_engsys_codeowner_view to inspect current state.
Modify — Add/remove owners or labels.
Verify — Re-query to confirm.
Update cache — After all ownership changes are complete, ask the user if they want to run azsdk_engsys_codeowner_update_cache to propagate changes immediately. This is especially important when changes are needed to unblock PRs or releases.

New labels: azsdk_check_service_label → azsdk_create_service_label → PR merged → azsdk_engsys_codeowner_add_package_label. See data model.

Checking Package Readiness

Use azsdk_engsys_codeowner_check_package with a package directoryPath to verify a package has sufficient owners, PR labels, and service owners. This is useful to diagnose why a PR or release is blocked due to missing ownership.

Examples

"Add @user to azure-core in azure-sdk-for-python"
"Who owns azure-storage-blob?"

Troubleshooting

See troubleshooting for common issues.

Other skills for the same job

different authors, same section of the catalogue

MCP Builder

by anthropics

vendor ×13

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens

Finishing A Development Branch

by ZhanlinCui

×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Vercel React Native Skills

by vercel-labs

vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

39k tokens

Vercel React Best Practices

by ratacat

×5

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

1k tokens

How to use it

Copy the folder

Take azure/owners from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.