mcp-builder-do
Enforces best practices for building MCP tools with TypeScript and Zod.
Install
mkdir -p .claude/skills/mcp-builder-do && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18104" && unzip -o skill.zip -d .claude/skills/mcp-builder-do && rm skill.zipInstalls to .claude/skills/mcp-builder-do
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Sub-skill of mcp-builder: Do (+1).Key capabilities
- →Use TypeScript for type safety
- →Validate all inputs with Zod
- →Provide clear, actionable error messages
- →Use environment variables for secrets
- →Implement rate limiting for external APIs
- →Add tool annotations for destructive operations
How it works
The skill provides mandatory guidelines for tool creation, enforcing practices like TypeScript for type safety, Zod for input validation, and environment variables for secrets.
Inputs & outputs
When to use mcp-builder-do
- →Validating tool inputs
- →Setting up tool security
- →Improving error reporting in tools
About this skill
Do (+1)
Do
- Use TypeScript for type safety
- Validate all inputs with Zod
- Provide clear, actionable error messages
- Use environment variables for secrets
- Implement rate limiting for external APIs
- Add tool annotations for destructive operations
Don't
- Hardcode API keys or secrets
- Skip input validation
- Return raw error stack traces
- Create overly complex tool schemas
- Ignore rate limits on external services
When not to use it
- →When hardcoding API keys or secrets
- →When skipping input validation
- →When returning raw error stack traces
Limitations
- →Does not permit hardcoding API keys or secrets
- →Does not allow skipping input validation
- →Does not support returning raw error stack traces
How it compares
This skill standardizes tool implementation by providing explicit 'Do' and 'Don't' rules, which differs from ad-hoc tool development without predefined guidelines.
Compared to similar skills
mcp-builder-do side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| mcp-builder-do (this skill) | 0 | 3mo | No flags | Beginner |
| mcporter | 7 | 2mo | No flags | Intermediate |
| calcom-api | 2 | 3mo | No flags | Intermediate |
| dust-mcp-server | 1 | 10d | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by vamseeachanta
View all by vamseeachanta →You might also like
mcporter
openclaw
Use the mcporter CLI to list, configure, auth, and call MCP servers/tools directly (HTTP or stdio), including ad-hoc servers, config edits, and CLI/type generation.
calcom-api
calcom
Interact with the Cal.com API v2 to manage scheduling, bookings, event types, availability, and calendars. Use this skill when building integrations that need to create or manage bookings, check availability, configure event types, or sync calendars with Cal.com's scheduling infrastructure.
dust-mcp-server
dust-tt
Step-by-step guide for creating new internal MCP server integrations in Dust that connect to remote platforms (Jira, HubSpot, Salesforce, etc.). Use when adding a new MCP server, implementing a platform integration, or connecting Dust to a new external service.
developing-genkit-tooling
firebase
Best practices for authoring Genkit tooling, including CLI commands and MCP server tools. Covers naming conventions, architectural patterns, and consistency guidelines.
juicebox-rate-limits
jeremylongshore
Implement Juicebox rate limiting and backoff. Use when handling API quotas, implementing retry logic, or optimizing request throughput. Trigger with phrases like "juicebox rate limit", "juicebox quota", "juicebox throttling", "juicebox backoff".
clay-sdk-patterns
jeremylongshore
Apply production-ready Clay SDK patterns for TypeScript and Python. Use when implementing Clay integrations, refactoring SDK usage, or establishing team coding standards for Clay. Trigger with phrases like "clay SDK patterns", "clay best practices", "clay code patterns", "idiomatic clay".