CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-openai-to-responses

Migrate Python apps from Azure OpenAI Chat Completions to the Responses API. Covers AzureOpenAI/AsyncAzureOpenAI client migration to the v1 endpoint, streaming, tools, structured output, multi-turn, EntraID auth, and model compatibility checks. Python-focused, Azure OpenAI-specific. USE FOR: migrate to responses API, switch from chat completions, openai responses, upgrade openai SDK, responses API migration, move from completions to responses, gpt-5 migration, azure openai python migration, chat completions to responses, AzureOpenAI to OpenAI client, python azure openai upgrade. DO NOT USE FOR: building new apps from scratch (start with responses directly), Node/TypeScript/C#/Java/Go migrations (this skill is Python-only), Azure infrastructure setup (use azure-prepare), deploying models (use microsoft-foundry).

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, actionable, well-sequenced migration skill with excellent progressive disclosure and validation gates. Its only weakness is length and internal redundancy across the model-compatibility and parameter-mapping sections, which could be consolidated to improve token efficiency.

Suggestions

Consolidate the model-constraint material so each parameter rule (temperature, max_output_tokens, seed, top_p, reasoning) appears in one canonical location instead of being repeated across the older-models, o-series, and migration-notes sections.

Reduce the parameter-mapping duplication by keeping the authoritative mapping table and trimming the overlapping prose in 'Migration notes' and the 'Heuristics' list to pointers rather than restatements.

Move the long block of `rg` search patterns to detect_legacy.py's documentation or cheat-sheet.md, keeping only the canonical few in SKILL.md to shorten the body.

DimensionReasoningScore

Conciseness

The body is dense and largely avoids explaining concepts Claude already knows, but at ~430 lines it carries redundancy — model constraints appear in the older-models, o-series, and migration-notes sections, and the parameter mapping repeats across the table, Step 2 notes, and heuristics — so it could be tightened rather than padding.

2 / 3

Actionability

Provides copy-paste-ready executable code (smoke test), concrete `rg` search commands, before/after tables, and a full parameter-mapping table — matching the fully-executable anchor.

3 / 3

Workflow Clarity

Sequenced Step 0 → Step 1 (detect) → Step 2 (apply) with explicit validation checkpoints (code-level, test-infrastructure, and behavioral acceptance gates) and a smoke-test feedback loop, matching the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

SKILL.md is an overview pointing one level deep to real, clearly-signaled bundle files — cheat-sheet.md, test-migration.md, troubleshooting.md, and detect_legacy.py — all of which exist, with a consolidated References section, matching the well-signaled reference anchor.

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A high-quality description: it states concrete capabilities, provides rich natural trigger terms, answers both 'what' and 'when', and includes explicit negative triggers to avoid conflicts with sibling skills.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'client migration to the v1 endpoint, streaming, tools, structured output, multi-turn, EntraID auth, and model compatibility checks' — matching the anchor for listing several specific capabilities, rather than the partial domain-only anchor below.

3 / 3

Completeness

It explicitly states what ('Migrate Python apps from Azure OpenAI Chat Completions to the Responses API') and when via explicit 'USE FOR:' and 'DO NOT USE FOR:' clauses, satisfying both halves of the top anchor.

3 / 3

Trigger Term Quality

The 'USE FOR:' list supplies natural phrasings a user would say ('switch from chat completions', 'gpt-5 migration', 'chat completions to responses', 'azure openai python migration') with broad keyword coverage matching the good natural-terms anchor.

3 / 3

Distinctiveness Conflict Risk

'Python-focused, Azure OpenAI-specific' plus a 'DO NOT USE FOR' clause redirecting Node/infra/deploy cases to azure-prepare and microsoft-foundry gives it a clear niche unlikely to trigger the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
microsoft/ai-agents-for-beginners
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.