azure-functions

Expert patterns for Azure Functions development including isolated worker model, Durable Functions orchestration, cold start optimization, and production patterns. Covers .NET, Python, and Node.js programming models.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/azure-functions/SKILL.md

Quality

Content

63%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.

The body is a well-structured overview with exemplary progressive disclosure: one real reference, clearly linked, with instructions on when to read it fully. Its weaknesses are redundancy (verbatim description restatement and repetitive trigger bullets) and the absence of any substantive actionable content or workflow summary in the body itself.

Suggestions

Drop the verbatim restatement of the frontmatter description from the body to save tokens without losing information.

Collapse the 'When to Use' list into a single line (e.g. 'Use when the user mentions Azure Functions, function apps, Durable Functions, or Azure serverless') and remove the singular/plural duplicate.

Surface 2-3 key workflow steps or sharp edges (e.g. the 230-second HTTP timeout, HttpClient reuse) from the guide so the body carries minimal actionable context, not just a pointer.

Dimension	Reasoning	Score
Conciseness	The body restates the frontmatter description verbatim ('Expert patterns for Azure Functions development including isolated worker model...') and repeats 'User mentions or implies:' five times, including a singular/plural duplicate ('azure function' / 'azure functions') that could be collapsed to one line.	3 / 5
Actionability	The single directive is concrete ('Read [the detailed guide](references/detailed-guide.md) before executing this skill... Treat its safety, prerequisites, and validation requirements as mandatory'), but all executable substance is delegated and no key commands, patterns, or steps are surfaced in the body itself.	3 / 5
Workflow Clarity	The single action is unambiguous (read the guide first, treat its requirements as mandatory) and the skill is neither destructive nor batch, but the actual execution sequence and validation checkpoints live entirely in the reference with no summary in the body.	4 / 5
Progressive Disclosure	A clean overview body with one clearly signaled, verified, one-level-deep reference (references/detailed-guide.md, 1356 lines with its own section headers) plus explicit guidance on reading sections selectively versus in full — a textbook match for anchor 5.	5 / 5
	Total	15 / 20 Passed

Description

61%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.

The description clearly scopes a distinct Azure Functions domain with good natural keyword coverage, but it reads as a topic inventory rather than a statement of concrete actions and lacks any explicit 'when to use' trigger guidance. Adding a 'Use when...' clause with trigger phrases and action-oriented verbs would lift both completeness and specificity.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions Azure Functions, function apps, Durable Functions, or Azure serverless workloads.'

Replace topic nouns with concrete actions (e.g. 'Implement, debug, and optimize Azure Functions...') so the description states what the skill does, not just what it covers.

Include missing natural trigger terms such as 'function app', 'serverless', and 'F#' to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain plus four concrete sub-topics ('isolated worker model, Durable Functions orchestration, cold start optimization, and production patterns') but is a topic list with no action verbs, matching anchor 3's level of concreteness rather than anchor 4's specific actions.	3 / 5
Completeness	Has a clear 'what' ('Expert patterns for Azure Functions development including...') but no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('Azure Functions', 'Durable Functions', '.NET, Python, and Node.js', 'cold start') but misses common variations like 'serverless', 'function app', and 'F#'.	4 / 5
Distinctiveness Conflict Risk	'Azure Functions' and 'Durable Functions' form a clear niche with minimal conflict risk, but 'production patterns' is generic and there is minor overlap risk with general Azure or .NET skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/agentic-awesome-skills
Path: skills/azure-functions/SKILL.md
Commit: 7b534bc

Reviewed: 8 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.