agentleFS
PantaniPantani/ableton-mind/.agents/skills/mcp-server-development/SKILL.md

mcp-server-development

Skill9 starsChanged 5 months agoMITView on GitHub

Implementation patterns for the ableton-mind TypeScript MCP server: Zod tools, resources, prompts, bridge client, verify loop, transactions and idempotency.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when implementing or reviewing src/server, src/tools, src/resources, src/prompts, src/live-client or src/feedback.

    line 8
  2. Distinctive:

    Keep a persistent JSON-RPC TCP client with request IDs, timeout, reconnect backoff and notification events.

    line 26

“Common” is measured: kept by at least 6 in 10 of the 5 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 Server Development — TS/Node Patterns

Use this skill when implementing or reviewing src/server, src/tools, src/resources, src/prompts, src/live-client or src/feedback.

Stack

TypeScript 5, Node 20, ESM, @modelcontextprotocol/sdk, zod, tsup, biome, vitest and native net.

Tool Rules

  • Tool names use snake_case and align with Python handler names.
  • Descriptions explain what changes, idempotency and side effects.
  • Input and output schemas use Zod. Avoid any and unknown except debug sinks.
  • Handlers are async and receive input plus ctx.
  • Mutations read before write and verify by reading back.
  • Return ok, verified and diff where relevant.
  • Errors are structured and never call process.exit.

Bridge Client

Keep a persistent JSON-RPC TCP client with request IDs, timeout, reconnect backoff and notification events. Tools talk through the context abstraction, not by importing low-level clients directly.

Resources and Prompts

Resources expose live state or embedded knowledge without mutating Live. Prompts are short client-visible templates and should not replace documentation.

Tests

Each tool needs at least one happy path and one validation/error path. Integration tests use a mock bridge by default and a real bridge only when explicitly enabled.

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.

Reviews can't be read right now.

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.