--- name: agent-sdk-dev-d52c5ecb3568 description: A comprehensive plugin for creating and verifying Claude Agent SDK applications in Python and TypeScript. --- # Agent SDK Development Plugin A comprehensive plugin for creating and verifying Claude Agent SDK applications in Python and TypeScript. ## Overview The Agent SDK Development Plugin streamlines the entire lifecycle of building Agent SDK applications, from initial scaffolding to verification against best practices. It helps you quickly start new projects with the latest SDK versions and ensures your applications follow official documentation patterns. ## Features ### Command: `/new-sdk-app` Interactive command that guides you through creating a new Claude Agent SDK application. **What it does:** - Asks clarifying questions about your project (language, name, agent type, starting point) - Checks for and installs the latest SDK version - Creates all necessary project files and configuration - Sets up proper environment files (.env.example, .gitignore) - Provides a working example tailored to your use case - Runs type checking (TypeScript) or syntax validation (Python) - Automatically verifies the setup using the appropriate verifier agent **Usage:** ```bash /new-sdk-app my-project-name ``` Or simply: ```bash /new-sdk-app ``` The command will interactively ask you: 1. Language choice (TypeScript or Python) 2. Project name (if not provided) 3. Agent type (coding, business, custom) 4. Starting point (minimal, basic, or specific example) 5. Tooling preferences (npm/yarn/pnpm or pip/poetry) **Example:** ```bash /new-sdk-app customer-support-agent # → Creates a new Agent SDK project for a customer support agent # → Sets up TypeScript or Python environment # → Installs latest SDK version # → Verifies the setup automatically ``` ### Agent: `agent-sdk-verifier-py` Thoroughly verifies Python Agent SDK applications for correct setup and best practices. **Verification checks:** - SDK installation and version - Python environment setup (requirements.txt, pyproject.toml) - Correct SDK usage and patterns - Agent initialization and configuration - Environment and security (.env, API keys) - Error handling and functionality - Documentation completeness **When to use:** - After creating a new Python SDK project - After modifying an existing Python SDK application - Before deploying a Python SDK application **Usage:** The agent runs automatically after `/new-sdk-app` creates a Python project, or you can trigger it by asking: ``` "Verify my Python Agent SDK application" "Check if my SDK app follows best practices" ``` **Output:** Provides a comprehensive report with: - Overall status (PASS / PASS WITH WARNINGS / FAIL) - Critical issues that prevent functionality - Warnings about suboptimal patterns - List of passed checks - Specific recommendations with SDK documentation references ### Agent: `agent-sdk-verifier-ts` Thoroughly verifies TypeScript Agent SDK applications for correct setup and best practices. **Verification checks:** - SDK installation and version - TypeScript configuration (tsconfig.json) - Correct SDK usage and patterns - Type safety and imports - Agent initialization and configuration - Environment and security (.env, API keys) - Error handling and functionality - Documentation completeness **When to use:** - After creating a new TypeScript SDK project - After modifying an existing TypeScript SDK application - Before deploying a TypeScript SDK application **Usage:** The agent runs automatically after `/new-sdk-app` creates a TypeScript project, or you can trigger it by asking: ``` "Verify my TypeScript Agent SDK application" "Check if my SDK app follows best practices" ``` **Output:** Provides a comprehensive report with: - Overall status (PASS / PASS WITH WARNINGS / FAIL) - Critical issues that prevent functionality - Warnings about suboptimal patterns - List of passed checks - Specific recommendations with SDK documentation references ## Workflow Example Here's a typical workflow using this plugin: 1. **Create a new project:** ```bash /new-sdk-app code-reviewer-agent ``` 2. **Answer the interactive questions:** ``` Language: TypeScript Agent type: Coding agent (code review) Starting point: Basic agent with common features ``` 3. **Automatic verification:** The command automatically runs `agent-sdk-verifier-ts` to ensure everything is correctly set up. 4. **Start developing:** ```bash # Set your API key echo "ANTHROPIC_API_KEY=your_key_here" > .env # Run your agent npm start ``` 5. **Verify after changes:** ``` "Verify my SDK application" ``` ## Installation This plugin is included in the Claude Code repository. To use it: 1. Ensure Claude Code is installed 2. The plugin commands and agents are automatically available ## Best Practices - **Always use the latest SDK version**: `/new-sdk-app` checks for and installs the latest version - **Verify before deploying**: Run the verifier agent before deploying to production - **Keep API keys secure**: Never commit `.env` files or hardcode API keys - **Follow SDK documentation**: The verifier agents check against official patterns - **Type check TypeScript projects**: Run `npx tsc --noEmit` regularly - **Test your agents**: Create test cases for your agent's functionality ## Resources - [Agent SDK Overview](https://docs.claude.com/en/api/agent-sdk/overview) - [TypeScript SDK Reference](https://docs.claude.com/en/api/agent-sdk/typescript) - [Python SDK Reference](https://docs.claude.com/en/api/agent-sdk/python) - [Agent SDK Examples](https://docs.claude.com/en/api/agent-sdk/examples) ## Troubleshooting ### Type errors in TypeScript project **Issue**: TypeScript project has type errors after creation **Solution**: - The `/new-sdk-app` command runs type checking automatically - If errors persist, check that you're using the latest SDK version - Verify your `tsconfig.json` matches SDK requirements ### Python import errors **Issue**: Cannot import from `claude_agent_sdk` **Solution**: - Ensure you've installed dependencies: `pip install -r requirements.txt` - Activate your virtual environment if using one - Check that the SDK is installed: `pip show claude-agent-sdk` ### Verification fails with warnings **Issue**: Verifier agent reports warnings **Solution**: - Review the specific warnings in the report - Check the SDK documentation references provided - Warnings don't prevent functionality but indicate areas for improvement ## Author Ashwin Bhat (ashwin@anthropic.com) ## Version 1.0.0 # Workflow Instructions ## Command: new-sdk-app.md --- description: Create and setup a new Claude Agent SDK application argument-hint: [project-name] --- You are tasked with helping the user create a new Claude Agent SDK application. Follow these steps carefully: ## Reference Documentation Before starting, review the official documentation to ensure you provide accurate and up-to-date guidance. Use WebFetch to read these pages: 1. **Start with the overview**: https://docs.claude.com/en/api/agent-sdk/overview 2. **Based on the user's language choice, read the appropriate SDK reference**: - TypeScript: https://docs.claude.com/en/api/agent-sdk/typescript - Python: https://docs.claude.com/en/api/agent-sdk/python 3. **Read relevant guides mentioned in the overview** such as: - Streaming vs Single Mode - Permissions - Custom Tools - MCP integration - Subagents - Sessions - Any other relevant guides based on the user's needs **IMPORTANT**: Always check for and use the latest versions of packages. Use WebSearch or WebFetch to verify current versions before installation. ## Gather Requirements IMPORTANT: Ask these questions one at a time. Wait for the user's response before asking the next question. This makes it easier for the user to respond. Ask the questions in this order (skip any that the user has already provided via arguments): 1. **Language** (ask first): "Would you like to use TypeScript or Python?" - Wait for response before continuing 2. **Project name** (ask second): "What would you like to name your project?" - If $ARGUMENTS is provided, use that as the project name and skip this question - Wait for response before continuing 3. **Agent type** (ask third, but skip if #2 was sufficiently detailed): "What kind of agent are you building? Some examples: - Coding agent (SRE, security review, code review) - Business agent (customer support, content creation) - Custom agent (describe your use case)" - Wait for response before continuing 4. **Starting point** (ask fourth): "Would you like: - A minimal 'Hello World' example to start - A basic agent with common features - A specific example based on your use case" - Wait for response before continuing 5. **Tooling choice** (ask fifth): Let the user know what tools you'll use, and confirm with them that these are the tools they want to use (for example, they may prefer pnpm or bun over npm). Respect the user's preferences when executing on the requirements. After all questions are answered, proceed to create the setup plan. ## Setup Plan Based on the user's answers, create a plan that includes: 1. **Project initialization**: - Create project directory (if it doesn't exist) - Initialize package manager: - TypeScript: `npm init -y` and setup `package.json` with type: "module" and scripts (include a "typecheck" script) - Python: Create `requirements.txt` or use `poetry init` - Add necessary configuration files: - TypeScript: Create `tsconfig.json` with proper settings for the SDK - Python: Optionally create config files if needed 2. **Check for Latest Versions**: - BEFORE installing, use WebSearch or check npm/PyPI to find the latest version - For TypeScript: Check https://www.npmjs.com/package/@anthropic-ai/claude-agent-sdk - For Python: Check https://pypi.org/project/claude-agent-sdk/ - Inform the user which version you're installing 3. **SDK Installation**: - TypeScript: `npm install @anthropic-ai/claude-agent-sdk@latest` (or specify latest version) - Python: `pip install claude-agent-sdk` (pip installs latest by default) - After installation, verify the installed version: - TypeScript: Check package.json or run `npm list @anthropic-ai/claude-agent-sdk` - Python: Run `pip show claude-agent-sdk` 4. **Create starter files**: - TypeScript: Create an `index.ts` or `src/index.ts` with a basic query example - Python: Create a `main.py` with a basic query example - Include proper imports and basic error handling - Use modern, up-to-date syntax and patterns from the latest SDK version 5. **Environment setup**: - Create a `.env.example` file with `ANTHROPIC_API_KEY=your_api_key_here` - Add `.env` to `.gitignore` - Explain how to get an API key from https://console.anthropic.com/ 6. **Optional: Create .claude directory structure**: - Offer to create `.claude/` directory for agents, commands, and settings - Ask if they want any example subagents or slash commands ## Implementation After gathering requirements and getting user confirmation on the plan: 1. Check for latest package versions using WebSearch or WebFetch 2. Execute the setup steps 3. Create all necessary files 4. Install dependencies (always use latest stable versions) 5. Verify installed versions and inform the user 6. Create a working example based on their agent type 7. Add helpful comments in the code explaining what each part does 8. **VERIFY THE CODE WORKS BEFORE FINISHING**: - For TypeScript: - Run `npx tsc --noEmit` to check for type errors - Fix ALL type errors until types pass completely - Ensure imports and types are correct - Only proceed when type checking passes with no errors - For Python: - Verify imports are correct - Check for basic syntax errors - **DO NOT consider the setup complete until the code verifies successfully** ## Verification After all files are created and dependencies are installed, use the appropriate verifier agent to validate that the Agent SDK application is properly configured and ready for use: 1. **For TypeScript projects**: Launch the **agent-sdk-verifier-ts** agent to validate the setup 2. **For Python projects**: Launch the **agent-sdk-verifier-py** agent to validate the setup 3. The agent will check SDK usage, configuration, functionality, and adherence to official documentation 4. Review the verification report and address any issues ## Getting Started Guide Once setup is complete and verified, provide the user with: 1. **Next steps**: - How to set their API key - How to run their agent: - TypeScript: `npm start` or `node --loader ts-node/esm index.ts` - Python: `python main.py` 2. **Useful resources**: - Link to TypeScript SDK reference: https://docs.claude.com/en/api/agent-sdk/typescript - Link to Python SDK reference: https://docs.claude.com/en/api/agent-sdk/python - Explain key concepts: system prompts, permissions, tools, MCP servers 3. **Common next steps**: - How to customize the system prompt - How to add custom tools via MCP - How to configure permissions - How to create subagents ## Important Notes - **ALWAYS USE LATEST VERSIONS**: Before installing any packages, check for the latest versions using WebSearch or by checking npm/PyPI directly - **VERIFY CODE RUNS CORRECTLY**: - For TypeScript: Run `npx tsc --noEmit` and fix ALL type errors before finishing - For Python: Verify syntax and imports are correct - Do NOT consider the task complete until the code passes verification - Verify the installed version after installation and inform the user - Check the official documentation for any version-specific requirements (Node.js version, Python version, etc.) - Always check if directories/files already exist before creating them - Use the user's preferred package manager (npm, yarn, pnpm for TypeScript; pip, poetry for Python) - Ensure all code examples are functional and include proper error handling - Use modern syntax and patterns that are compatible with the latest SDK version - Make the experience interactive and educational - **ASK QUESTIONS ONE AT A TIME** - Do not ask multiple questions in a single response Begin by asking the FIRST requirement question only. Wait for the user's answer before proceeding to the next question. --- Source attribution: David-Li0406 Original project: https://github.com/David-Li0406/meta-skill-evloving/blob/ca3a335628981df10c36e00cb9850df2c247ab9a/skill-flow/data/skills-refined-36k/skillsmp/agent-sdk-dev/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: David-Li0406 Original project: https://github.com/David-Li0406/meta-skill-evloving/blob/ca3a335628981df10c36e00cb9850df2c247ab9a/skill-flow/data/skills-refined-36k/skillsmp/agent-sdk-dev/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering Roles: Backend Developer, Full-Stack Developer, ML / AI Engineer Specialties: API, Backend Tools: Claude Agent Sdk Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 0b5daadbebf6400f2006c23a4e326e4954adf599afd0d8450f2d5d2a38e83c73