agentleFS
Sign inStart free
metagit-aimetagit-ai/metagit-cli/skills/metagit-mcp-resources/SKILL.md

metagit-mcp-resources

Skill4 starsChanged 13 days agoMITView on GitHub

Token-efficient MCP resource ladder for metagit workspaces — catalog, map, layered prompts, project/repo drill-down. Use when the IDE host exposes metagit resources/read instead of shell CLI.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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. Very specific:

    Use this skill when an agent connects via MCP (metagit mcp serve) and should minimize context bloat.

    line 10
  2. Very specific:

    Never read metagit://workspace/config?view=full on large umbrellas unless the operator passed confirm=1.

    line 16

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

Metagit MCP layered resources

Use this skill when an agent connects via MCP (metagit mcp serve) and should minimize context bloat. Prefer resources/read and prompts/get over dumping the full manifest or calling metagit_context_pack tier 2 repeatedly.

<!-- modality:context_reduction -->

Never read metagit://workspace/config?view=full on large umbrellas unless the operator passed confirm=1. Maps, catalog lists, and campaign status are paged.

Session start (MCP)

  1. resources/read → metagit://catalog
  2. metagit://gate/status — confirm state_backend.backend (local vs http) when using shared coordination state
  3. metagit://workspace/map?limit=80
  4. metagit://prompt/workspace/session-start?instructions=0 or prompts/get name workspace/session-start
  5. metagit://session/meta
  6. Once per session window: tool metagit_session_begin when a full bootstrap envelope is required (mutates boundary)

Idle return: metagit://session/digest/summary (read-only; does not bump boundary).

Resource ladder

LayerURIWhen
L0metagit://catalogFirst read every connect
L0metagit://workspace/map?limit=80Paged boundaries, clone existence
L0metagit://session/metaActive project context
L1metagit://prompt/{scope}/{kind}?instructions=0Task procedure
L1metagit://project/{project}/summaryAfter project scope is known
L1metagit://repo/{project}/{repo}/cardSingle-repo health
L1metagit://objectivesShared objective state
L1metagit://approvals/pendingBefore mutating ops
L1metagit://handoffs/openMulti-agent coordination
L2metagit://session/digest/summaryReturn-after-idle
L2metagit://workspace/healthPreflight before sync
L2metagit://workspace/repos/status?summary=1Aggregate index health
L2metagit://events/recent?since=Poll objective/approval/handoff changes
L3metagit://workspace/config?view=summaryManifest counts only
L3metagit://workspace/config?view=full&confirm=1Operator-approved dump only

MCP prompts capability

MethodUse
prompts/listDiscover scope/kind names
prompts/getSame bodies as prompt resources; check _meta.resource_uri

Tools vs resources

NeedResourceTool
Backend modegate/status (state_backend)—
Mapworkspace/map?limit=80metagit_context_pack tier 0 (max_map_repos)
Campaign page—metagit_campaign_status
ADO WIT—metagit_campaign_board_sync (dry_run first)
Repo cardrepo/{p}/{r}/cardmetagit_repo_card
Objectivesobjectivesmetagit_objective_*
Approvalsapprovals/pendingmetagit_approval_*
Handoffshandoffs/openmetagit_handoff_*
Events pollevents/recent?since=metagit_events
Digest (read-only)session/digestmetagit_session_digest
Full bootstrap + boundary—metagit_session_begin
Search / sync / mutations—respective tools

Dispatch plans: metagit_agent_dispatch_plan returns handoff.mcp_resources[] with scoped read order.

Anti-patterns

  • Auto-subscribing to metagit://workspace/config without ?view=summary
  • Calling metagit_context_pack tier 2 on every turn or unscoped on 500+ repos
  • Loading all repo cards when only one repo is in scope
  • metagit_workspace_list with include_workspace: true
  • metagit_campaign_status without a limit page on a large overlay

Spec

Full URI taxonomy: docs/reference/mcp-layered-resources-spec.md

Related skills

  • metagit-sharing-state — METAGIT_STATE_URL, MCP host env, multi-agent setup
  • metagit-context-pack — CLI + tool tier workflow
  • metagit-workspace-scope — gate and boundaries
  • metagit-control-center — ongoing multi-repo coordination

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