Name: testland/azure-functions-tests
Rating: 72 (1 reviews)
Author: testland

testland/azure-functions-tests

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.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Well-structured, actionable content with a clear multi-step workflow and exemplary progressive disclosure into three focused reference files. The main improvement area is conciseness and adding an explicit error-recovery feedback loop in the workflow.

Suggestions

Tighten the 'Nearest neighbours' paragraph and Limitations prose — state the differentiators and constraints more tersely to reclaim tokens.

Add an explicit error-recovery checkpoint (e.g. 'If `func start` errors on AzureWebJobsStorage, confirm Azurite is running and UseDevelopmentStorage=true is set, then retry') to elevate workflow_clarity.

Surface the per-language unit-test entry points with a one-line command each (e.g. `dotnet test` / `pytest` / `npm test`) inline in step 5 rather than only referencing the file.

Dimension	Reasoning	Score
Conciseness	Mostly lean and assumes Claude's competence (no generic explanations of what a serverless function is), but the nearest-neighbours differentiation paragraph and some Limitations prose could be trimmed slightly.	4 / 5
Actionability	Copy-paste ready commands throughout — `func init ... --worker-runtime dotnet-isolated`, `func new --template ...`, `azurite --silent --location ./azurite-data`, and a full curl admin-endpoint call with headers and body — and the worked example covers the common queue-trigger case end to end.	5 / 5
Workflow Clarity	A clear 7-step 'How to use' sequence with a verification checkpoint in the worked example ('host returns HTTP 202... function logs the processed order'), but there is no explicit error-recovery feedback loop for common failures like Azurite not running or `func start` erroring.	4 / 5
Progressive Disclosure	A concise overview that delegates depth to three real, one-level-deep reference files (local-setup.md, triggering-functions.md, unit-testing-handlers.md), each clearly signaled both inline and in a dedicated 'Reference files' section, with content appropriately split.	5 / 5
	Total	18 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A high-quality description: concrete, third-person, and explicitly covering both what the skill does and when to use it, with a distinct Azure-specific niche. The only minor gap is a few missing natural trigger phrasings.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Runs Azure Functions locally using Azure Functions Core Tools v4 (`func start`)', 'Azurite storage emulation', 'framework-native unit tests for handler code', plus 'admin-endpoint invocation' and 'binding verification via local.settings.json' — giving comprehensive coverage of the domain.	5 / 5
Completeness	Explicitly answers what ('Runs Azure Functions locally... Covers HTTP, queue, and timer trigger testing...') and when ('Use when testing Azure Functions before deployment, reproducing trigger behaviour... or gating function handler logic in CI') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural keywords ('Azure Functions', 'testing Azure Functions before deployment', 'HTTP, queue, and timer trigger', 'CI') with useful synonyms, but a few natural phrasings a user might say (e.g. 'integration test', 'local testing') are not present.	4 / 5
Distinctiveness Conflict Risk	Clear Azure-only niche with distinct triggers ('func start', 'Azurite', '.NET isolated worker model', 'admin-endpoint invocation') that are unlikely to fire for AWS/Cloudflare or integration-test-builder skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Reviewed

19 days ago

Table of Contents

Discovery Implementation Validation