From ai-eng-plugin-dev
Scaffolds agent applications across 5 harnesses (Anthropic, Cursor, OpenAI, OpenCode, Pi) with interactive setup, per-harness SDK docs, patterns, and built-in verification.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ai-eng-plugin-dev:agents-sdk-devThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Unified agent scaffolding and verification. One interactive flow, per-harness SDK
Unified agent scaffolding and verification. One interactive flow, per-harness SDK detail, built-in verification.
| Harness | SDK Package | Languages | Runtime |
|---|---|---|---|
| Anthropic | @anthropic-ai/claude-agent-sdk / claude-agent-sdk | TS, Python | API |
| Cursor | @cursor/sdk | TS | Local + Cloud |
| OpenAI | @openai/agents / openai-agents | TS, Python | API |
| OpenCode | opencode | TS | Local |
| Pi | CLI bridge (pi -p) | Any | Local subprocess |
Gather Requirements → Load SDK Reference → Setup Plan → Implement → Verify
Ask these questions one at a time. Wait for the answer before asking the next. Skip any the user already provided via arguments.
"Which harness are you targeting?"
If the user's request implies a harness ("build with claude", "cursor agent"), infer it and confirm.
"TypeScript or Python?"
"What would you like to name your project?"
"What kind of agent are you building?"
"Would you like:"
Confirm the package manager:
bun.lock exists)uv.lock exists)Based on the harness choice, read the appropriate reference file from this
skill's references/ directory:
| Harness | Reference File | Official Docs |
|---|---|---|
| Anthropic | references/anthropic-sdk.md | https://docs.anthropic.com/en/docs/agents-and-tools/claude-agent-sdk |
| Cursor | references/cursor-sdk.md | https://docs.cursor.com/tools/sdk |
| OpenAI | references/openai-agents-sdk.md | https://openai.github.io/openai-agents-python/ |
| OpenCode | references/opencode-sdk.md | Package types / README |
| Pi | references/pi-cli-bridge.md | pi --help / local examples |
Always fetch the latest live docs via WebFetch or WebSearch before generating code. SDK surfaces evolve; the reference file is a baseline, not a substitute for current documentation.
Check for latest versions before installing. Check the package registry (npm, PyPI) and verify the version installs without errors.
Present a concise plan covering:
.env.example, .gitignore, API key instructionsGet user confirmation before proceeding.
Execute the confirmed plan:
.env.example, .gitignore)After all files are created and dependencies installed:
npx tsc --noEmit
Fix ALL type errors. Do not consider setup complete until this passes cleanly.
python -c "import <sdk_package>"
Verify imports resolve and no syntax errors exist.
Run through these checks regardless of harness:
.env.example exists, .env in .gitignore)**Status**: PASS | PASS WITH WARNINGS | FAIL
**Critical Issues**: (blockers, runtime failures, type errors)
**Warnings**: (suboptimal patterns, missing features)
**Passed**: (what's correct)
**Recommendations**: (specific improvements with SDK doc links)
Provide the user:
.env.example)@anthropic-ai/claude-agent-sdkclaude-agent-sdkagents/research-runner/anthropic/runner.tsreferences/anthropic-sdk.md@cursor/sdkAgent.create(), Agent.prompt(), Agent.resume(), streamingagents/research-runner/cursor/runner.tsreferences/cursor-sdk.md@openai/agentsopenai-agentsagents/research-runner/codex/runner.tsreferences/openai-agents-sdk.mdopencode (local SDK)agents/research-runner/opencode/runner.tsreferences/opencode-sdk.mdpi -p "prompt"pi with arguments, capture stdout/stderragents/research-runner/pi/runner.tsreferences/pi-cli-bridge.mdAll scaffolded agents that integrate with the ai-eng-system runner framework should expose this contract:
type WorkflowInput = {
goal: string;
cwd?: string;
model?: string;
maxIterations?: number;
statePath?: string;
};
type WorkflowResult = {
status: "success" | "blocked" | "failed";
summary: string;
artifacts: string[];
nextSteps?: string[];
};
Shared types: agents/research-runner/shared/workflow-contract.ts
| File | Content |
|---|---|
references/anthropic-sdk.md | Anthropic Agent SDK API surface, patterns, code examples |
references/cursor-sdk.md | Cursor TypeScript SDK API surface, patterns, traps |
references/openai-agents-sdk.md | OpenAI Agents SDK API surface, handoffs, tracing |
references/opencode-sdk.md | OpenCode local SDK patterns and session management |
references/pi-cli-bridge.md | Pi CLI bridge, subprocess patterns, MCP subagent tools |
This skill helps the user build agent applications. It is not the place to validate, congratulate, or sell any SDK as a choice. The user's intent is the input; your job is execution.
Ask questions one at a time. Do not batch questions. Respect the user's time.
When the user specifies a harness, load the reference file and follow its patterns. When the user asks to verify, run the verification checklist. When the user asks for help with an existing project, skip to the relevant step.
npx claudepluginhub p/v1truv1us-ai-eng-plugin-dev-plugins-ai-eng-plugin-devGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Reference for writing and editing skills with predictable behavior, covering invocation models, description writing, and information hierarchy.
2plugins reuse this skill
First indexed Jul 8, 2026