Add skill routing rules + prefix mm trigger words

- Updated SOUL-MM.md: Skill Routing Rules section
- All mm* skills now use 'mm' prefix in trigger words
- Clear separation from MCP-based skills (meta-ads, google-ads)
- mm-analytics-orchestrator explicitly states 'uses scripts NOT MCP'
- Routing table: which skill to use for which task

SOUL-MM.md

@@ -75,6 +75,29 @@ Data Stage → Content Stage → Publish Article → Social Stage → Publish So
 | mm-blog-categories | Fetch/cache blog categories |
 | mm-analytics | Pull analytics data |
 
+## Skill Routing Rules
+
+**When to use mm* skills vs existing skills:**
+
+| Task | Use THIS | NOT this |
+|------|----------|----------|
+| Pull Meta Ads data | `mm_meta_ads.py` script | `meta-ads` skill (needs MCP) |
+| Pull Google Ads data | `mm_google_ads.py` script | `google-ads` skill (needs MCP) |
+| Pull GSC data | `mm_gsc.py` script | `seo-analysis` skill (needs gcloud) |
+| Analytics report | `mm-analytics-orchestrator` | `ads-meta` / `ads-google` |
+| Content pipeline | `mm-content-orchestrator` | individual skills directly |
+| Deep ad analysis | `ads-meta` / `ads-google` (if MCP available) | — |
+| SEO audit | `seo-analysis` (if gcloud available) | — |
+
+**Trigger words for mm* skills:**
+- "mm analytics", "mm report", "วิเคราะห์ผล"
+- "mm pipeline", "mm content", "เริ่มงาน content"
+- "mm publish", "publish บทความ"
+
+**When existing skills trigger accidentally:**
+- If `meta-ads` or `google-ads` triggers and asks for MCP → switch to mm* scripts
+- If `seo-analysis` triggers and asks for gcloud → switch to `mm_gsc.py`
+
 ## OrbitOS Integration
 
 This project uses OrbitOS vault conventions. Load these skills when needed: