Agent skill · Backend & API

openai-assistants

Build stateful chatbots with OpenAI Assistants API v2 - Code Interpreter, File Search (10k files), Function Calling. ⚠️ Sunset H1 2026; use openai-responses for new projects. Use when: building stateful chatbots, implementing RAG, or troubleshooting "thread has active run", vector store delays, polling timeouts, or file upload errors.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill openai-assistants --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 31 KB
Bundled scripts: none
Path: skills/ai-llm/openai-assistants/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

Review
written from the skill's own SKILL.md · Aug 5, 2026

What it does

Guides a coding agent to work with OpenAI Assistants API v2 to build stateful chatbots using Assistants, Threads, Messages, and Runs, including tools like Code Interpreter, File Search, and Function Calling.

How it works

Describes object models (Assistants, Threads, Messages, Runs) and their interactions:

  • Create an Assistant with name, instructions, model, tools, tool_resources, and metadata.
  • Create/Retrieve/Update/Delete/List Assistants.
  • Create Threads (empty or with initial messages) and retrieve/update/delete metadata.
  • Add Messages to a Thread with role, content, attachments, and metadata.
  • Create Runs on a Thread with assistant_id, optional instructions, additional_messages, and overrides for tools/temperature/top_p/max tokens; poll Run status until completion or requires_action; handle streaming and cancellation.
  • Streaming Runs provide real-time events for run and message progress.
  • Use Tools (Code Interpreter, File Search, Function Calling) within Runs and Messages as described.
  • Use available outputs from Code Interpreter via listing messages and accessing file contents.

When to use it

Use when building stateful chatbots, implementing RAG, or troubleshooting issues related to thread activity, vector store delays, polling timeouts, or file upload errors.

What it can touch

Tools include Code Interpreter, File Search, and Function Calling as per the skill's guidance. The content shows how to reference tools in assistants and runs, and how to attach tools to messages and runs.

Caveats

OpenAI Assistants API v2 is sunset in H1 2026; migration to Responses API is advised. Deeper migration guidance is in the migration-to-responses path. Deactivation and deprecation status is noted, with recommended use only for existing code or legacy maintenance. The skill documents how to create, retrieve, update, delete, list, and run assistants, threads, messages, and runs, including polling patterns and streaming behavior.

From the SKILL.md

# OpenAI Assistants API v2 **Status**: Production Ready (Deprecated H1 2026) **Package**: openai@6.7.0 **Last Updated**: 2025-10-25 **v1 Deprecated**: December 18, 2024 **v2 Sunset**: H1 2026 (migrate to Responses API) --- ## ⚠️ Important: Deprecation Notice **OpenAI announced that the Assistants API will be deprecated in favor of the [Responses API](../openai-responses/SKILL.md).** **Timeline:** - ✅ **Dec 18, 2024**: Assistants API v1 deprecated - ⏳ **H1 2026**: Planned sunset of Assistants API v2 - ✅ **Now**: Responses API available (recommended for new projects) **Should you still use this skill?** - ✅ **Yes, if**: You have existing Assistants API code (12-18 month migration window) - ✅ **Yes, if**: You need to maintain legacy applications - ✅ **Yes, if**: Planning migration from Assistants → Responses - ❌ **No, if**: Starting a new project (use openai-responses skill instead) **Migration Path:** See `references/migration-to-responses.md` for complete migration guide. --- ## Table of Contents 1. [Quick Start](#quick-start) 2. [Core Concepts](#core-concepts) 3. [Assistants](#assistants) 4. [Threads](#threads) 5. [Messages](#messages) 6. [Runs](#runs) 7. [Streaming Runs](#streamin

What's inside
Steps it walks through
  1. ⚠️ Important: Deprecation Notice
  2. Table of Contents
  3. Quick Start
  4. Installation
  5. Environment Setup
  6. Basic Assistant (Node.js SDK)
  7. Basic Assistant (Fetch - Cloudflare Workers)
  8. Core Concepts
  9. 1. Assistants
  10. 2. Threads
  11. 3. Messages
  12. 4. Runs
  13. Assistants
  14. Create an Assistant
Ships with 1 file
  • metadata.json
Commands it runs
npm install openai@6.7.0
export OPENAI_API_KEY="sk-..."
More from claude-skill-registry
All skills →
About this skill
What does the openai-assistants skill do?

Build stateful chatbots with OpenAI Assistants API v2 - Code Interpreter, File Search (10k files), Function Calling. ⚠️ Sunset H1 2026; use openai-responses for new projects. Use when: building stateful chatbots, implementing RAG, or troubleshooting "thread has active run", vector store delays, polling timeouts, or file upload errors.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill openai-assistants --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going