agent-sdk-development
Central authority for Claude Agent SDK (TypeScript and Python SDKs). Covers SDK installation, authentication (Anthropic key, Bedrock, Vertex), sessions and resumption, forking sessions, streaming vs single mode, custom tools, permissions (allowedTools, disallowedTools, permissionMode), MCP integration, system prompts (CLAUDE.md, appendSystemPrompt, outputStyle), cost tracking, todo tracking, structured outputs, hosting patterns, plugins, and SDK branding guidelines. Assists with building custom agents, configuring SDK options, and troubleshooting SDK issues. Delegates 100% to docs-management s
npx skills add majiayu000/claude-skill-registry --skill agent-sdk-development --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Agent SDK Meta Skill ## 🚨 MANDATORY: Invoke docs-management First > **STOP - Before providing ANY response about Claude Agent SDK:** > > 1. **INVOKE** `docs-management` skill > 2. **QUERY** using keywords: Agent SDK, TypeScript SDK, Python SDK, sessions, custom tools, permissions, or related topics > 3. **BASE** all responses EXCLUSIVELY on official documentation loaded > > **Skipping this step results in outdated or incorrect information.** ### Verification Checkpoint Before responding, verify: - [ ] Did I invoke docs-management skill? - [ ] Did official documentation load? - [ ] Is my response based EXCLUSIVELY on official docs? If ANY checkbox is unchecked, STOP and invoke docs-management first. ## Overview Central authority for Claude Agent SDK (TypeScript and Python SDKs). This skill uses **100% delegation to docs-management** - it contains NO duplicated official documentation. **Architecture:** Pure delegation with keyword registry. All official documentation is accessed via docs-management skill queries. ## Reference Loading Guide This skill follows a **pure delegation architecture** with three loading layers: ### Layer 1: Always in Context - **SKILL.md** (this file) - Ke
- 🚨 MANDATORY: Invoke docs-management First
- Verification Checkpoint
- Overview
- Reference Loading Guide
- Layer 1: Always in Context
- Layer 2: On-Demand via docs-management
- Layer 3: External Resources (GitHub)
- Loading Strategy
- When to Use This Skill
- Keyword Registry for docs-management Queries
- SDK Fundamentals
- Authentication
- Sessions
- Input Modes
What does the agent-sdk-development skill do?
Central authority for Claude Agent SDK (TypeScript and Python SDKs). Covers SDK installation, authentication (Anthropic key, Bedrock, Vertex), sessions and resumption, forking sessions, streaming vs single mode, custom tools, permissions (allowedTools, disallowedTools, permissionMode), MCP integration, system prompts (CLAUDE.md, appendSystemPrompt, outputStyle), cost tracking, todo tracking, structured outputs, hosting patterns, plugins, and SDK branding guidelines. Assists with building custom agents, configuring SDK options, and troubleshooting SDK issues. Delegates 100% to docs-management s
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill agent-sdk-development --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.