mugglelisted

# Muggle Test > Telemetry first step: see [`_shared/telemetry-emit.md`](../_shared/telemetry-emit.md). Use `skillName: "muggle"`. Use this as the top-level Muggle Test command router. ## Preferences User preferences are injected by the SessionStart hook into a `Muggle Test Preferences` line in session context (key=value pairs). Resolution: defaults → `~/.muggle-ai/preferences.json` (global) → `<repo>/.muggle-ai/preferences.json` (project). Treat absent prefs as `ask`. This router skill itself does not gate any decision on a preference — it just routes user intent to a downstream skill. Each downstream skill consults its own preferences. For example, `checkForUpdates` is consulted by `muggle-status` (Check 4), not here. If the user types "muggle" with no subcommand and you want to surface a contextual hint about the update-check pref, defer to `muggle-status` rather than reimplementing the gate in this router. ## Menu When user asks for "muggle" with no specific subcommand, use `AskUserQuestion` to present these four options: - "Test a feature — run E2E acceptance tests locally or remotely" → `muggle-test-feature-local` (local) or `muggle-test` (remote/change-driven) - "Build something — implement a feature with E2E acceptance tests and a visual PR" → `muggle-do` - "Health check — verify installation and fix issues" → `muggle-status` (then `muggle-repair` if issues found) - "Upgrade — update to latest version" → `muggle-upgrade` ## Routing If the user intent clearly