kitlisted
Install: claude install-skill x-mesh/xm
<Purpose>
Show available x-mesh tools and their installation status.
</Purpose>
<Use_When>
- User asks "what tools are available"
- User says "xm", "x-mesh tools"
</Use_When>
<Do_Not_Use_When>
- User wants a specific tool (use x-build or x-op directly)
</Do_Not_Use_When>
# xm — x-mesh Toolkit
## First-Run Init Check
**Before executing any xm subcommand** (except `init` itself), verify the project is initialized:
1. Check `test -f .claude/hooks/trace-session.mjs` in the current working directory.
2. If **missing**, pause the requested command and prompt via AskUserQuestion:
- header: `xm init`
- option 1 label: `Yes (권장)` — description: `hooks + settings + x-sync client 설치`
- option 2 label: `Skip sync` — description: `hooks + settings만, x-sync 제외`
- option 3 label: `No` — description: `이번만 건너뛰기`
3. Before the AskUserQuestion, print:
```
⚠ xm이 이 프로젝트에 초기화되지 않았습니다.
설치 항목: trace hook, block-marketplace hook, .claude/settings.json, x-sync client
```
4. On **Yes** → run `xm init`. On **Skip sync** → run `xm init --skip-sync`. On **No** → proceed with the original command without init (do not re-prompt this session).
5. After init completes, resume the originally requested subcommand.
Skip this check when the user explicitly invokes `xm init`, `xm doctor`, or passes `--no-init-check`.
For a fuller picture (not just trace-session.mjs), suggest `xm doctor` — but the fast `test -f` check is sufficient as the entry gate.
## Model Routing
| Subcommand