SKILLEMALL.ai

DF azure-openai-to-responses

(no description)

microsoft/ai-agents-for-beginners Agent Skills author: microsoft MIT 4 files body ≈ 6 068 tokens Open the sourcegithub.com↗ analyzed 6 d ago

جب صارف چاہتا ہو تو اس قابلیت کو فعال کریں: python

As a process F 28/100 · No process to follow — References files that are not bundled: ../../../../../.agents/skills/azure-openai-to-responses/scripts/detect_legacy.py

IntegrationAzureGitHubAI and agentsInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
D
70/100
safety, quality, tests
Safety 60%
100
Quality 40%
25
Run on models
none yet
Process rating
F
28/100
No process to follow
References files that are not bundled: ../../../../../.agents/skills/azure-openai-to-responses/scripts/detect_legacy.py
Tools and files w 18
0
Result and completion w 14
0
When it triggers w 12
0
the three weakest of ten parameters · all ten

How to improve

  1. Add a description to the frontmatter: without it the skill never triggers.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  3. 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-missing SKILL.md: no `description` — the skill can never trigger
  • warning body-long SKILL.md body ≈ 6068 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: ../../../../../.agents/skills/azure-openai-to-responses/scripts/detect_legacy.py
  • note edit-residue the text marks something as outdated (lines 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 28/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
  • 0When it triggers. No condition that starts the skill
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 16 mutating operations with no state check
  • 70Execution cost. Instruction body is 6068 tokens
  • 100Steps. 92 steps
  • 100Consistency. Name and required fields are in place
  • 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
  • +2Single-language instructions
  • +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

Quality base 70; lint remarks subtract, signals add up to 100. Result: 25.