DD azure-openai-to-responses
(no description)
Активируйте этот навык, когда пользователь хочет: python
As a process D 49/100 · Unfinished process — References files that are not bundled: ../../../../../.agents/skills/azure-openai-to-responses/scripts/detect_legacy.py
IntegrationAzureGitHubInfrastructureAI and agentstype and topics are labelled automatically from the skill text
How to improve
- Add a description to the frontmatter: without it the skill never triggers.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
For the model run — optional
- 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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-missingSKILL.md: no `description` — the skill can never trigger - warning
body-longSKILL.md body ≈ 8202 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: ../../../../../.agents/skills/azure-openai-to-responses/scripts/detect_legacy.py - note
edit-residuethe text marks something as outdated (lines 153, 193, 233, 236, 414): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 49/100
Will not run. References files that are not bundled: ../../../../../.agents/skills/azure-openai-to-responses/scripts/detect_legacy.py
- 0Tools and files. 1 referenced file(s) missing: ../../../../../.agents/skills/azure-openai-to-responses/scripts/detect_legacy.py
- 0Result and completion. Does not say what the result is
- 30Running it twice. 26 mutating operations with no state check
- 40Execution cost. Instruction body is 8202 tokens: crowds the task out of the window
- 50When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Failures and branches. 9 branches
- 100Steps. 92 steps
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- low 13 top-level sections: this looks like several domains in one skill
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)
- +3Description length 0: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4Structure: 36 headings
- +3Step-by-step instructions: 92 items
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +1License stated
- +2Bilingual instructions (RU + EN)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 27.