CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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

A well-structured, highly actionable skill body with executable commands, a clear sequenced workflow, and clean one-level-deep progressive disclosure. The main weakness is mild token redundancy (repeated reference links and an inline time-sensitive deprecation date) rather than any gap in guidance.

Suggestions

Remove the standalone 'Reference files' section or merge it into 'How to use' to avoid repeating the same three links twice.

Move the in-process model deprecation date '2026-11-10' into a 'Deprecated' or 'old patterns' note so the time-sensitive detail doesn't penalize conciseness.

Consider condensing the anti-patterns table to the highest-impact rows (e.g. Azurite requirement and admin-endpoint Content-Type) to tighten the token budget.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands and no padding of basics Claude knows, but the 'Reference files' section repeats links already given in 'How to use', the long anti-patterns table adds tokens, and the time-sensitive in-process deprecation date '2026-11-10' sits inline outside a deprecated section — keeping it at the 'could be tightened' level rather than the lean level-3 anchor.

2 / 3

Actionability

Provides fully executable, copy-paste-ready commands (func init/new/start, azurite --silent --location, a complete curl POST with headers and body, a local.settings.json snippet) rather than the incomplete/pseudocode level-2 anchor.

3 / 3

Workflow Clarity

A clearly sequenced 7-step 'How to use' plus a worked example, with verification checkpoints ('Confirm binding config against Azurite') and an anti-patterns table that serves as error-recovery guidance; not the level-2 anchor with missing/implicit checkpoints.

3 / 3

Progressive Disclosure

SKILL.md is a concise overview pointing to three well-signaled, one-level-deep reference files (local-setup.md, triggering-functions.md, unit-testing-handlers.md), all real and non-nested, with content appropriately split for easy navigation.

3 / 3

Total

11

/

12

Passed

Description

100%

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 specific, complete, and distinctive description that names concrete capabilities and explicit 'Use when' triggers for the Azure Functions local-testing niche. Strong across all four dimensions with no notable weaknesses.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Runs Azure Functions locally', 'Azurite storage emulation', 'admin-endpoint invocation for non-HTTP triggers', 'binding verification via local.settings.json'), matching the comprehensive multi-action anchor rather than the partial level-2 anchor.

3 / 3

Completeness

Explicitly answers what ('Runs... Covers...') and when ('Use when testing Azure Functions before deployment, reproducing trigger behaviour... or gating function handler logic in CI'), satisfying the explicit-trigger anchor; not level 2 where 'when' is missing or only implied.

3 / 3

Trigger Term Quality

Covers natural terms a user would say for this domain ('Azure Functions', 'testing', 'before deployment', 'trigger behaviour', 'CI'); coverage is strong rather than the partial level-2 'some relevant keywords but missing common variations'.

3 / 3

Distinctiveness Conflict Risk

Clear niche (Azure Functions local testing via Core Tools v4, Azurite, .NET isolated worker model) with distinct triggers unlikely to fire for sibling serverless skills; not the overlap-prone level-2 anchor.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents