CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/azure-functions/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 exemplary for progressive disclosure and conciseness, acting as a clean overview that defers detail to a real reference file. Actionability and workflow clarity are weaker because the body contains no executable steps or validation checkpoints, relying entirely on the referenced guide.

Suggestions

Include a short Quick Start snippet (one minimal trigger example) in the body so the skill is actionable without loading the full guide.

Add an explicit end-to-end workflow with a validation checkpoint (e.g., deploy, then verify with `func azure functionapp list-functions`) for at least one common path.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: overview, a single signaled reference, When-to-Use, and Limitations, with no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

The body itself provides no executable code or commands, delegating all concrete guidance to detailed-guide.md; the referenced guide carries the actionable material, but the SKILL.md body is mostly pointer text.

3 / 5

Workflow Clarity

There is no multi-step process with validation checkpoints in the body; the Limitations section references validation generally, but explicit sequencing and feedback loops are absent.

3 / 5

Progressive Disclosure

A clear overview points to a single, well-signaled, one-level-deep reference (references/detailed-guide.md) that exists as a real file, with content appropriately split and easy navigation.

5 / 5

Total

16

/

20

Passed

Description

70%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 conveys what the skill covers with concrete Azure Functions capabilities and good trigger terms, but lacks an explicit 'when to use' clause, capping completeness. It is distinctive and unlikely to fire for the wrong skill.

Suggestions

Add an explicit 'Use when ...' clause to the description naming user-facing triggers (e.g., 'Use when working with Azure Functions, durable orchestration, or serverless function apps').

Surface common trigger synonyms like 'serverless' or 'function app' in the description rather than only in the body's When-to-Use list.

DimensionReasoningScore

Specificity

Names the domain plus several concrete capabilities ('isolated worker model, Durable Functions orchestration, cold start optimization, and production patterns') and language models, with only minor coverage gaps.

4 / 5

Completeness

A clear 'what' is present but there is no explicit 'Use when...' clause in the description itself, which caps completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

Includes natural terms users say ('Azure Functions', 'Durable Functions', 'isolated worker') with good coverage; a few common synonyms ('serverless', 'function app') live in the body rather than the description.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Azure Functions, isolated worker, Durable Functions) with distinct triggers and minimal overlap risk with unrelated skills.

5 / 5

Total

16

/

20

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
sickn33/agentic-awesome-skills
Reviewed

Table of Contents

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.