What does this skill do, and when should you use it?
This skill gives coding agents practical guidance and C# patterns for the Azure.ResourceManager.ApiCenter .NET SDK. It covers API Center services, workspaces, APIs, versions, definitions, environments, deployments, and metadata schemas. It also explains DefaultAzureCredential authentication, specification import/export, API listing, and Azure error handling. It fits .NET teams that use Azure API Center as an organization-wide API inventory and governance system.
Guides agents to install Azure.ResourceManager.ApiCenter and Azure.Identity, read Azure subscription, resource-group, and API Center service configuration, and produce C# code. The examples create or update API Center services, workspaces, APIs, API versions, API definitions, environments, deployments, and metadata schemas; import or export OpenAPI-style specifications; enumerate APIs, versions, environments, and deployments; and handle 400, 409, and other RequestFailedException failures.
- A platform team provisions an API Center service and creates workspaces for engineering teams or products.
- A .NET developer registers APIs with lifecycle stages, contacts, external documentation, and custom properties.
- A governance team defines metadata schemas and requires APIs to record ownership, cost center, or data classification.
- An API team uploads an OpenAPI specification, manages API versions, and exports a definition for another workflow.
- A platform or operations team records development, testing, staging, and production environments and links API definitions to deployments.
How do you install this skill?
- Create, update, and import operations can change Azure resources or write API specifications externally; confirm the target subscription, resource group, RBAC permissions, and rollback plan before use.
- The snippets are not a complete compilable project; verify DefaultAzureCredential usage, collection-initializer syntax, package versions, and API models.
- The skill does not explain protection of sensitive data in API specifications, contacts, or custom metadata, nor reachability of referenced documentation and Azure services from mainland-China networks.
- Shell / CLI
- Network access
- Local filesystem
.NET SDKAzure.ResourceManager.ApiCenterAzure.Identity
In an environment supporting the collection, run npx skills add microsoft/skills and select the required skill in the wizard. Skills are installed in the selected agent directory, such as .github/skills/ for GitHub Copilot; the repository also documents copying or symlinking individual skill directories. This skill is located at .github/plugins/azure-sdk-dotnet/skills/azure-mgmt-apicenter-dotnet/SKILL.md. For SDK use, install Azure.ResourceManager.ApiCenter with dotnet add package Azure.ResourceManager.ApiCenter and install Azure.Identity with dotnet add package Azure.Identity.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/microsoft/skills.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/.github/plugins/azure-sdk-dotnet/skills/azure-mgmt-apicenter-dotnet" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Ask the coding agent for a task containing terms such as “API Center,” ApiCenterService, ApiCenterWorkspace, ApiCenterApi, “API inventory,” “API governance,” “API versioning,” “API catalog,” or “API discovery.” Supply the Azure subscription ID, resource-group name, and API Center service name. If production code uses DefaultAzureCredential, set AZURE_TOKEN_CREDENTIALS=prod or select a specific credential. The agent can then generate C# management code based on ArmClient.
What are this skill's strengths and limitations?
- Covers the main API Center resource hierarchy and lifecycle operations.
- Provides copyable asynchronous C# examples for specification import/export, deployment linking, and metadata governance.
- States the API version 2024-03-01, SDK version v1.0.0 GA, and MIT license.
- Includes authentication, environment variables, resource types, best practices, and common Azure error handling.
- It focuses on Azure.ResourceManager.ApiCenter for .NET rather than general API management or gateway development.
- Examples require an Azure subscription, resource group, and API Center service; the source provides no local mock environment or complete skill-specific test suite.
- The source does not document installation details for clients beyond the listed agent installation methods.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Azure API Center for .NET this page ✓ Microsoft · Official | 48 · Use with care | ★ 2.7k | 3mo ago | MIT |
| Azure API Center Python Manager ✓ Microsoft · Official | 48 · Use with care | ★ 2.7k | 3mo ago | MIT |
| Azure Playwright Workspace Manager ✓ Microsoft · Official | 54 · Use with care | ★ 2.7k | 3mo ago | MIT |
| Fabric Capacity Manager for .NET ✓ Microsoft · Official | 53 · Use with care | ★ 2.7k | 3mo ago | MIT |
| MongoDB Atlas Azure ARM Manager ✓ Microsoft · Official | 51 · Use with care | ★ 2.7k | 3mo ago | MIT |
Unlike Azure.ResourceManager.ApiManagement, this skill focuses on API Center inventory, governance, versioning, definitions, environments, and deployment records. The source describes the API Management SDK as covering API gateways and policies.
How did FollowSkills review this skill?
The skill shows Azure SDK authentication, resource-management, and specification-import operations, with no malware, credential theft, or covert exfiltration; however, it omits least-privilege RBAC guidance, user confirmation, sensitive-specification handling, impact disclosure, rollback, and recovery, so points are deducted.
It covers service, workspace, API, version, definition, environment, deployment, metadata, and listing workflows and includes limited Azure exception handling; however, there are no skill-specific tests or retry/idempotency guidance, and several C# snippets may not compile as written, so the static score remains below 10.
Triggers, the .NET SDK target, and primary scenarios are reasonably clear; however, non-fit boundaries, Azure/RBAC prerequisites, input-output boundaries, Chinese-language support, and mainland-China network reachability are not addressed, so points are deducted.
The document has clear sections, installation commands, environment variables, hierarchy, workflows, type references, best practices, error handling, license, author, and version metadata; it lacks a changelog, explicit maintenance owner/update path, compatibility guidance, and known limitations, so points are deducted.
The material covers common API Center management tasks and offers directly useful reference patterns for experienced Azure .NET developers; however, examples may require correction and omit end-to-end validation, permission setup, existing-resource handling, and complete project context, so effectiveness is only partial.
NuGet, API reference, product documentation, and source links are provided, along with package and API version claims; however, this review is static, and no skill-specific CI, committed tests, or third-party execution evidence is shown, preventing independent reproduction of key examples.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →