The /mm-add skill installs a MemoryMarket pack into your workspace, driven by your AI agent. You only confirm decisions — the agent runs every CLI command. It wraps mm install and an optional inline wiki-integration step (Phase 4) into one conversational flow.
This page mirrors the canonical packages/cli/skills/mm-add/SKILL.md file shipped in the memorymarket npm package. The SKILL.md is what your agent actually reads at invocation time — if this page drifts from it, the SKILL.md wins.
| Flag | Required | Purpose |
|---|---|---|
pack-ref | no | Pack reference (e.g. @user/slug) or local path to a pack directory. If omitted, the skill asks you. |
--scope | no | project (default — ./.memorymarket/<slug>/) or user (~/.memorymarket/<slug>/). |
--agent | no | Force-target a specific agent (claude-code, codex, cursor, windsurf, openclaw). If omitted, mm install auto-detects. |
--no-wiki | no | Skip the optional wiki-integration phase even if a Karpathy-style wiki is detected. |
The agent confirms the mm CLI is on your PATH before doing anything else.
mm --help. The skill does NOT use mm whoami here — whoami requires auth credentials and exits non-zero on a fresh install even when mm is on PATH.If you are installing from the registry (@user/slug), mm install requires auth. The skill runs mm whoami and, if not authenticated, runs mm login. Local-path installs (--from-path) do not need auth.
@ari/10k-mrr-in-24h) or a local directory path.”@, matches @<user>/<slug> (lowercase a-z/0-9/dash). Local path: must be an existing directory containing manifest.json.--scope was passed: “Project scope (./.memorymarket/<slug>/, applies to this directory only) or user scope (~/.memorymarket/<slug>/, applies to every project)?” Default: project.--agent was not passed, the skill lets mm install auto-detect.mm install <pack-ref> --scope <scope>. Local path: mm install --from-path <path> --scope <scope>. Adds --agent <name> if provided.--from-path, the skill surfaces the CLI's signature-skip warning. Local-path installs bypass Ed25519 signature verification — registry installs are the safer default../.memorymarket/<slug>/ (or ~/.memorymarket/<slug>/) and patched the host agent's rules file (managed block in CLAUDE.md, AGENTS.md, .cursor/rules/<slug>.md, etc.) so the pack is active immediately. A sidecar metadata file is written to .memorymarket/.meta/<slug>.json — it tracks the installed agent + source so mm update and mm uninstall know what to touch. Do not delete it.<slug> to <path>. The pack is active in your agent — try a relevant prompt.”NO_ENTITLEMENT — you have not purchased a paid pack. The skill prints the pack URL https://memorymarket.co/pack/<slug> and stops.SIGNATURE_INVALID — the pack failed signature verification. The skill stops and never retries blindly.This phase runs only if a Karpathy-style wiki is detected and --no-wiki was not passed.
./knowledge-base/wiki/index.md. If absent, skips Phase 4 silently.memory/*.md into matching wiki pages, appending a “From <slug>pack” section with new content and source attribution. Wikilinks are added conservatively. There is no separate skill for this step.mm install actually wrote — read from the CLI output.mm install with different flags after a NO_ENTITLEMENT or SIGNATURE_INVALID error. Those are terminal.mm install already manages a clearly-marked block.--scope decision. Project vs user scope changes where the pack lands and which projects it affects.