BB 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 programming models.
The skill promises Azure Functions patterns: isolated worker model, Durable Functions, cold start optimization, production patterns for .NET, Python, and Node.js. Two files in the folder, no critical errors. Quality score 84 shows clear instructions, but process score 67 signals structural gaps.
No sandbox runs, no model testing. Code examples haven't been validated—outdated snippets or typos are likely, especially problematic for production patterns. Compatible with all major platforms, which helps, but doesn't offset missing validation. Skip it if you need tested, current code.
Expert patterns for Azure Functions development including isolated worker model, Durable Functions orchestration, cold start optimization, and production…
As a process B 67/100 · Nearly there — weak spots: result and completion, when it triggers, failures and branches
The same skill appears in 1 more place: agentic-awesome-skills
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 67/100
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Result and completion. Does not say what the result is
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 8 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 281 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 216: enough signal without eating the budget
- +4Structure: 4 headings
- +3Step-by-step instructions: 8 items
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.