agentleFS
codewhale-hqcodewhale-hq/codewhale-plugin-marketplace/skills/mcp-builder/SKILL.md

mcp-builder

Skill5 starsChanged 18 days agoMITView on GitHub

Design, build, configure, or debug Model Context Protocol servers for codewhale, including stdio and HTTP/SSE transports.

186 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use chinese-code-review, chinese-commit-conventions and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Leodorareluctant259Skill

    chinese-code-review

    中文代码审查规范——在保持专业严谨的同时,用符合国内团队文化的方式给出有效反馈

    Also in 8 projects that use this

  • Leodorareluctant259Skill

    chinese-commit-conventions

    中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化

    Also in 8 projects that use this

  • ComposioHQSkill

    codebase-migrate

    Run large codebase migrations and multi-file refactors. Uses the Composio CLI to coordinate issue tracking, batched PRs, and CI verification while the agent executes the transforms locally across hundreds of files.

    Also in 5 projects that use this

  • truongtv22Skill

    Problem-Solving Techniques

    Apply systematic problem-solving techniques for complexity spirals (simplification cascades), innovation blocks (collision-zone thinking), recurring patterns (meta-pattern recognition), assumption constraints (inversion exercise), scale uncertainty (scale game), and dispatch when stuck. Techniques derived from Microsoft Amplifier project patterns adapted for immediate application.

    Also in 5 projects that use this

  • ArogyaReddySkill

    skill-share

    A skill that creates new Claude skills and automatically shares them on Slack using Rube for seamless team collaboration and skill discovery.

    Also in 26 projects that use this

  • AnthropicSkill

    academy-guide

    Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.

    Also in 8 projects that use this

  • +2 more from Leodorareluctant259

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 170 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Use this skill when the user asks to create, configure, or debug an MCP server or tool integration.

    line 8
  2. Distinctive:

    Prefer stdio MCP servers for local tools and HTTP/SSE for remote services.

    line 13
  3. Distinctive:

    Keep tool schemas small, typed, and explicit.

    line 14
  4. Distinctive:

    Put secrets in environment variables, never in committed config.

    line 16
  5. Distinctive:

    Add timeouts and clear error messages around external APIs.

    line 19
  6. Very specific:

    Add the server with codewhale mcp add or edit ~/.codewhale/mcp.json.

    line 42
  7. Very specific:

    Run codewhale mcp validate, then codewhale mcp tools.

    line 43
  8. Distinctive:

    Test one happy path and one failure path before calling it done.

    line 44

“Common” is measured: kept by at least 6 in 10 of the 170 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

MCP Builder

Use this skill when the user asks to create, configure, or debug an MCP server or tool integration.

Design Rules

  • Prefer stdio MCP servers for local tools and HTTP/SSE for remote services.
  • Keep tool schemas small, typed, and explicit. Return structured JSON where possible.
  • Put secrets in environment variables, never in committed config.
  • For HTTP/SSE clients, send Accept: application/json, text/event-stream by default unless the server explicitly requires something else.
  • Add timeouts and clear error messages around external APIs.

Codewhale Setup

Common commands:

codewhale mcp init
codewhale mcp add my-server --command node --arg server.js
codewhale mcp add remote-server --url http://127.0.0.1:3000/mcp
codewhale mcp list
codewhale mcp validate
codewhale mcp tools

HTTP/SSE entries can include per-server headers in ~/.codewhale/mcp.json when credentials or custom routing headers are required.

Workflow

  1. Define the service boundary and the minimum useful tools.
  2. Choose transport and credential handling.
  3. Implement the server using a maintained MCP SDK when available.
  4. Add the server with codewhale mcp add or edit ~/.codewhale/mcp.json.
  5. Run codewhale mcp validate, then codewhale mcp tools.
  6. Test one happy path and one failure path before calling it done.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.