CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-functions

Modern .NET execution model with process isolation

31

Quality

25%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/azure-functions/SKILL.md

The canonical home for this skill is azure-functions in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

33%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 structurally organized into reasonable sections but is substantively hollow: anti-pattern headings have no content, the Sharp Edges table is filled with literal 'Issue' placeholders and solution cells that are heading fragments, and there is no executable code, command sequence, or validation guidance. It reads as an unfinished template rather than a working skill.

Suggestions

Replace the placeholder Sharp Edges table with real issue names, severities, and concrete solutions (commands or code snippets) instead of repeated 'Issue' cells and '## ...' heading fragments.

Add executable examples for each pattern, e.g. an isolated worker function skeleton and an IHttpClientFactory registration snippet, to lift actionability above high-level hints.

Provide a sequenced workflow with validation checkpoints for at least one common task (e.g. creating a new isolated-worker function project and verifying it runs locally), so the steps form an ordered, verifiable process.

DimensionReasoningScore

Conciseness

The body is mostly lean, but tokens are wasted on placeholder table rows where every Issue cell reads 'Issue' and Solution cells contain heading fragments like '## Use async pattern...', matching 'Mostly efficient but includes some unnecessary explanation or could be tightened'.

3 / 5

Actionability

It offers only high-level hints (e.g. 'Use IHttpClientFactory', 'Use isolated worker for new projects') with no code, commands, or concrete steps, matching 'Minimal concrete guidance; high-level hints but missing the specific steps to execute'.

2 / 5

Workflow Clarity

There is no sequenced workflow or validation checkpoints anywhere in the body; the Patterns, Anti-Patterns, and Sharp Edges sections are a flat taxonomy rather than ordered steps, matching 'Steps missing or incoherent; no sequence'.

1 / 5

Progressive Disclosure

The skill is under 50 lines with no external references and is organized into clearly labeled sections (Patterns, Anti-Patterns, Sharp Edges, When to Use), giving it good structure despite the malformed table, matching 'Good structure; most content is appropriately placed'.

4 / 5

Total

10

/

20

Passed

Description

17%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 is a terse technical label rather than a usable skill description: it names a domain but gives no concrete actions, no natural trigger terms, and no 'when to use' guidance. It is third-person and free of first-person voice issues, but scores low across all dimensions for its lack of actionable, distinguishable content.

Suggestions

Rewrite the description to list concrete actions, e.g. 'Build and deploy Azure Functions using the .NET isolated worker model, configure bindings, and set up Durable Functions.'

Add a 'Use when...' clause with natural trigger terms users would say, such as 'Azure Functions', 'serverless .NET', 'function app', or 'isolated worker'.

Make the skill distinct from general .NET skills by foregrounding Azure Functions-specific terminology and the isolated worker model rather than the generic 'process isolation' phrasing.

DimensionReasoningScore

Specificity

The phrase 'Modern .NET execution model with process isolation' names the domain but offers no concrete actions, matching the anchor 'Names the domain but actions are minimal or generic' and falling well below the level-3 anchor which requires 1-2 concrete actions.

2 / 5

Completeness

A vague 'what' is present but there is no 'when' or 'Use when...' clause, matching 'Has a vague what and no when'; per the judging guideline a missing Use-when clause caps completeness at 3, and this is below that bar.

2 / 5

Trigger Term Quality

It contains only technical jargon ('process isolation', '.NET execution model') with no natural terms a user would actually say such as 'Azure Functions', 'serverless', or 'function app', matching the 'No natural keywords; only technical jargon' anchor.

1 / 5

Distinctiveness Conflict Risk

The terse, generic phrasing is very broad and would overlap with many other .NET skills, matching 'Very broad; high overlap risk' rather than the more specific level-3 anchor.

2 / 5

Total

7

/

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
administrakt0r/AI-Agents-Safe-Coding-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.