azure-functions
tessl i github:sickn33/antigravity-awesome-skills --skill azure-functionsExpert 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. Use when: azure function, azure functions, durable functions, azure serverless, function app.
Validation
63%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 10 / 16 Passed | |
Implementation
15%This skill content appears to be an incomplete template or skeleton rather than a functional skill. It lacks any executable code, concrete examples, or actual guidance - just placeholder headings and a malformed table with 'Issue' repeated in the Issue column and markdown headers in the Solution column. The content fails to teach Claude anything actionable about Azure Functions.
Suggestions
Add complete, executable code examples for each programming model (isolated worker, Node.js v4, Python v2) showing actual function implementations
Replace the placeholder 'Issue' entries in the sharp edges table with actual issues (e.g., 'Cold start latency', 'Connection exhaustion') and provide concrete solution code, not just headers
Include specific anti-pattern examples with before/after code showing the wrong approach and the correct fix
Add a quick start section with a minimal working function example that can be copy-pasted
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is brief but too sparse - it lists concepts without explanation, which is different from being efficiently concise. The table format is token-efficient but the content itself is incomplete. | 2 / 3 |
Actionability | No executable code, commands, or concrete examples provided. Only vague labels like 'Modern .NET execution model' and solutions like '## Use async pattern' without any actual implementation guidance. | 1 / 3 |
Workflow Clarity | No workflows defined. The sharp edges table mentions solutions but provides no steps, sequences, or validation checkpoints. The solutions column contains markdown headers instead of actual instructions. | 1 / 3 |
Progressive Disclosure | Content appears to be a broken or incomplete skeleton. No references to external files, no clear navigation structure, and the table appears malformed with repeated 'Issue' placeholders instead of actual content. | 1 / 3 |
Total | 5 / 12 Passed |
Activation
100%This is a well-crafted skill description that excels across all dimensions. It provides specific technical capabilities, includes an explicit 'Use when:' clause with natural trigger terms, and carves out a distinct niche for Azure Functions development that won't conflict with other cloud or serverless skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'isolated worker model, Durable Functions orchestration, cold start optimization, and production patterns' plus coverage of specific programming models (.NET, Python, Node.js). | 3 / 3 |
Completeness | Clearly answers both what (expert patterns for Azure Functions including specific capabilities) AND when (explicit 'Use when:' clause with trigger terms). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'azure function, azure functions, durable functions, azure serverless, function app' - these are exactly what developers would type when seeking help with Azure Functions. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on Azure Functions with distinct triggers like 'durable functions', 'function app', and 'azure serverless' - unlikely to conflict with general cloud or serverless skills. | 3 / 3 |
Total | 12 / 12 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.