Claude API
Build, debug, and migrate Anthropic Claude API apps with prompt caching, tool use, and Managed Agents baked in.
Overview
The Claude API skill is the official Anthropic Agent Skill that teaches Claude Code (and other agents) to build, debug, and optimize applications on the Claude API and Anthropic SDK — with prompt caching, adaptive thinking, tool use, and Managed Agents wired in by default.
What is the Claude API skill?
It is a skill from Anthropic's anthropics/skills repository that activates whenever your code imports anthropic or @anthropic-ai/sdk, when you ask for the Claude API, the Anthropic SDK, or Managed Agents, or when you tune a Claude feature such as caching, thinking, tool use, batch, files, citations, or memory. It detects the project language — Python, TypeScript/JavaScript, Java/Kotlin/Scala, Go, Ruby, C#, PHP, or raw cURL — and reads the matching language-specific reference files before writing a single line of code, so it never guesses SDK signatures.
What it does
- Writes Claude API calls through the official Anthropic SDK for your language (or raw HTTP only when you explicitly ask), never an OpenAI-compatible shim.
- Adds prompt caching with correct
cache_controlbreakpoint placement and verifies cache hits viausage.cache_read_input_tokens. - Defaults to the current model ID
claude-opus-4-8and adaptive thinking (thinking: {type: "adaptive"}), with streaming for long requests. - Migrates existing code between Claude model versions (4.5 to 4.6, 4.6 to 4.7, 4.7 to 4.8) and replaces retired models, translating deprecated
budget_tokensand prefill patterns. - Implements tool use (user-defined and server-side), structured outputs via
output_config.format, batches at 50% cost, the Files API, citations, and server-side compaction. - Sets up Managed Agents — persisted, versioned agent configs plus per-session containers — using the create-once, reference-by-ID flow.
How it works
Everything routes through the single POST /v1/messages endpoint; tools and output constraints are features of that endpoint, not separate APIs. The skill first scans for non-Anthropic provider markers (import openai, gpt-4, *-openai.py) and refuses to inject Anthropic SDK calls into provider-neutral files. It then reads {lang}/claude-api/README.md first, pulling in shared/prompt-caching.md, shared/tool-use-concepts.md, shared/agent-design.md, shared/model-migration.md, and the Managed Agents references only as the task requires. Live SDK documentation is fetched from shared/live-sources.md whenever a binding is not explicitly documented.
Who it is for
Engineers building LLM-powered applications on Claude — backend developers, AI application teams, and anyone integrating the Anthropic SDK into a Python, TypeScript, Java, Go, Ruby, C#, or PHP codebase, or calling the API over cURL. It is aimed at developers who want correct, current, cache-optimized Claude code rather than hallucinated SDK calls.
What you can build
Classification, summarization, and extraction services; streaming chat UIs; code-orchestrated workflows with tool use; custom agents that run their own loop; batch pipelines; document and report generators using the code-execution sandbox; and server-managed stateful agents with file mounts and an SSE event stream via Managed Agents.
Why it matters
LLMs frequently hallucinate SDK method names, append wrong date suffixes to model IDs, and forget prompt caching — quietly inflating cost and breaking builds. This skill pins the agent to documented APIs, the exact claude-opus-4-8 model string, adaptive thinking, and verified caching, so the Claude code your agent ships actually compiles, caches, and stays current across model migrations.
What's Included
- Language detection for Python, TypeScript/JavaScript, Java, Go, Ruby, C#, PHP, and cURL
- Prompt caching guidance with breakpoint placement and cache-hit verification
- Current model reference (claude-opus-4-8) with adaptive thinking and effort settings
- Model migration playbook for 4.5 to 4.6, 4.6 to 4.7, 4.7 to 4.8, and retired models
- Tool use, structured outputs, batches, Files API, and compaction patterns
- Managed Agents setup with persisted configs and per-session containers
- Live-sources reference for fetching latest official SDK documentation
Installation
1. Install via the skills CLI
npx skills add anthropics/skills --skill claude-api2. Or add it as a Claude Code plugin
Register the Anthropic marketplace, then install the example skills plugin:
/plugin marketplace add anthropics/skills
/plugin install example-skills@anthropic-agent-skills3. Use it
Open a project that imports anthropic or @anthropic-ai/sdk and ask your agent to add a feature — for example, "add prompt caching to this Claude call" or "migrate this file to Opus 4.8". The skill triggers automatically.
Requirements
- An Anthropic API key and access to the Claude API
- A project using an official Anthropic SDK (anthropic, @anthropic-ai/sdk, etc.) or raw HTTP
- Claude Code, Cursor, or another agent that supports Anthropic Agent Skills
Changelog
Initial listing of the official Anthropic claude-api skill.
FAQs
Related Skills
Webapp Testing
Test and debug local web apps with Playwright — capture browser screenshots, read console logs, and verify frontend behavior from your AI agent.
GSAP AI Skills
Official GreenSock skills that teach AI coding agents to write correct, performant GSAP animations
Official AI Skills for Stripe
Stripe's official agent skills that teach AI coding agents to build secure, correct Stripe payment integrations
Supabase Agent Skills
Official Supabase skills that teach AI agents to build, query, and secure Supabase apps correctly.
Official Skills for Next.js, React, and Vercel Deployments
Vercel's official agent skills that teach AI coding agents to build, optimize, and ship Next.js & React apps the right way
MCP Builder
Build high-quality MCP servers in Python (FastMCP) or TypeScript (MCP SDK) with well-designed tools and evals.