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/guardrails.md
View on GitHub# Guardrail coverage
Agent input guardrails run for the first agent; output guardrails check the
final-output agent. They do not surround every intermediate handoff or tool.
Input guardrails default to parallel execution. The agent can already consume
tokens or execute tools before a tripwire cancels it. Use
`run_in_parallel=False` when the check must complete before the run starts.
Output guardrails happen after execution and cannot undo side effects or
already-streamed output.
Tool input/output guardrails use the FunctionTool pipeline. Hosted/built-in
execution tools and handoff calls have different coverage; local MCP tools can
use server-configured guardrails in supported releases. Verify the installed
coverage before assuming a generic policy applies. With approval, tool input
guardrails run after approval, just before execution.
`RunConfig(tool_execution=ToolExecutionConfig(pre_approval_tool_input_guardrails=True))`
also runs them before the approval interruption, where a rejection replaces the
approval prompt; an approved call then runs them again, so each guardrail runs
twice and its side effects must tolerate that (verified in 0.24.0).
Output guardrails combined with Responses server-managed history
(`conversation_id`, `previous_response_id` or `auto_previous_response_id`)
raise `UserError`: rejected output cannot be removed from that history.
A returned tripwire and a guardrail exception have different failure and
session-persistence semantics. Read the current
[guardrail documentation](https://openai.github.io/openai-agents-python/guardrails/)
for those details rather than writing a broad catch that hides the distinction.
Keep actual access control in application/tool code. Test a rejected input,
tool denial, output tripwire and relevant streaming behavior.
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 |