Canonical manifest schema
plugin.json targets the official 1.0.0 schema.
Agent Plugins specification §5.2
Build Claude-powered applications with current API and SDK patterns for streaming, tools, files, batches, and managed-agent workflows across common languages.
grounded
in current APIs.
Choose the language, confirm live SDK behavior, then implement streaming and tools with explicit error paths.
Explainable standards check
Official latest version: 1.0.0 (Working Draft). The value is read from the official specification and cached for one day.
This is a static package-format check, not a security audit, quality score, malware scan, or guarantee of client compatibility.
plugin.json targets the official 1.0.0 schema.
Agent Plugins specification §5.2
The plugin name “claude-api” satisfies the 1–64 character naming rules.
Agent Plugins specification §§5.3 and 5.5
No unknown top-level manifest fields were found.
Agent Plugins specification §5.2
All present metadata and extension fields use permitted JSON types.
Agent Plugins specification §§5.2–5.6
A regular plugin.json file exists at the plugin root.
Agent Plugins specification §§4.1 and 5.1
1 immediate-child Agent Skill discovered; every SKILL.md passed required frontmatter and naming checks.
Agent Plugins specification §7.1 and Agent Skills specification
No root mcp.json is present; MCP is optional and its absence is conforming.
Agent Plugins specification §§6.2 and 7.2
Capabilities
Build against current Claude API behavior, not stale assumptions.
Use this plugin when implementing Claude calls, streaming, tool loops, Files API, batches, or managed-agent patterns in a supported language.
Language-specific references keep examples aligned with the conventions and capabilities of each supported SDK.
The workflow warns that training knowledge may be stale and requires current documentation checks for unstable details.
Practical workflow
Identify the project language, required model behavior, streaming needs, tools, files, and operational constraints.
Use current SDK syntax, handle errors and tool calls, protect credentials, and exercise realistic success and failure cases.
Package contents
Claude API declares 1 Skill, 0 MCP configurations, and 1 additional resource. The included-file links below point to the reviewed source repository.
Agent Skills
1
claude-api
MCP servers
0
No runtime service
Package format
Agent Plugins
Official latest 1.0.0
Installation
Sparse-clone the plugin directory and load it in a compatible client. The package provides guidance and references; it does not install credentials or an API runtime.
git clone --filter=blob:none --sparse https://github.com/chenmiaohero/Portable-Agent-Plugins.git
cd Portable-Agent-Plugins
git sparse-checkout set plugins/claude-apiSynced source content
This README snapshot is stored by Agent Plugins Hub and refreshed by the daily GitHub synchronization pipeline. Remote images and embedded content are not loaded.
This repository does not currently provide a README snapshot. The plugin instructions below remain available.
Source documentation
Rendered from the linked GitHub source. Raw HTML is disabled, scripts cannot execute, remote images are omitted, and external links open separately.
Claude API helps implement Claude-powered applications across major SDK languages. It covers current syntax checks, streaming, tool use, Files API, message batches, managed-agent patterns, error handling, and output requirements.
Identify the project's language and required API behavior first. Verify unstable SDK details against current official Anthropic documentation, then implement authentication, messages, streaming or tool loops, retries, and realistic failure handling.
Never place API keys in prompts or source control. API and SDK details can change after model training, so current official documentation remains authoritative. Test rate limits, malformed tool output, network failures, and cancellation.
This portable package is maintained in chenmiaohero/Portable-Agent-Plugins from a pinned Apache-2.0 upstream Skill.
Continue exploring
A portable design-lead workflow for building production-ready interfaces that feel specific to the product instead of assembled from defaults.
The small official reference package for inspecting a portable manifest and migration workflow.
A portable creative-coding workflow for original p5.js generative art and interactive exploration.