agentleFS
Sign inStart free
kinqsradiokinqsradio/orbyn-fullstack-skills/skills/orbyn-mcp-builder/SKILL.md

orbyn-mcp-builder

Skill4 starsChanged 5 days agoMITView on GitHub

Design, build and evaluate a Model Context Protocol (MCP) server in TypeScript or Python with Anthropic's bundled guide and evaluation harness. Use when creating or reworking an MCP server or its tools; for model-powered app behavior use orbyn-ai-application.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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:

    Follow the consuming project's instructions and requested scope.

    line 8
  2. Distinctive:

    Read the bundled guide in full, then only the reference it points to for your language: the TypeScript or

    line 11
  3. Distinctive:

    Installing is a change: Ask before adding SDK packages to the project.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 builder

Follow the consuming project's instructions and requested scope; use the portable defaults only where guidance is missing.

Read the bundled guide in full, then only the reference it points to for your language: the TypeScript or Python guide, the best practices and the evaluation guide.

Where these rules override the source

  1. Use the project's stack. An existing server keeps its language and SDK. For a new one, choose with stack selection when the choice is open.
  2. Fetch docs with the host's own tool. Where the source says "WebFetch", use whatever web or documentation tool the host has; offline, say which current fact is unverified.
  3. Design the tools as a contract. Each tool's name, inputs, errors, authority and side effects follow orbyn-backend-design and the tool-design guidance in orbyn-ai-application. A tool that writes, sends or deletes says so and needs the user's confirmation path.
  4. Secrets stay out of code. Credentials come from the environment or the host's secret store, never from tool arguments or the repository.
  5. Evaluations cost money. scripts/evaluation.py calls a model. Run it only with the user's OK, and report the model and the result.
  6. Installing is a change. Ask before adding SDK packages to the project.

Source and updates

Bundled from anthropics/skills at 2c5958e, Apache-2.0, with its LICENSE.txt and a snapshot.json of file hashes. Refresh it with upstream review.

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