laguagu/claude-code-nextjs-skills / skills/openai-agents-sdk
openai-agents-sdk
VerifiedOpenAI 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.9 KB |
| references/guardrails.md | markdown | 1.8 KB |
| references/handoffs.md | markdown | 1.4 KB |
| references/patterns.md | markdown | 1.5 KB |
| references/providers.md | markdown | 2.8 KB |
| references/sandbox.md | markdown | 1.5 KB |
| references/sessions.md | markdown | 1.6 KB |
| references/streaming.md | markdown | 1.5 KB |
| references/structured-output.md | markdown | 838 B |
| references/tools.md | markdown | 3.0 KB |
references/handoffs.md
View on GitHub# Delegation and history
A handoff changes the active agent, which continues the conversation. An
agent-as-tool returns a result to the manager. Either can be model-selected;
handoff versus tool is a control-flow decision, not a deterministic-routing
guarantee.
Use the installed handoff API for declared input, hooks and filtering. Preserve
the current `HandoffInputData` fields when changing history (for example with a
dataclass replacement) rather than reconstructing the structure field by field.
Filter only what the specialist should not receive. Keep tool-call/result and
provider protocol context valid. Use built-in filters when they meet the
contract and inspect their effect on the actual conversation. The recipient
gets full conversation history by default; handoff `input_type` supplies
model-written metadata to `on_handoff`, not replacement conversation input.
`remove_all_tools` removes tool items but not text already copied into messages;
`nest_handoff_history` summarizes history and is not a redaction boundary.
Local run context is separate from model-visible history. Authorization,
guardrail coverage and tool permissions need checking in the receiving path too.
Read [handoff docs](https://openai.github.io/openai-agents-python/handoffs/)
and [orchestration docs](https://openai.github.io/openai-agents-python/multi_agent/)
for compatible implementations.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 119k | Updated | Claude CodeCodex | Verified | Install |
| 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: 118k | Updated | Claude CodeCodex | Verified | Install |