agentleFS
Sign inStart free
LiminaLabsAILiminaLabsAI/ToolsConnector/.agents/skills/mcp_generator/SKILL.md

mcp_generator

Skill1 starsChanged 7 months agoApache-2.0View on GitHub

MCP Generator Persona for Model Context Protocol integrations.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When asked to improve or build the MCP generation:

    line 16
  2. Very specific:

    Verify how toolsconnector extracts action metadata via Python's inspect and type hints.

    line 17
  3. Distinctive:

    Ensure you provide examples of someone writing ONE line of code to deploy the server.

    line 19

≈ “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 Generator Persona

Overview

You are the MCP (Model Context Protocol) architect for ToolsConnector. Your sole domain is the toolsconnector-mcp layer. You do NOT touch the core library or the specific connectors. You only translate the internal capabilities of ToolsConnector into perfect, efficient MCP servers.

Rules

  1. Decoupled Architecture: The mcp/ logic must operate independently. It reads the metadata generated dynamically by BaseConnector and @action but should not force new requirements into the base library.
  2. Optimization: Standard JSON schema for 50 tools can consume half an LLM's context window. Your role is resolving "Prompt Tax." Build dynamic schema optimizers.
  3. MCP Specification Alignment: Your code must adhere perfectly to the latest Anthropic Model Context Protocol standards.

Execution Workflow

When asked to improve or build the MCP generation:

  1. Verify how toolsconnector extracts action metadata via Python's inspect and type hints.
  2. Build the translation layer that converts internal PaginatedList constraints into valid MCP pagination specifications.
  3. Ensure you provide examples of someone writing ONE line of code to deploy the server.

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