CD testing-course-samples
Tumia wakati unapoombwa kuthibitisha, kujaribu, kufanya mtihani wa haraka, au kuendesha daftari la kozi na mifano ya msimbo dhidi ya usanidi hai wa Microsoft Foundry / Azure OpenAI. Inajumuisha usanidi wa mazingira (.env, az login, vifurushi), mchezaji wa scripts/validate-notebooks.ps1, kutafsiri matokeo ya PASS/FAIL, na ni masomo yapi yanayohitaji rasilimali za ziada (Azure AI Search, GitHub MCP, Foundry Local, Playwright).
Tumia wakati unapoombwa kuthibitisha, kujaribu, kufanya mtihani wa haraka, au kuendesha daftari la kozi na mifano ya msimbo dhidi ya usanidi hai wa Microsoft…
As a process D 38/100 · Unfinished process — References files that are not bundled: ../../../../../scripts/validate-notebooks.ps1, ../../../tests/README.md, ../../../../../.env.example
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: ../../../../../scripts/validate-notebooks.ps1 - warning
missing-refreference to a missing file: ../../../tests/README.md - warning
missing-refreference to a missing file: ../../../../../.env.example - warning
missing-refreference to a missing file: scripts/validate-notebooks.ps1
Process rating: all ten parameters 38/100
- 0Tools and files. 4 referenced file(s) missing: ../../../../../scripts/validate-notebooks.ps1, ../../../tests/README.md, ../../../../../.env.example
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 13 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1236 tokens
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
- +1No license
- +2Single-language instructions
- +3Description length 428: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 13 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.