Build applications with the Anthropic Claude API and SDKs.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionclaude-apiExecute the skills CLI command in your project's root directory to begin installation:
Fetches claude-api from affaan-m/everything-claude-code and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate claude-api. Access via /claude-api in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
142.9K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
142.9K
stars
Build applications with the Anthropic Claude API and SDKs.
anthropic (Python) or @anthropic-ai/sdk (TypeScript)| Model | ID | Best For |
|---|---|---|
| Opus 4.1 | claude-opus-4-1 |
Complex reasoning, architecture, research |
| Sonnet 4 | claude-sonnet-4-0 |
Balanced coding, most development tasks |
| Haiku 3.5 | claude-3-5-haiku-latest |
Fast responses, high-volume, cost-sensitive |
Default to Sonnet 4 unless the task requires deep reasoning (Opus) or speed/cost optimization (Haiku). For production, prefer pinned snapshot IDs over aliases.
pip install anthropic
import anthropic
client = anthropic.Anthropic() # reads ANTHROPIC_API_KEY from env
message = client.messages.create(
model="claude-sonnet-4-0",
max_tokens=1024,
messages=[
{"role": "user", "content": "Explain async/await in Python"}
]
)
print(message.content[0].text)
with client.messages.stream(
model="claude-sonnet-4-0",
max_tokens=1024,
messages=[{"role": "user", "content": "Write a haiku about coding"}]
) as stream:
for text in stream.text_stream:
print(text, end="", flush=True)
message = client.messages.create(
model="claude-sonnet-4-0",
max_tokens=1024,
system="You are a senior Python developer. Be concise.",
messages=[{"role": "user", "content": "Review this function"}]
)
npm install @anthropic-ai/sdk
import Anthropic from "@anthropic-ai/sdk";
const client = new Anthropic(); // reads ANTHROPIC_API_KEY from env
const message = await client.messages.create({
model: "claude-sonnet-4-0",
max_tokens: 1024,
messages: [
{ role: "user", content: "Explain async/await in TypeScript" }
],
});
console.log(message.content[0].text);
const stream = client.messages.stream({
model: "claude-sonnet-4-0",
max_tokens: 1024,
messages: [{ role: "user", content: "Write a haiku" }],
});
for await (const event of stream) {
if (event.type === "content_block_delta" && event.delta.type === "text_delta") {
process.stdout.write(event.delta.text);
}
}
Define tools and let Claude call them:
tools = [
{
"name": "get_weather",
"description": "Get current weather for a location",
"input_schema": {
"type": "object",
"properties": {
"location": {"type": "string", "description": "City name"},
"unit": {"type": "string", "enum": ["celsius", "fahrenheit"]}
},
"required": ["location"]
}
}
]
message = client.messages.create(
model="claude-sonnet-4-0",
max_tokens=1024,
tools=tools,
messages=[{"role": "user", "content": "What's the weather in SF?"}]
)
# Handle tool use response
for block in message.content:
if block.type == "tool_use":
# Execute the tool with block.input
result = get_weather(**block.input)
# Send result back
follow_up = client.messages.create(
model="claude-sonnet-4-0",
max_tokens=1024,
tools=tools,
messages=[
{"role": "user", "content": "What's the weather in SF?"},
{"role": "assistant", "content": message.content},
{"role": "user", "content": [
{"type": "tool_result", "tool_use_id": block.id, "content": str(result)}
]}
]
)
Send images for analysis:
import base64
with open("diagram.png", "rb") as f:
image_data = base64.standard_b64encode(f.read()).decode("utf-8")
message = client.messages.create(
model="claude-sonnet-4-0",
max_tokens=1024,
messages=[{
"role": "user",
"content": [
{"type"Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
- 1Install skill using provided installation command
- 2Test with simple use case relevant to your work
- 3Evaluate output quality and relevance
- 4Iterate on prompts to improve results
- 5Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Related Skills
java-coding-standards
18affaan-m/everything-claude-code
Backendsame repoprompt-optimizer
23affaan-m/everything-claude-code
Productivitysame repovideo-editing
19affaan-m/everything-claude-code
Videosame repocaveman
3.3KJuliusBrussee/caveman
Marketingtag: claudecaveman-review
81JuliusBrussee/caveman
Marketingtag: claudeseo-geo
70whyashthakker/agent-skills-marketing
Marketingtag: claudeReviews
4.5★★★★★31 reviews- DDhruvi Jain★★★★★Dec 24, 2024
Registry listing for claude-api matched our evaluation — installs cleanly and behaves as described in the markdown.
- SSophia Tandon★★★★★Dec 4, 2024
claude-api has been reliable in day-to-day use. Documentation quality is above average for community skills.
- KKwame Brown★★★★★Nov 23, 2024
Solid pick for teams standardizing on skills: claude-api is focused, and the summary matches what you get after install.
- OOshnikdeep★★★★★Nov 15, 2024
Keeps context tight: claude-api is the kind of skill you can hand to a new teammate without a long onboarding doc.
- MMaya Brown★★★★★Oct 22, 2024
claude-api fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- AAma Tandon★★★★★Oct 14, 2024
claude-api is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- GGanesh Mohane★★★★★Oct 6, 2024
I recommend claude-api for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- SSophia Sanchez★★★★★Sep 25, 2024
Keeps context tight: claude-api is the kind of skill you can hand to a new teammate without a long onboarding doc.
- BBenjamin Sethi★★★★★Sep 9, 2024
claude-api has been reliable in day-to-day use. Documentation quality is above average for community skills.
- CChinedu Verma★★★★★Aug 28, 2024
claude-api fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 31
1 / 4Discussion
Comments — not star reviews- No comments yet — start the thread.