CF azure-openai-to-responses
Ilipat ang mga Python app mula sa Azure OpenAI Chat Completions papuntang Responses API. Saklaw nito ang pag-migrate ng AzureOpenAI/AsyncAzureOpenAI client sa v1 endpoint, streaming, tools, structured output, multi-turn, EntraID auth, at mga pagsusuri sa compatibility ng modelo. Nakatuon sa Python, para sa Azure OpenAI. GAMITIN PARA SA: pag-migrate sa responses API, paglipat mula sa chat completions, openai responses, pag-upgrade ng openai SDK, migration sa responses API, paglipat mula completions sa responses, gpt-5 migration, azure openai python migration, chat completions papuntang responses, AzureOpenAI papuntang OpenAI client, python azure openai upgrade. HUWAG GAMITIN PARA SA: paggawa ng mga bagong app mula sa simula (simulan direkta sa responses), Node/TypeScript/C#/Java/Go migrations (Python lang ang kasanayang ito), Azure infrastructure setup (gumamit ng azure-prepare), pag-deploy ng mga modelo (gumamit ng microsoft-foundry).
Ilipat ang mga Python app mula sa Azure OpenAI Chat Completions papuntang Responses API.
As a process F 29/100 · No process to follow — References files that are not bundled: ../../../../../.agents/skills/azure-openai-to-responses/scripts/detect_legacy.py
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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.
- 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
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 6780 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 119, 151, 153, 171, 193, 231): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 29/100
- 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
- 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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 22 mutating operations with no state check
- 70Execution cost. Instruction body is 6780 tokens
- 85Steps. 92 steps, 1 vague phrases
- 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 948: 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: 58.