Runs Azure Functions locally using Azure Functions Core Tools v4 (`func start`), Azurite storage emulation, and framework-native unit tests for handler code (.NET isolated worker model, Node.js v4, Python v2). Covers HTTP, queue, and timer trigger testing, admin-endpoint invocation for non-HTTP triggers, and binding verification via local.settings.json. Use when testing Azure Functions before deployment, reproducing trigger behaviour without live Azure services, or gating function handler logic in CI.
74
93%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
The CI and setup snippets fetch and install runtime components from external locations — notably https://packages.microsoft.com/keys/microsoft.asc and https://packages.microsoft.com/repos/microsoft-ubuntu-$(lsb_release -cs)-prod (used to install Azure Functions Core Tools in CI) and mcr.microsoft.com/azure-storage/azurite (Docker image for Azurite) — which will download and execute remote code required by the skill.