azure-functions
Modern .NET execution model with process isolation
28
11%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/azure-functions/SKILL.mdQuality
Discovery
7%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 extremely vague and reads more like a technical concept label than a skill description. It lacks concrete actions, natural trigger terms, and any explicit guidance on when Claude should select this skill. Without knowing what the skill actually does or when to use it, Claude would struggle to appropriately select it from a list of available skills.
Suggestions
Replace the abstract phrase with concrete actions, e.g., 'Runs .NET applications using modern hosting with process isolation, manages dotnet build/run/publish commands, and configures application hosting.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about running .NET apps, dotnet CLI commands, C# project execution, or application hosting configuration.'
Include common user-facing keywords like 'C#', 'dotnet', 'build', 'run', 'deploy', '.csproj', or 'ASP.NET' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses abstract, technical language ('execution model', 'process isolation') without listing any concrete actions. It does not describe what the skill actually does—no verbs like 'build', 'run', 'deploy', or 'test'. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no 'Use when...' clause and the 'what' is extremely vague—it describes a concept rather than a capability. | 1 / 3 |
Trigger Term Quality | The terms 'execution model' and 'process isolation' are technical jargon that users would rarely use in natural requests. Common terms like '.NET', 'C#', 'dotnet run', 'build', or 'compile' are mostly absent or buried in jargon. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of '.NET' and 'process isolation' provides some domain specificity that narrows the scope, but 'execution model' is vague enough to overlap with other .NET-related or general runtime skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
14%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a skeleton or outline with no substantive content. It lists patterns, anti-patterns, and sharp edges as headings and table rows but provides no actual instructions, code examples, or actionable guidance. The sharp edges table contains placeholder 'Issue' text repeated for every row, and the 'When to Use' section is a generic boilerplate sentence.
Suggestions
Add concrete, executable code examples for each pattern (Isolated Worker, Node.js v4, Python v2) showing function definitions, bindings, and deployment commands.
Replace placeholder 'Issue' entries in the sharp edges table with specific, real issues (e.g., 'Cold start latency', 'Binding configuration errors') and provide actionable solutions with code snippets.
Add a clear workflow section with sequenced steps for creating, testing, and deploying an Azure Function, including validation checkpoints (e.g., local testing with func start, deployment verification).
Either flesh out the anti-patterns with concrete bad/good code comparisons, or link to separate reference files for detailed guidance on each pattern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but much of it is placeholder-like (e.g., repeated 'Issue' in the table, generic headings without substance). It doesn't over-explain concepts Claude knows, but the content that exists is largely empty shells rather than efficient, meaningful instruction. | 2 / 3 |
Actionability | There is no concrete code, no executable commands, no specific examples, and no actual instructions. The headings and table entries are vague labels ('Issue', 'Use async pattern with Durable Functions') without any implementation details or copy-paste ready guidance. | 1 / 3 |
Workflow Clarity | There are no sequenced steps, no workflows, and no validation checkpoints. The content is a collection of headings and a table with placeholder values, providing no clear process for Claude to follow. | 1 / 3 |
Progressive Disclosure | The content is a flat list of headings and a table with no references to detailed files, no navigation structure, and no meaningful organization beyond section headers. There are no links to deeper content or well-signaled references. | 1 / 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
d739c8b
- 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.