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/sandbox.md
View on GitHub# Sandbox agents
Use `SandboxAgent` when the agent needs a persistent workspace, filesystem/shell
tools or lazily loaded skills. Ordinary API/function-tool work need not pay for
a workspace runtime.
The sandbox hosts execution; the agent loop remains in the application process.
The docs labelled this API beta through 0.22.x and removed the label before
0.23. Read the current
[sandbox quickstart](https://openai.github.io/openai-agents-python/sandbox_agents/)
and installed source before choosing clients, capabilities, manifests or mounts.
A local Unix client, Docker client and remote environment do not establish the
same isolation/permission boundary. `UnixLocalSandboxClient` adds no OS
confinement on Linux; its macOS `sandbox-exec` filesystem restrictions do not
isolate the network (verified in 0.24.0). Use a suitably isolated backend for
untrusted commands. Configure allowed paths, commands, network access and
credentials for the task; do not copy demo defaults blindly.
Use documented session/snapshot state to resume the workspace. Define who owns
cleanup and how mounts or files persist. Skills are instruction bundles;
loading them does not authorize tools or grant isolation.
Verify the actual client on the target host, including cancellation, cleanup,
resume and access limits. Do not show an incomplete constructor sketch as a
working example. `agents.testing.scripted_sandbox_session()` supports offline
workflow tests without starting a sandbox (verified in 0.24.0).
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 |