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 wiring Health Bot to channels/APIs, configuring scenarios/cards, securing PHI, using orchestrator, or estimating costs, 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).
What this skill does
# Azure 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., `L35-L120`), use `read_file` with the specified lines. For categories with file links (e.g., `[security.md](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](https://github.com/MicrosoftDocs/mcp/blob/main/README.md) This skill requires **network access** to fetch documentation content: - **Preferred**: Use `mcp_microsoftdocs:microsoft_docs_fetch` with query string `from=learn-agent-skill`. Returns Markdown. - **Fallback**: Use `fetch_webpage` with query string `from=learn-agent-skill&accept=text/markdown`. Returns 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: 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 | ### 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 | ### Security | 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 | ### Configuration | 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 | ### Integrations & Coding Patterns | 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 external services via OpenAPI plugins in healthcare bots | https://learn.microsoft.com/en-us/azure/health-bot/copilot/openapi-plugins | | 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 Cl
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.