agentleFS
isaacsightisaacsight/kernel/.agents/skills/mcp-source/SKILL.md

mcp-source

Skill16 starsChanged 4 months agoMITView on GitHub

Switch MCP for Unity package source in connected Unity projects. Use /mcp-source [main|beta|branch|local] to swap between upstream releases, your remote branch, or local dev checkout.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    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
  1. Distinctive:

    If empty or not one of the four valid values, ask the user to choose:

    line 22
  2. Distinctive:

    Run these git commands from the current working directory to find the unity-mcp repo:

    line 30
  3. Very specific:

    Read mcpforunity://project/info for each connected Unity instance (use ListMcpResourcesTool to find available instances).

    line 45
  4. Very specific:

    If no MCP instances are connected, search upward from the current working directory for Packages/manifest.json files using Bash:

    line 48
  5. Distinctive:

    If multiple manifests are found, update all of them (confirming with the user first).

    line 53
  6. Distinctive:

    Read the file with the Read tool

    line 73
  7. Distinctive:

    Use the Edit tool to replace the old value with the new URL

    line 75
  8. Distinctive:

    After updating, tell the user:

    line 80

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

Switch MCP for Unity Package Source

You are switching the com.coplaydev.unity-mcp package source in one or more Unity projects.

allowed-tools

Bash, Read, Edit, ReadMcpResourceTool, ListMcpResourcesTool

Instructions

1. Parse arguments

The user's argument is: $ARGUMENTS

Valid values: main, beta, branch, local, or empty.

If empty or not one of the four valid values, ask the user to choose:

  • main — upstream main branch (stable releases)
  • beta — upstream beta branch (pre-release)
  • branch — your current remote branch (for testing a PR)
  • local — local file reference to your checkout (for live dev iteration)

2. Detect repo context

Run these git commands from the current working directory to find the unity-mcp repo:

git rev-parse --show-toplevel    # → repo_root
git rev-parse --abbrev-ref HEAD  # → branch_name
git remote get-url origin        # → origin_url

Convert SSH origins to HTTPS: if origin_url starts with git@github.com:, transform it to https://github.com/{owner}/{repo}.git.

3. Discover target Unity projects

Try two approaches to find Packages/manifest.json files to update:

Approach A — MCP resources (preferred): Read mcpforunity://project/info for each connected Unity instance (use ListMcpResourcesTool to find available instances). Extract projectRoot and use {projectRoot}/Packages/manifest.json.

Approach B — filesystem fallback: If no MCP instances are connected, search upward from the current working directory for Packages/manifest.json files using Bash:

find "$(pwd)" -maxdepth 3 -name "manifest.json" -path "*/Packages/manifest.json" 2>/dev/null

If multiple manifests are found, update all of them (confirming with the user first).

4. Build the package URL

Based on the user's selection, construct the dependency value:

SelectionURL
mainhttps://github.com/CoplayDev/unity-mcp.git?path=/MCPForUnity#main
betahttps://github.com/CoplayDev/unity-mcp.git?path=/MCPForUnity#beta
branch{origin_https}?path=/MCPForUnity#{branch_name}
localfile:{repo_root}/MCPForUnity

For branch: use the HTTPS-normalized origin URL and current git branch name. For local: use the absolute path to the repo root with file: prefix (no //), e.g. file:/Users/davidsarno/unity-mcp/MCPForUnity.

5. Update each manifest

For each discovered manifest.json:

  1. Read the file with the Read tool
  2. Find the "com.coplaydev.unity-mcp" dependency line
  3. Use the Edit tool to replace the old value with the new URL
  4. Report what was changed: old value → new value, file path

6. Report results

After updating, tell the user:

  • Which manifests were updated
  • The old and new package source values
  • Remind them: "Unity will re-resolve the package automatically. If it doesn't, open Package Manager and click Refresh."

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.