Help us improve
Share bugs, ideas, or general feedback.
Shared Azure Functions reference material for the Azure Functions skill suite: runtime/language routing, trigger/binding extension references, official docs and repository pointers. Use only when another Azure Functions skill needs reusable language or binding context. Not intended as a standalone user-facing workflow.
npx claudepluginhub azure/azure-functions-skills --plugin azure-functions-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/azure-functions-skills:azure-functions-commonThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this suite-internal skill as the shared reference pack for Azure Functions skills.
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
Use this suite-internal skill as the shared reference pack for Azure Functions skills.
This skill is intentionally workflow-light. Do not load all references up front. Use routing.md to choose only the runtime/language and trigger/binding reference files needed for the current task.
Shared references include:
references/languages/.references/extensions/.references/local-emulators.md.references/routing.md.Task-specific skills keep their own workflows, scripts, evidence checklists, and output formats. For example, diagnostics owns diagnostic workflow and health evidence rules; this skill only owns reusable Azure Functions reference material.
This is a shared reference skill. Return to the calling Azure Functions skill after loading only the relevant references.
references/local-emulators.md when local E2E verification involves a non-HTTP trigger, service-backed binding, emulator, container, or temporary development resource.