Agent-Skills azure-health-bot
Expert knowledge for Azure Health Bot development including best practices, decision making, architecture & design patterns, security, configuration, and integrations & coding patterns. Use when configuring Health Bot channels, web chat/voice embeds, management APIs, orchestrator flows, or cost estimation, and other Azure Health Bot related development tasks. Not for Azure AI Bot Service (use azure-bot-service), Azure Communication Services (use azure-communication-services), Azure Health Data Services (use azure-health-data-services).
git clone https://github.com/MicrosoftDocs/Agent-Skills
T=$(mktemp -d) && git clone --depth=1 https://github.com/MicrosoftDocs/Agent-Skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/azure-health-bot" ~/.claude/skills/microsoftdocs-agent-skills-azure-health-bot && rm -rf "$T"
skills/azure-health-bot/SKILL.mdAzure Health Bot 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.
How to Use This Skill
IMPORTANT for Agent: Use the Category Index below to locate relevant sections. For categories with line ranges (e.g.,
), useL35-L120with the specified lines. For categories with file links (e.g.,read_file), use[security.md](security.md)on the linked reference fileread_file
IMPORTANT for Agent: If
is more than 3 months old, suggest the user pull the latest version from the repository. Ifmetadata.generated_attools are not available, suggest the user install it: Installation Guidemcp_microsoftdocs
This skill requires network access to fetch documentation content:
- Preferred: Use
with query stringmcp_microsoftdocs:microsoft_docs_fetch
. Returns Markdown.from=learn-agent-skill - Fallback: Use
with query stringfetch_webpage
. Returns Markdown.from=learn-agent-skill&accept=text/markdown
Category Index
| 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: consent, data export/deletion, auth, encryption keys, abuse safeguards, secrets/keys, and portal access control for healthcare bots. |
| 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 |
Best Practices
| Topic | URL |
|---|---|
| Design error handling flows in healthcare bot scenarios | https://learn.microsoft.com/en-us/azure/health-bot/errorhandling |
Decision Making
| Topic | URL |
|---|---|
| Estimate healthcare agent service costs by action usage | https://learn.microsoft.com/en-us/azure/health-bot/pricing-details |
Architecture & Design Patterns
| Topic | URL |
|---|---|
| Use the healthcare orchestrator to route plugins and flows | https://learn.microsoft.com/en-us/azure/health-bot/copilot/orchestrator |