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 ...
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill azure-functions45
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
50%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 demonstrates strong technical specificity and clear domain focus on Azure Functions, making it distinctive. However, it critically lacks explicit trigger guidance ('Use when...') and the truncation suggests incomplete content. The technical jargon may not match how users naturally request help with serverless functions.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios like 'Use when building serverless functions on Azure, deploying function apps, or optimizing Azure Functions performance'
Include natural user terms like 'serverless', 'function app', 'Azure serverless', 'timer trigger', 'HTTP trigger' that users commonly say when requesting help
Complete the truncated description to ensure all capabilities are fully stated
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'isolated worker model, Durable Functions orchestration, cold start optimization, and production patterns' with explicit language coverage for '.NET, Python, and Node.js'. | 3 / 3 |
Completeness | Describes what the skill covers but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. The truncation ('...') suggests incomplete content. | 1 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'Azure Functions', 'Durable Functions', 'cold start', and language names, but lacks natural user phrases like 'serverless', 'function app', or 'trigger bindings' that users commonly say. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly targets Azure Functions specifically with distinct terminology like 'isolated worker model' and 'Durable Functions orchestration' - unlikely to conflict with general serverless or other cloud provider skills. | 3 / 3 |
Total | 9 / 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 content is essentially a skeleton or outline with no actionable substance. It lists Azure Functions concepts and anti-patterns but provides zero executable code, no concrete guidance, and appears to have formatting/content errors (the sharp edges table has placeholder 'Issue' text and malformed solutions). The content fails to teach Claude how to actually implement any Azure Functions patterns.
Suggestions
Add executable code examples for each programming model (isolated worker .NET, Node.js v4, Python v2) showing complete, working function implementations
Fix the Sharp Edges table - replace placeholder 'Issue' text with actual issues and provide real solutions instead of what appear to be section headers
Include concrete anti-pattern examples with before/after code showing the problem and the correct approach
Add step-by-step workflows for common tasks like deploying functions, configuring Durable Functions orchestration, or optimizing cold starts with validation checkpoints
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but lacks substance - it's more of a skeleton with headers and table entries that don't provide actual information. The table has placeholder 'Issue' text repeated rather than real content. | 2 / 3 |
Actionability | No concrete code examples, commands, or executable guidance provided. Headers mention patterns like 'Isolated Worker Model' but provide no implementation details, code snippets, or specific instructions. | 1 / 3 |
Workflow Clarity | No workflows are defined. The content lists concepts and anti-patterns but provides no sequenced steps, validation checkpoints, or process guidance for any Azure Functions task. | 1 / 3 |
Progressive Disclosure | Content is poorly organized with incomplete sections. No references to external files for detailed content. The sharp edges table appears malformed with solutions that look like section headers rather than actual solutions. | 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 | |
- 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.