Expert knowledge for Azure Health Bot development including best practices, security, configuration, and integrations & coding patterns. Use when wiring Teams/SMS/WhatsApp channels, embedding web chat, calling external APIs, configuring handoff, or enforcing consent, 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 Functions (use azure-functions).
npx skills add https://github.com/MicrosoftDocs/Agent-Skills --skill azure-health-bot
This skill provides expert guidance for Azure Health Bot. Covers best practices, 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), use read_file with the specified lines. For categories with file links (e.g., security.md), use read_file on the linked reference file
> IMPORTANT for Agent: If metadata.generated_at is more than 3 months old, suggest the user pull the latest version from the repository. If mcp_microsoftdocs tools 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 | L32-L36 | 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. |
| Security | L37-L49 | 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 | L50-L67 | 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 | L68-L89 | 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 |
|-------|-----|
| Configure end-user consent and compliance in healthcare bots | https://learn.microsoft.com/en-us/azure/health-bot/bot_docs/consent |
| Enable end-user deletion of personal data in healthcare bots | https://learn.microsoft.com/en-us/azure/health-bot/bot_docs/deleting_data |
| Allow users to view and export personal data from healthcare bots | https://learn.microsoft.com/en-us/azure/health-bot/bot_docs/viewing_data |
| Configure customer-managed encryption keys for healthcare bots | https://learn.microsoft.com/en-us/azure/health-bot/cmk |
| Monitor and manage abuse in generative healthcare scenarios | https://learn.microsoft.com/en-us/azure/health-bot/copilot/abuse-monitoring |
| Configure health safeguards for generative healthcare agents | https://learn.microsoft.com/en-us/azure/health-bot/copilot/safeguards |
| Configure end-user authentication for Healthcare agent service | https://learn.microsoft.com/en-us/azure/health-bot/end-user-authentication |
| Manage secrets, keys, and endpoints in Healthcare agent service | https://learn.microsoft.com/en-us/azure/health-bot/keys |
| Manage portal user permissions with Microsoft Entra ID | https://learn.microsoft.com/en-us/azure/health-bot/portal-users |
| Topic | URL |
|-------|-----|
| Configure automatic welcome messages in healthcare bots | https://learn.microsoft.com/en-us/azure/health-bot/automatic_welcome_howto |
| Configure scenario cancellation behavior in healthcare agents | https://learn.microsoft.com/en-us/azure/health-bot/bot_docs/cancelling |
| Configure end-user feedback collection in healthcare bots | https://learn.microsoft.com/en-us/azure/health-bot/bot_docs/feedback |
| Configure help command behavior in healthcare agents | https://learn.microsoft.com/en-us/azure/health-bot/bot_docs/help |
| Configure interruptible scenarios in healthcare conversations | https://learn.microsoft.com/en-us/azure/health-bot/bot_docs/interruptions |
| Configure terms and privacy links for healthcare agents | https://learn.microsoft.com/en-us/azure/health-bot/bot_docs/terms |
| Configure interrupting scenarios for healthcare conversations | https://learn.microsoft.com/en-us/azure/health-bot/configuring_interruptions |
| Configure human handoff in healthcare agent service | https://learn.microsoft.com/en-us/azure/health-bot/handoff |
| Configure Microsoft Teams handoff for healthcare bots | https://learn.microsoft.com/en-us/azure/health-bot/handoff-teams |
| Configure and use conversation cards in healthcare bots | https://learn.microsoft.com/en-us/azure/health-bot/scenario-authoring/adding-cards |
| Use and manage instance variables in healthcare scenarios | https://learn.microsoft.com/en-us/azure/health-bot/scenario-authoring/instance-variables |
| Manage and organize healthcare bot scenarios in the portal | https://learn.microsoft.com/en-us/azure/health-bot/scenario-authoring/scenario_management |
| Use scenario snapshots to manage healthcare bot versions | https://learn.microsoft.com/en-us/azure/health-bot/scenario-authoring/snapshots |
| Use resources and static variables in healthcare bot scenarios | https://learn.microsoft.com/en-us/azure/health-bot/tenant-resources |
| Topic | URL |
|-------|-----|
| Configure authentication providers for healthcare bot integrations | https://learn.microsoft.com/en-us/azure/health-bot/authentication_providers |
| Configure Direct Line channel for healthcare agent service | https://learn.microsoft.com/en-us/azure/health-bot/channels/directline |
| Connect healthcare bot to Facebook Messenger and Workplace | https://learn.microsoft.com/en-us/azure/health-bot/channels/facebook |
| Integrate healthcare agent service with Dynamics Omnichannel | https://learn.microsoft.com/en-us/azure/health-bot/channels/oc_channel |
| Connect healthcare agent service to Microsoft Teams | https://learn.microsoft.com/en-us/azure/health-bot/channels/teams |
| Connect healthcare bot to Twilio SMS channel | https://learn.microsoft.com/en-us/azure/health-bot/channels/twilio |
| Embed healthcare agent web chat into web applications | https://learn.microsoft.com/en-us/azure/health-bot/channels/webchat |
| Configure WhatsApp via Twilio for healthcare agent service | https://learn.microsoft.com/en-us/azure/health-bot/channels/whatsapp |
| Integrate healthcare bot telemetry with Application Insights | https://learn.microsoft.com/en-us/azure/health-bot/custom_telemetry |
| Use data connections to call external APIs from healthcare bots | https://learn.microsoft.com/en-us/azure/health-bot/data_connection |
| Use Clinical Safeguards API with Azure Health Agent Service | https://learn.microsoft.com/en-us/azure/health-bot/integrations/clinicalsafeguardsapi |
| Use healthcare agent service management API for automation | https://learn.microsoft.com/en-us/azure/health-bot/integrations/managementapi |
| Invoke healthcare bot scenarios proactively across channels | https://learn.microsoft.com/en-us/azure/health-bot/integrations/proactive |
| Invoke healthcare bot scenarios from client-side JavaScript | https://learn.microsoft.com/en-us/azure/health-bot/integrations/programmatic_invocation |
| Enable voice interactions in healthcare web chat and apps | https://learn.microsoft.com/en-us/azure/health-bot/integrations/voice |
| Extend healthcare scenarios with advanced integration elements | https://learn.microsoft.com/en-us/azure/health-bot/scenario-authoring/advanced_functionality |
| Extend healthcare scenarios with advanced integration elements | https://learn.microsoft.com/en-us/azure/health-bot/scenario-authoring/advanced_functionality |
| Extend healthcare scenarios with advanced integration elements | https://learn.microsoft.com/en-us/azure/health-bot/scenario-authoring/advanced_functionality |
| Extend healthcare scenarios with advanced integration elements | https://learn.microsoft.com/en-us/azure/health-bot/scenario-authoring/advanced_functionality |
Skill converted from mcp-deploy-manage-agents.prompt.md
Use this skill when the user wants to launch a new AltClaw, OpenClaw, PicoClaw, or Ottie deployment through Cloud Claw. Covers the same user-facing fields and constraints exposed in the Cloud Claw UI, using the local altllm cloud-claw-* commands. Do NOT use for post-launch lifecycle tasks like start/stop/delete/logs; use cloud-claw-manage-vm.
Build hosted agents using Azure AI Projects SDK with ImageBasedHostedAgentDefinition. Use when creating container-based agents in Azure AI Foundry.
Build MCP (Model Context Protocol) servers on Cloudflare Workers with tools, resources, and prompts.
Chain agent outputs as inputs in sequential or parallel pipelines for data flow orchestration
Audit cloned or reimplemented websites for fidelity gaps, tracking scripts, source-brand and language residue, placeholders, and risky external dependencies. Use before handoff or deployment, or when asked to review a website clone for cleanup and readiness.
> Install and operate Hermes Tweet, a Hermes Agent plugin for X/Twitter research, timeline reading, tweet analysis, and approval-gated tweet actions. Use this skill when installing Hermes Tweet, researching X/Twitter accounts, monitoring launch signals, investigating mentions, auditing giveaways, or preparing guarded tweet actions. Use proactively when a Hermes Agent workflow needs current X/Twitter context. Requires XQUIK_API_KEY for read and action tools.
Handles LLM-as-judge evaluation workflows on Arize including creating/updating evaluators, running evaluations on spans or experiments, managing tasks, trigger-run operations, column mapping, and continuous monitoring. Use when the user mentions create evaluator, LLM judge, hallucination, faithfulness, correctness, relevance, run eval, score spans, score experiment, trigger-run, column mapping, continuous monitoring, or improve evaluator prompt.
Take microsoftdocs/azure-health-bot from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.