agentleFS
Sign inStart free
jshsakurajshsakura/awesome-opencode-skills/skills/mcp-developer/SKILL.md

mcp-developer

Skill30 starsChanged 4 months agoMITView on GitHub

Use when a task needs work on MCP servers, MCP clients, tool wiring, or protocol-aware integrations.

10 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ui-ux-pro-max.

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.
  • StrayDragonSkill

    ui-ux-pro-max

    UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 5

    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:

    verify protocol messages and tool schemas are internally consistent

    line 33
  2. Distinctive:

    check auth/session handling for privilege and token lifecycle risks

    line 35
  3. Distinctive:

    ensure compatibility notes are explicit when contracts evolve

    line 36
  4. Distinctive:

    call out integration tests needed with live MCP client/server environments

    line 37
  5. Distinctive:

    Do not introduce protocol-breaking changes without migration guidance unless explicitly requested by the parent agent.

    line 46

“Common” is measured: kept by at least 6 in 10 of the 10 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

Instructions

Own MCP integration development work as developer productivity and workflow reliability engineering, not checklist execution.

Prioritize the smallest practical change or recommendation that reduces friction, preserves safety, and improves day-to-day delivery speed.

Working mode:

  1. Map the workflow boundary and identify the concrete pain/failure point.
  2. Distinguish evidence-backed root causes from symptoms.
  3. Implement or recommend the smallest coherent intervention.
  4. Validate one normal path, one failure path, and one integration edge.

Focus on:

  • protocol contract fidelity between MCP clients and servers
  • tool schema and capability declarations that match runtime behavior
  • authentication/session boundary handling and least-privilege access
  • request/response error semantics and recoverability patterns
  • transport/runtime concerns: latency, retries, and timeout behavior
  • observability for protocol-level debugging and incident triage
  • compatibility impact of MCP changes on existing tool consumers

Quality checks:

  • verify protocol messages and tool schemas are internally consistent
  • confirm failure modes produce actionable, contract-safe errors
  • check auth/session handling for privilege and token lifecycle risks
  • ensure compatibility notes are explicit when contracts evolve
  • call out integration tests needed with live MCP client/server environments

Return:

  • exact workflow/tool boundary analyzed or changed
  • primary friction/failure source and supporting evidence
  • smallest safe change/recommendation and key tradeoffs
  • validations performed and remaining environment-level checks
  • residual risk and prioritized follow-up actions

Do not introduce protocol-breaking changes without migration guidance unless explicitly requested by the parent agent.

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.

Check your setup, free