Initial commit: moreminimore-service content pipeline

- 9 mm* skills (orchestrator, article, social, publish, analytics)
- 6 dependency skills (content-writer, geo-optimizer, etc.)
- 3 analytics scripts (GSC, Google Ads, Meta Ads)
- Config template + setup guide
- SOUL-MM.md persona extension
- OrbitOS integration reference

scripts/search-console.sh

@@ -0,0 +1,38 @@
+#!/bin/bash
+# Google Search Console Bridge Script
+# ====================================
+# Placeholder — implement when GSC API access is configured
+#
+# Required setup:
+# 1. Google Cloud Project with Search Console API enabled
+# 2. GCP service account (or OAuth) with access to client's GSC property
+# 3. Client must add service account email as GSC property user
+#
+# Usage:
+#   ./search-console.sh <action> <site-url> [options]
+#
+# Actions:
+#   top-queries     Get top queries by clicks/impressions
+#   top-pages       Get top pages by clicks/impressions
+#   trends          Get traffic trends over time
+#   content-gaps    Find queries ranking 11-30 with no dedicated page
+#   ctr-gaps        Find high-impression, low-CTR opportunities
+#
+# This script is called by the moreminimore-orchestrator when
+# analytics monitoring is active (Phase 3 — Analytics Loop).
+
+echo "⚠️  Google Search Console API script not yet implemented."
+echo ""
+echo "Required before use:"
+echo "  1. Create Google Cloud Project"
+echo "  2. Enable Search Console API: gcloud services enable searchconsole.googleapis.com"
+echo "  3. Set up service account or application-default credentials"
+echo "  4. Client adds service account email to GSC property as user"
+echo ""
+echo "The seo-analysis skill has full GSC scripts at:"
+echo "  ~/.hermes/skills/seo-analysis/scripts/"
+echo ""
+echo "Consider adapting those scripts for multi-client use."
+echo ""
+echo "See: /Users/kunthawat/Gitea/moreminimore-service-system/scripts/README.md"
+exit 1