agentsclimarketplace

Mct cli

Skill JLugagne/claude-skills/tools/mct-cli/skills/mct-cli

Reference guide for mct (claude-mercato), a Git-based package manager for Claude agent and skill definitions. Use this skill whenever the user asks how to use mct, asks about mct commands, wants to install/update/search/export agents or skills, asks about markets, drift, sync, pinning, import/export, or any other mct workflow. Also trigger when the user is looking for skills or agents to add to their project, wants to find a skill for a specific task, asks "is there a skill for X", "find me a skill that does Y", "what skills are available", or wants to browse or discover available Claude skills and agents. Trigger even if the user says "claude-mercato", "mct add", "mct sync", or just asks "how do I install an agent from a market?"From its SKILL.md

Install
npx -y skills add JLugagne/claude-skills --skill mct-cli

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

8.0 KB, ~1.8k tokens by cl100k_base, as published. Nobody here has run it

mct — Claude Agent & Skill Package Manager

mct manages Claude agent and skill markdown files distributed through Git repositories called markets. No central registry. No server. Just Git.


Core Concepts

TermWhat it is
MarketA Git repo containing agent/skill .md files in agents/ and/or skills/
EntryA single .md file (agent or skill) from a market
RefUnique entry ID: market/path/to/file.md
ProfileA directory grouping within a market (e.g. mymarket/dev/go)
DriftLocal modifications to an installed file (detected via MD5 checksum)
Managed skillA skill auto-installed as a dependency of an agent

State files (never edit manually):

  • Config: ~/.config/mct/config.yml
  • Checksums: ~/.cache/mct/mct.checksums.json
  • Sync state: ~/.cache/mct/mct.state.json
  • Market clones: ~/.cache/mct/{market-name}/

Global Flags

--config       path to config file
--cache        cache directory
--offline      disable all network operations
--verbose      detailed log output
--quiet        suppress output except errors
--no-color     disable ANSI colors
--ci           non-interactive mode

Most commands also support --json for machine-readable output.


Markets

Register and manage Git repositories as markets.

mct market add <name> <url>        # Register a Git repo as a market
  --branch string   branch to track (default: main)
  --trusted         skip breaking-change confirmation prompts
  --read-only       index only, never install from it
  --no-clone        register without cloning immediately

mct market list                    # List all registered markets (alias: mct markets)
mct market info <name>             # Detailed market info (entries, last sync, etc.)
mct market rename <old> <new>      # Rename a market
mct market set <name> <key> <val>  # Update a market property
mct market remove <name>           # Unregister a market
  --force       skip installed-entries check
  --keep-cache  keep the local clone

Market names must be kebab-case, 2–64 characters.


Installing & Removing Entries

mct add <ref>          # Install an entry (alias: mct install)
  --pin <sha>       pin to a specific commit SHA
  --no-deps         skip auto-installing required skills
  --dry-run         preview without making changes
  --accept-breaking accept breaking-change flag without prompt

mct remove             # Remove an installed entry
  --ref <ref>   (required)

mct add automatically installs skill dependencies listed in the entry's frontmatter requires_skills field, and marks them as managed by the agent.


Sync & Updates

mct refresh            # Fetch latest from all markets (no local changes)
mct update             # Apply pending upstream changes to installed files
  --ref <ref>       only update this entry
  --market <name>   filter to one market
  --dry-run
  --agents-only / --skills-only
  --all-keep        keep all local changes
  --all-delete      discard all local changes
  --all-merge       merge all changes
  --accept-breaking

mct sync               # refresh + update in one step
  --market, --dry-run, --accept-breaking, --all-merge

Status & Drift

mct check              # Show status of all installed entries (alias: mct status)
  --market <name>   filter
  --short           one-line summary

Status indicators:

SymbolMeaning
okClean — up to date, no local changes
upUpdate available (no local changes)
~Drift — locally modified, no update
!Both drift and update available
xDeleted from upstream
+New in registry (not installed)
oOrphaned — market removed
?Unknown state

Search & List

