# Getting started

Install the maintenance package from npm, then let it install the CLI and supported host plugins:

```bash
npm install -g @mutmutco/hub
mmi-hub install
mmi-hub status
```

Keep automatic updates enabled. Install converges the tools immediately and enables an hourly
schedule on supported systems. Status is read-only: it reports installed versions, scheduling,
the last run, and failures. A missing, unsupported, or failing schedule is not a healthy installation.
Use `mmi-hub autoupdate on` to enable scheduling and `mmi-hub update` for an immediate update.
Do not edit plugin caches or installation records by hand.

Install and update use the shared installer run, including plain terminal output.
`mmi-hub install --dry-run` previews changes without enabling the schedule.

Complete the host's trust and reload step: reload plugins or restart Claude Code, restart Codex,
reload the Cursor window, restart JervCode, or start a fresh Hermes process. An existing session
may still hold the old skill catalog until then. The updater manages the MMI plugin on each
supported host present on the machine, and on Hermes that means every profile home as well as the
default one; each running profile needs its own fresh process. It does not grant repository or
vault access.

Authenticate GitHub for your assigned repository. In its checkout, run `mmi-cli onboard` for
readiness and `mmi-cli oracle board read` for work. Use `mmi-cli commands --json` to discover routes
and `mmi-cli explain <command> --json` for exact syntax. Check `mmi-hub status` separately for
machine-wide updater health.

Ask for **MMI help** for the short introduction or open the [org guide](../SKILL.md) for one topic.
The guide travels with the plugin on every release; it requires neither a Hub checkout nor wiki access.