extra-orgextra-org/extra/.claude/skills/mcp-tools/SKILL.md

mcp-tools

Skill119 starsChanged 5 months agoMITView on GitHub

Working on Python plugin tools, MCP server connections, tool invocation, or tool tracing. Primary task is tasks/0007-mcp-tools-and-permissions.md.

3 other projects use a version of this.

Adopted by

Most recently taken up by

komluk/scaffoldingtheir own version, first seen Nov 7, 2026
sazardev/gocatheir own version, first seen Oct 8, 2026
operately/operatelytheir own version, first seen Oct 8, 2026

Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
operately/operately★ 618same name
sazardev/goca★ 299same name
komluk/scaffolding★ 16same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architecture-reviewSkill
- code-reviewSkill
- documentationSkill
- git-workflowSkill
- project-architectureSkill
- prompt-renderingSkill
- refactoringSkill
- runtime-engineSkill
- senior-python-engineeringSkill
- sidecar-auth-contextSkill
- skill-authoringSkill
- testingSkill
- vercel-react-best-practicesSkill
- yaml-schemaSkill

The file

We split this skill into the rules it gives an agent

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

0
Common
Most of the 3 edited versions we read keep these.
0
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

Very specific:
Do not edit this file directly.
line 10
Very specific:
Use this when working on Python plugin tools, MCP server connections, tool invocation, or tool tracing.
line 18

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

<!--
This file is generated by tools/skills.
Do not edit this file directly.
Edit .ai/skills/mcp-tools.md and run `make generate-ai`.
-->

Skill: MCP & Tools

When to use this skill

Use this when working on Python plugin tools, MCP server connections, tool invocation, or tool tracing. Primary task: tasks/0007-mcp-tools-and-permissions.md.

Files to read first

AGENTS.md
docs/MCP_AND_TOOLS.md
docs/RUNTIME_LIFECYCLE.md

Architecture rules

Resolver plugins run before a node; tool plugins are exposed to the LLM during execution.
MCP clients are created once and shared; never per request.
Per-request data flows via ExecutionContext / ctx.
Prompt text is not a security boundary.
Secrets never live in YAML; they are redacted in traces.

Implementation rules

Implement tool registry and MCP integration in src/agentplatform/tools.
Load plugin classes once where possible.
Invoke configured class/method references with ctx.
Validate tool and MCP ids during validation/compilation; runtime should use resolved bindings.
Hold MCP clients on the long-lived runtime.

Validation checklist

Tool plugin references load and invoke through the registry.
MCP connections are created once and reused.
Per-request context does not leak through shared state.
Tool/MCP calls are traced with redaction.
Tests cover success and failure with fakes.
make check passes.

Common mistakes to avoid

Recreating MCP connections per request.
Treating resolvers as tools or tools as resolvers.
Skipping trace redaction.
Relying on prompt wording for enforcement.

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