mct search <query>     # BM25 full-text search across all markets
  --limit int       max results (default: 10)
  --type agent|skill
  --market <name>   scope search to a single market
  --category <cat>
  --installed / --not-installed
  --include-deleted

mct list               # List all installed entries

Results are grouped by profile. Use --market to narrow results when multiple markets are registered.


Version Pinning & Diff

mct pin --ref <ref> --sha <sha>    # Lock entry to a specific commit
mct diff --ref <ref>               # Open external difftool: local vs. upstream

Pruning Deleted Entries

When an upstream entry is deleted it becomes tombstoned (still exists locally, flagged as deleted).

mct prune
  --ref <ref>       specific entry
  --all-keep        keep all locally (stop tracking)
  --all-remove      delete all locally

Import / Export

Portable JSON format for sharing setups across machines.

mct export [file]      # Export all markets + installed profiles to JSON
                       # (omit file to write to stdout)

mct import <file>      # Import markets and entries from JSON
  --dry-run            preview without changes
  --yes                auto-confirm adding markets not registered locally
                       (without --yes, unknown markets are skipped in --json
                        mode, or prompted interactively otherwise)

Configuration

mct config get [key]   # Show config value(s)
mct config set <key> <value>

Settable keys: ssh_enabled, local_path, conflict_policy, drift_policy, difftool, stale_after, namespace_dirs.


Other Commands

mct init               # Initialize mct in the current project
mct conflicts          # Show all conflicts (ref collisions, dep issues)
mct sync-state         # Print raw sync state for all markets
mct index              # Index operations
  --bench              measure indexing performance
  --dump               dump index as JSON
mct tui                # Interactive terminal UI (bubbletea)
mct lint [dir]         # Check a local directory as a market (default: current dir)
                       # Reports profile count, agent/skill counts, and issues:
                       #   error  invalid/missing frontmatter, unknown type
                       #   warn   missing README.md, missing tags, empty profile

Entry Frontmatter Reference

Fields mct reads from .md files in markets:

---
description: "..."    # required: short description
author: "..."         # optional
breaking_change: true # optional: flag for breaking changes
deprecated: true      # optional
requires_skills:      # optional: skill dependencies
  - file: skills/go-test.md
    pin: abc123       # optional: pin this dep to a SHA
---

Fields mct injects when installing (do not add these manually — mct will reject the file):

mct_ref: mymarket/dev/go/agents/go-developer.md
mct_version: "abc1234 2024-01-15"
mct_market: mymarket
mct_installed_at: "2024-01-15T10:30:00Z"

Market Repository Layout

A market is a Git repo with this structure:

<namespace>/<profile>/
  README.md              # optional but recommended — frontmatter: tags, description
  agents/
    my-agent.md
  skills/
    my-skill.md

Example: dev/go-hexagonal/agents/go-architect.md → ref mymarket/dev/go-hexagonal/agents/go-architect.md

See MARKET.md in this repo for the full market authoring guide.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most context ai engineering skills give in ~1.8k tokens

Counted across 1,193 of the 1,976 authors here whose files we hold, read 2026-08-07

  • Dispatch a fresh implementer subagent per taskin 48 of 1193, across 19 files
  • Dispatch a final code reviewer after all tasksin 33 of 1193, across 8 files
  • Provide full task text to the subagentin 30 of 1193, across 9 files
  • Review spec compliance before code qualityin 27 of 1193, across 10 files
  • Make the hook script executablein 26 of 1193, across 8 files
  • Re-snapshot after navigation or DOM changesin 25 of 1193, across 19 files
  • Read files before editing themin 22 of 1193, across 11 files
  • Answer subagent questions before proceedingin 22 of 1193, across 7 files
  • Mark task complete in TodoWrite after approvalin 22 of 1193, across 6 files
  • Merge hook into existing settingsin 21 of 1193, across 3 files
  • Ask if installation is global or projectin 20 of 1193, across 2 files
  • Copy the hook script to target locationin 20 of 1193, across 2 files

Said here and by no other author read

  • install entries using mct add
  • remove entries using mct remove
  • fetch upstream changes using mct refresh
  • apply pending changes using mct update
  • show installed entry status using mct check
  • search across markets using mct search

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,144. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.