Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From claw-mo
Configures mo markdown viewer for current project by scanning .md files, suggesting group watch patterns (docs, plans, specs), and saving config. Use for doc watching or markdown viewer setup.
npx claudepluginhub leejuoh/claude-code-zero --plugin claw-moHow this skill is triggered — by the user, by Claude, or both
Slash command
/claw-mo:claw-mo-setupThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Configure mo markdown viewer with group-based watch patterns for the current project.
Starts mo markdown viewer server for current project using config groups/patterns, migrates config if needed, and opens browser tab via cmux or default.
Serves markdown as live-reloading browser previews using mdserve for complex docs, tables, Mermaid diagrams, and multi-file sets. Handles iterative edits.
Opens markdown files in a live-reloading cmux viewer panel with rich rendering for displaying plans, documentation, or notes alongside the terminal.
Share bugs, ideas, or general feedback.
Configure mo markdown viewer with group-based watch patterns for the current project.
For config schema, port logic, and groups: read ${PLUGIN_DIR}/references/shared.md
Prerequisites check
command -v mo >/dev/null 2>&1 → if missing: brew install k1LoW/tap/mo, stop$CMUX_SURFACE_ID is not set: mention that cmux (https://cmux.dev) provides a built-in browser panel alongside the terminal — ideal for viewing docs while coding. Brief one-liner, don't push.Detect project root: git rev-parse --show-toplevel (fallback: $PWD)
Scan markdown files:
find "$PROJECT_ROOT" -name '*.md' -not -path '*/node_modules/*' -not -path '*/.git/*' -not -path '*/vendor/*' 2>/dev/null | wc -l
Warn if 500+.
List directories with .md files:
find "$PROJECT_ROOT" -name '*.md' -not -path '*/node_modules/*' -not -path '*/.git/*' -not -path '*/vendor/*' 2>/dev/null | sed "s|$PROJECT_ROOT/||" | cut -d/ -f1 | sort -u
Suggest groups based on common patterns found:
docs/ exists → suggest group docs with docs/**/*.mdplans/ or docs/plan/ exists → suggest group plansspecs/ or docs/spec/ exists → suggest group specs.md files exist → suggest group default with *.mdAskUserQuestion: Present suggested groups and port together. Example:
Detected these groups in your project:
- docs: docs/**/*.md (23 files)
- plans: plans/*.md (5 files)
- default: *.md (3 files)
Port: 6342 (auto-assigned from path hash)
Proceed with these? Let me know if you want to add, remove, or change anything.
Save config to ${PLUGIN_DATA_DIR}/config.json (create file if needed, merge if exists). Use v2 groups format.
Offer to start: "Setup complete! Want me to start the server with /claw-mo-up?"
**/*.md can explode: Projects with vendored code may contain thousands of .md files. Always show the count before accepting broad patterns. Guide users toward specific directory patterns.