instructor
You are an expert in Instructor, the library for getting structured, validated output from LLMs. You help developers extract typed data from unstructured text using Pydantic models (Python) or Zod schemas (TypeScript), with automatic retries on validation failures, streaming partial objects, and support for OpenAI, Anthropic, Google, and local models — turning LLMs into reliable data extraction engines.
What this skill does
# Instructor — Structured LLM Output with Validation
You are an expert in Instructor, the library for getting structured, validated output from LLMs. You help developers extract typed data from unstructured text using Pydantic models (Python) or Zod schemas (TypeScript), with automatic retries on validation failures, streaming partial objects, and support for OpenAI, Anthropic, Google, and local models — turning LLMs into reliable data extraction engines.
## Core Capabilities
### Python (Pydantic)
```python
# extraction.py — Type-safe LLM extraction
import instructor
from openai import OpenAI
from pydantic import BaseModel, Field
from typing import Literal
client = instructor.from_openai(OpenAI())
class ContactInfo(BaseModel):
name: str = Field(description="Full name of the person")
email: str | None = Field(default=None, description="Email address if mentioned")
phone: str | None = Field(default=None, description="Phone number if mentioned")
company: str | None = Field(default=None)
role: str | None = Field(default=None)
class ExtractedContacts(BaseModel):
contacts: list[ContactInfo]
confidence: float = Field(ge=0, le=1, description="Overall extraction confidence")
# Extract structured data — guaranteed to match schema
result = client.chat.completions.create(
model="gpt-4o-mini",
response_model=ExtractedContacts,
messages=[{
"role": "user",
"content": """Extract contacts from this email:
Hi, I'm reaching out on behalf of Sarah Chen ([email protected]),
VP of Engineering at TechCorp. She'd like to schedule a call.
You can also reach her at (415) 555-0123.
CC: Mike Johnson, [email protected], Head of DevOps""",
}],
max_retries=3, # Auto-retry on validation failure
)
# result.contacts[0].name → "Sarah Chen"
# result.contacts[0].email → "[email protected]"
# result.contacts[0].role → "VP of Engineering"
# Fully typed, validated by Pydantic
# Sentiment analysis with enum
class SentimentAnalysis(BaseModel):
sentiment: Literal["positive", "negative", "neutral", "mixed"]
emotions: list[Literal["joy", "anger", "sadness", "fear", "surprise", "disgust"]]
key_phrases: list[str]
summary: str
analysis = client.chat.completions.create(
model="gpt-4o-mini",
response_model=SentimentAnalysis,
messages=[{"role": "user", "content": f"Analyze sentiment: {review_text}"}],
)
# Streaming partial objects
from instructor import Partial
for partial in client.chat.completions.create_partial(
model="gpt-4o",
response_model=ExtractedContacts,
messages=[{"role": "user", "content": email_text}],
):
# partial.contacts may be incomplete — render progressively
print(f"Found {len(partial.contacts)} contacts so far...")
```
### TypeScript (Zod)
```typescript
import Instructor from "@instructor-ai/instructor";
import OpenAI from "openai";
import { z } from "zod";
const client = Instructor({ client: new OpenAI(), mode: "TOOLS" });
const ContactSchema = z.object({
contacts: z.array(z.object({
name: z.string(),
email: z.string().email().nullable(),
role: z.string().nullable(),
})),
confidence: z.number().min(0).max(1),
});
const result = await client.chat.completions.create({
model: "gpt-4o-mini",
response_model: { schema: ContactSchema, name: "ContactExtraction" },
messages: [{ role: "user", content: emailText }],
max_retries: 3,
});
// result is fully typed as z.infer<typeof ContactSchema>
```
### Multi-Provider
```python
# Works with any provider
from anthropic import Anthropic
import instructor
# Anthropic
client = instructor.from_anthropic(Anthropic())
result = client.messages.create(
model="claude-sonnet-4-20250514",
response_model=ExtractedContacts,
messages=[{"role": "user", "content": text}],
max_tokens=1024,
)
# Local models (Ollama)
from openai import OpenAI
client = instructor.from_openai(OpenAI(base_url="http://localhost:11434/v1", api_key="ollama"), mode=instructor.Mode.JSON)
```
## Installation
```bash
pip install instructor # Python
npm install @instructor-ai/instructor zod # TypeScript
```
## Best Practices
1. **Pydantic/Zod for schema** — Define exact output shape; LLM output is validated and typed automatically
2. **Field descriptions** — Add `description` to fields; helps the LLM understand what to extract
3. **max_retries** — Set to 2-3; Instructor auto-retries with validation error feedback when output doesn't match
4. **Literals for enums** — Use `Literal["a", "b"]` instead of `str` for categorical fields; constrains LLM output
5. **Nested models** — Use nested Pydantic models for complex structures; LLM handles hierarchical extraction
6. **Streaming** — Use `create_partial` for progressive rendering; show partial results as they arrive
7. **GPT-4o-mini for extraction** — Structured extraction doesn't need the smartest model; mini is 10x cheaper and fast
8. **Validation as feedback** — When validation fails, Instructor sends the error back to the LLM for self-correction
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.