CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-functions

Modern .NET execution model with process isolation

22

Quality

11%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

14%Scale 1-3

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

This skill appears to be a template or incomplete draft rather than a functional skill document. It has structural elements (patterns, anti-patterns, sharp edges table) but lacks actual content - anti-pattern sections are empty, the sharp edges table contains placeholder 'Issue' text, and there are no code examples or concrete guidance for working with Azure Functions.

Suggestions

Add concrete code examples for each programming model (Isolated Worker, Node.js v4, Python v2) showing basic function setup and configuration

Complete the anti-patterns sections with actual problematic code examples and their corrections

Fix the sharp edges table - replace placeholder 'Issue' text with actual issues and provide real solutions with code snippets instead of markdown headers

Add workflow guidance for common tasks like deploying functions, configuring bindings, or debugging locally

DimensionReasoningScore

Conciseness

The content is relatively brief but contains placeholder/template text ('Issue' repeated in table) and section headers without content (anti-patterns have headers but no explanations). Some unnecessary repetition in the sharp edges table.

2 / 3

Actionability

No concrete code examples, commands, or executable guidance provided. Anti-patterns sections are empty headers. Sharp edges table lists solutions as headers ('## Use async pattern') rather than actual implementation details or code.

1 / 3

Workflow Clarity

No clear workflows or sequences defined. The patterns section lists model names without explaining how to use them. No validation steps or process guidance for any Azure Functions operations.

1 / 3

Progressive Disclosure

Content appears incomplete with placeholder text. No references to external files for detailed information. The structure exists (Patterns, Anti-Patterns, Sharp Edges) but sections are either empty or contain malformed content.

1 / 3

Total

5

/

12

Passed

Description

7%Scale 1-3

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

This description is severely lacking in actionable detail. It reads more like a technical architecture note than a skill description, providing no concrete actions, no trigger terms users would naturally use, and no guidance on when to apply the skill. The description fails to help Claude distinguish when to select this skill from alternatives.

Suggestions

Add specific concrete actions the skill performs (e.g., 'Runs .NET applications, executes C# code, manages dotnet CLI commands')

Include a 'Use when...' clause with natural trigger terms like 'run C#', 'execute .NET', 'dotnet build', 'compile C#', '.csproj'

Clarify what 'process isolation' means in practical terms - what user problem does this solve?

DimensionReasoningScore

Specificity

The description uses abstract technical language ('execution model', 'process isolation') without describing any concrete actions. It doesn't explain what the skill actually does - no verbs indicating capabilities.

1 / 3

Completeness

Missing both 'what' and 'when'. The description doesn't explain what actions the skill performs or when Claude should use it. No 'Use when...' clause or equivalent trigger guidance.

1 / 3

Trigger Term Quality

Contains technical jargon ('execution model', 'process isolation') that users would rarely say naturally. Missing common terms like 'run', 'execute', 'C#', 'dotnet run', or specific .NET actions users would request.

1 / 3

Distinctiveness Conflict Risk

'.NET' provides some specificity to the technology domain, but 'execution model' is vague enough to potentially overlap with other .NET-related skills or general code execution skills.

2 / 3

Total

5

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

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.