What does this skill do, and when should you use it?
This Agent Skill covers the Azure Bot Service management plane through Azure.ResourceManager.BotService and Azure.Identity. It guides coding agents in creating, reading, updating, and deleting Azure Bot resources with Azure Resource Manager, along with configuring channels such as Direct Line, Microsoft Teams, Web Chat, and Slack. It also covers DefaultAzureCredential, resource hierarchy, Direct Line key regeneration, exception handling, and production-oriented practices. It fits .NET developers managing Azure Bot infrastructure and channels, rather than developers primarily implementing conversational bot behavior.
Guides an agent in generating and explaining C#/.NET code to install the Azure.ResourceManager.BotService and Azure.Identity packages, authenticate to Azure, access subscriptions and resource groups, create or update BotResource instances, list and configure BotChannelResource instances, regenerate Direct Line keys, read bot details, update or delete bots, and handle RequestFailedException.
- A .NET platform developer needs to provision Azure Bot resources as part of Azure infrastructure automation.
- A team needs to configure Direct Line, Microsoft Teams, or Web Chat for an existing Azure Bot.
- An operations engineer needs to read, update, or delete bots in an Azure resource group.
- A developer needs examples using DefaultAzureCredential, service-principal authentication, or managed identity with Azure Resource Manager.
How do you install this skill?
- Obtain explicit user confirmation before delete, update, or key-regeneration operations, and verify the subscription, resource group, resource name, and target environment.
- Do not place AZURE_CLIENT_SECRET, MSA app credentials, or DirectLine keys in source code, logs, or prompts; prefer managed identity or Key Vault.
- The examples are not shown to compile against the stated Azure.ResourceManager.BotService versions; perform pinned-version local compilation and integration validation before use.
- The skill provides no evidence about mainland-China network reachability, regional availability, or service limitations.
- Shell / CLI
- Network access
.NET SDKAzure.ResourceManager.BotServiceAzure.Identity
Install the repository collection with npx skills add microsoft/skills, then select the required skill in the wizard. This skill is located at .github/plugins/azure-sdk-dotnet/skills/azure-mgmt-botservice-dotnet/SKILL.md. The supplied material does not document additional client-specific enablement or invocation steps.
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-botservice-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?
Once installed, send your agent any of these to trigger it:
- create an Azure Bot with .NET
- configure Direct Line and Teams channels for an Azure Bot.
Ask a coding agent for a request containing a matching trigger, such as “create an Azure Bot with .NET” or “configure Direct Line and Teams channels for an Azure Bot.” The skill uses dotnet add package Azure.ResourceManager.BotService and dotnet add package Azure.Identity, then operates on subscriptions, resource groups, bots, and channels through ArmClient.
What are this skill's strengths and limitations?
- Covers the main CRUD workflow for Azure Bot resources.
- Includes concrete configuration examples for Direct Line, Teams, Web Chat, Slack, and other channels.
- Provides authentication, managed identity, asynchronous operation, and error-handling guidance.
- Documents key resource types, SKU values, Bot Service kinds, and MSA application types.
- It is focused on Azure Bot Service management-plane operations, not conversational logic or Bot Framework application implementation.
- Examples require an Azure subscription, resource-group access, credentials, and network connectivity.
- The source does not specify required Azure RBAC roles, regional constraints, or detailed permission setup.
- It lists stable v1.1.1 and preview v1.1.0-beta.1 but does not explain how to choose between them.
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 Bot Service ARM SDK for .NET this page ✓ Microsoft · Official | 48 · Use with care | ★ 2.7k | 3mo ago | MIT |
| Fabric Capacity Manager for .NET ✓ Microsoft · Official | 53 · Use with care | ★ 2.7k | 3mo ago | MIT |
| Azure Bot Service Python Manager ✓ Microsoft · Official | 52 · Use with care | ★ 2.7k | 3mo ago | MIT |
| Azure Playwright Workspace Manager ✓ Microsoft · Official | 54 · 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 the related Microsoft.Bot.Builder package named in the source, this skill focuses on ARM management of Azure Bot resources and channels. Microsoft.Bot.Builder is for building Bot Framework applications; the two can be used together but serve different purposes.
How did FollowSkills review this skill?
The skill documents Azure authentication options, production credential restrictions, Key Vault, managed identity, and DirectLine secure sites, with no evidence of malware or covert exfiltration. However, create, update, key regeneration, and delete operations can cause external effects without user confirmation, least-privilege RBAC guidance, data-flow disclosure, pre-delete backup, or rollback instructions, so points are deducted.
Installation, authentication, resource hierarchy, major CRUD workflows, and a RequestFailedException example are broadly consistent. Nothing was executed, and the skill lacks path-specific tests, input validation, idempotency/concurrency guidance, retry behavior, and stronger diagnostic coverage; SDK/API compatibility is also not proven in the supplied files, so the static cap and uncertainty reduce the score.
The name, description, trigger phrases, .NET SDK scope, and core workflows are reasonably clear. Non-fit cases, input/output boundaries, required permissions, and service limitations are not defined; Chinese-language guidance is absent, and mainland-China network reachability is not evidenced, so points are deducted.
The document has clear sections for installation, environment variables, authentication, workflows, type references, best practices, error handling, related SDKs, MIT licensing, author, and version metadata. It lacks a changelog, explicit maintenance owner and update path, FAQs, known limitations, and source-backed version maintenance; the stated package versions may become stale, so points are deducted.
It covers bot creation, several channel configurations, retrieval, update, key regeneration, and deletion, making the examples potentially useful for common ARM management tasks. Static review found no execution evidence, and important areas such as connection settings, permission setup, pagination/retry, existence handling, and production deployment remain incomplete; generated code therefore requires substantial review and is limited by the static effectiveness cap.
The skill includes NuGet, API, GitHub, and Azure documentation references, while the repository supplies general CI and test infrastructure. The supplied material does not show that this skill's examples compile or run, contains no path-specific committed tests or third-party execution evidence, and does not establish pinned or cross-validated references, so only limited credit is justified.
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 →