Skip to content

laguagu/claude-code-nextjs-skills / skills/openai-agents-sdk

openai-agents-sdk

Verified

OpenAI Agents SDK (Python) development. Use when building AI agents, multi-agent handoffs, function tools, guardrails, sessions, streaming, or tracing with the `openai-agents` / `agents` Python package — including Azure OpenAI through its native client or LiteLLM. Triggers on imports from `agents`, uses of `Runner.run_sync`/`Runner.run_streamed`, `@function_tool`, `AgentOutputSchema`, `SQLiteSession`, or questions about the openai-agents-python SDK. Python only — not the TypeScript `@openai/agents` SDK.

FileKindSize
SKILL.mdskill md5.9 KB
references/guardrails.mdmarkdown1.8 KB
references/handoffs.mdmarkdown1.4 KB
references/patterns.mdmarkdown1.5 KB
references/providers.mdmarkdown2.8 KB
references/sandbox.mdmarkdown1.5 KB
references/sessions.mdmarkdown1.6 KB
references/streaming.mdmarkdown1.5 KB
references/structured-output.mdmarkdown838 B
references/tools.mdmarkdown3.0 KB

references/providers.md

View on GitHub
# Agents and provider wiring

Read [model docs](https://openai.github.io/openai-agents-python/models/) and the
installed package source. Omitting `model` uses SDK defaults, which can change
(0.24.0 fallback: `gpt-5.6-luna`, not a model recommendation);
`OPENAI_DEFAULT_MODEL` is an SDK setting, while a
custom app variable needs explicit wiring. Tuned default ModelSettings apply
in 0.24.0 only to supported `gpt-5` names; other IDs, including `gpt-6.1-sol`, get a
plain `ModelSettings()` and the API's default reasoning effort, so set
`reasoning` explicitly. The installed `agents/models/default_models.py` shows
the current rules.

Configure only settings supported by the selected provider/model. Reasoning,
sampling and tool support differ by endpoint. Do not infer capabilities or a
model family from an Azure deployment's user-defined name.

Azure can use native OpenAI model classes with an `AsyncAzureOpenAI` client:
per agent via `OpenAIResponsesModel` or
`OpenAIChatCompletionsModel(model=<deployment>, openai_client=client)`, or
process-wide via `set_default_openai_client(client, use_for_tracing=False)`
plus `set_default_openai_api("chat_completions")` when the deployment lacks
Responses. Choose Responses/Chat Completions from deployed capabilities and the
current Azure API contract. GPT-6 Astra, GPT-6.1 Sol and GPT-6.1 Terra require Responses for
tool calling; GPT-6 Sol and Luna allow function calling on Chat
Completions only with reasoning effort `none`; an agent needing tools and
reasoning must use Responses (`LitellmModel` always uses Chat Completions).
See the [GPT-6 API guide](https://developers.openai.com/api/docs/guides/latest-model)
and the Azure deployment's capabilities before choosing an adapter.
Read deployment configuration or documented Azure management APIs to identify
the deployment; do not rely on an old generic listing endpoint.

LiteLLM/Any-LLM are beta adapters recommended when built-in integration points
are insufficient. They have independent model maps, imports and package extras.
A rejected parameter may be adapter capability metadata rather than the
provider: LiteLLM raises `UnsupportedParamsError ... ['reasoning_effort']` for
an Azure deployment name its model map does not recognize. After confirming the
deployment supports it, pass
`ModelSettings(reasoning=..., extra_args={"allowed_openai_params": ["reasoning_effort"]})`;
`litellm.drop_params=True` silently discards the setting.

Tracing is separate from model authentication. An Azure/LiteLLM key does not
authorize OpenAI trace uploads. Configure trace destination or disable uploads
according to the application's policy.

See [SDK models](https://openai.github.io/openai-agents-python/models/),
[LiteLLM integration](https://docs.litellm.ai/docs/tutorials/openai_agents_sdk)
and the configured provider's current docs.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall