Individual skill

agents-openai

Build agents on OpenAI's platform patterns — assistants-style threads, function calling, structured outputs, and multi-step tool workflows. Use when working with OpenAI models as the agent engine.

skills/agents-openai/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 54
Repository last updated: Oct 10, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-skills Repository topic
ai-agents Repository topic
ai-agents-automation Repository topic
ai-skills Repository topic
awesome Repository topic
awesome-list Repository topic
chatgpt Repository topic
claude-skills Repository topic
meta-ai Repository topic
muse-ai Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 4,176 bytes

Read excerpt


# Agents on OpenAI Platform Patterns

OpenAI's agent-building surface centers on a few primitives: chat models with native function 
calling, structured outputs, persistent threads for conversation state, and file/code-interpreter 
tools. This skill covers using them as an agent substrate.

## Overview

The core loop: the model reasons, emits function calls with structured arguments, your code 
executes them, results go back into the conversation, repeat. Structured outputs (JSON schema mode) 
make the model's responses machine-readable. Threads persist conversation state server-side so you 
don't manage history yourself. Built-in tools — code execution, file search — cover common 
needs without custom tooling. Your architecture decisions sit on top: when to call functions vs. 
answer, how to manage the loop, where humans intervene.