Stats
Actions
Tags
From azure-agent-skills
Provides expert guidance for Azure Health Bot development: best practices, architecture, security, configuration, integrations, and cost estimation. Use when wiring bots to channels/APIs, configuring scenarios, securing PHI, or using the healthcare orchestrator.
How this skill is triggered — by the user, by Claude, or both
Slash command
/azure-agent-skills:azure-health-botThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill provides expert guidance for Azure Health Bot. Covers best practices, decision making, architecture & design patterns, security, configuration, and integrations & coding patterns. It combines local quick-reference content with remote documentation fetching capabilities.
This skill provides expert guidance for Azure Health Bot. Covers best practices, decision making, architecture & design patterns, security, configuration, and integrations & coding patterns. It combines local quick-reference content with remote documentation fetching capabilities.
IMPORTANT for Agent: Use the Category Index below to locate relevant sections. For categories with line ranges (e.g.,
L35-L120), useread_filewith the specified lines. For categories with file links (e.g.,[security.md](security.md)), useread_fileon the linked reference file
IMPORTANT for Agent: If
metadata.generated_atis more than 3 months old, suggest the user pull the latest version from the repository. Ifmcp_microsoftdocstools are not available, suggest the user install it: Installation Guide
This skill requires network access to fetch documentation content:
mcp_microsoftdocs:microsoft_docs_fetch with query string from=learn-agent-skill. Returns Markdown.fetch_webpage with query string from=learn-agent-skill&accept=text/markdown. Returns Markdown.| Category | Lines | Description |
|---|---|---|
| Best Practices | L34-L38 | Guidance on designing robust error-handling flows in Azure Health Bot scenarios, including detecting failures, user-friendly recovery paths, and safe handling of clinical conversation errors. |
| Decision Making | L39-L43 | Estimating Azure Health Bot costs based on action usage, understanding pricing drivers, and forecasting expenses for different bot scenarios. |
| Architecture & Design Patterns | L44-L48 | Designing bot architectures using the healthcare orchestrator to route between plugins and flows, manage conversation logic, and structure complex healthcare scenarios |
| Security | L49-L61 | Configuring security, privacy, and compliance: user consent, data access/deletion, encryption keys, abuse safeguards, authentication, secrets management, and portal permissions for Healthcare bots/agents. |
| Configuration | L62-L79 | Configuring bot behavior and conversations: welcome/help messages, feedback, interruptions, human/Teams handoff, terms links, and managing scenarios, variables, cards, and versions. |
| Integrations & Coding Patterns | L80-L102 | Connecting Health Bot/Agent to channels (Teams, SMS, WhatsApp, Facebook), embedding web chat/voice, calling external APIs/OpenAPI, telemetry, auth, management APIs, and proactive scenario invocation |
| Topic | URL |
|---|---|
| Design error handling flows in healthcare bot scenarios | https://learn.microsoft.com/en-us/azure/health-bot/errorhandling |
| Topic | URL |
|---|---|
| Estimate healthcare agent service costs by action usage | https://learn.microsoft.com/en-us/azure/health-bot/pricing-details |
| Topic | URL |
|---|---|
| Use the healthcare orchestrator to route plugins and flows | https://learn.microsoft.com/en-us/azure/health-bot/copilot/orchestrator |
npx claudepluginhub microsoftdocs/agent-skills --plugin azure-agent-skillsProvides expert guidance for Azure AI Bot Service development including troubleshooting, architecture, security, and deployment patterns for bots using Direct Line, Teams, OAuth/SSO, and proactive messaging.
Manages Azure Bot Service resources including bots, channels, and connections using Python SDK. Use for creating, listing, updating, and deleting bots.
Routes Azure tasks to the right specialist agent from a catalog. Classifies tasks into domains (architecture, containers, database, etc.) and dispatches single agents or parallel teams. Does not answer Azure questions itself.