@cmo-so/skills 0.4.1 → 0.5.0

package/skills/cmo-website-setup/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: cmo-website-setup
-description: "Get a website ready in CMO.so: verify ownership by email or DNS, detect the platform, and hand off the publishing connection to a computer. Use when the user says things like \"add my website to CMO.so\"; \"verify my website\"; \"I didn't get the verification code\"; \"how do I connect WordPress?\"; \"what platform is my site on?\"; \"why isn't Maggie publishing to my site?\". Needs the CMO.so MCP server."
+description: "Get a website ready in CMO.so: verify ownership by email, DNS, the WordPress plugin or by asking the team, detect the platform, and hand off the publishing connection to a computer. Use when the user says things like \"add my website to CMO.so\"; \"verify my website\"; \"I didn't get the verification code\"; \"how do I connect WordPress?\"; \"what platform is my site on?\"; \"why isn't Maggie publishing to my site?\". Needs the CMO.so MCP server."
 license: MIT
 metadata:
   category: "core"
   tier: "core"
   funnel_stage: "all"
   channels: "cmo.so,wordpress,shopify,wix,api"
-  version: "0.4.1"
+  version: "0.5.0"
   docs: "https://cmo.so/skills/cmo-website-setup"
 ---
 # Website setup & verification
@@ -37,7 +37,10 @@ Choose the route with one question: "Do you have an email address at example.com
 |---|---|---|
 | User has a mailbox at the site's domain | Email code | Minutes |
 | No such mailbox, but DNS access (registrar, Cloudflare, host panel) | DNS TXT record | Minutes to hours |
-| Neither | Ask whoever manages the domain or email; or send the DNS steps to them via `handoff_to_desktop` | Varies |
+| WordPress site, user can install a plugin | WordPress plugin: install the CMO.so connector and add its key; that verifies and connects in one go | Minutes |
+| None of these | "Ask us": the user emails maggie@cmo.so or messages the team on WhatsApp from the app, and the team verifies it by hand; or send the DNS steps to whoever manages the domain via `handoff_to_desktop` | Hours |
+
+The WordPress-plugin and "Ask us" routes are in the CMO.so app only (Home → "Verify my domain"); there is no tool for them. Point the user there, use `wordpress_plugin_get` to check the plugin and key afterwards, then `setup_status_get` to confirm.
 
 **Email code** (both are changes: preview, then confirm):
 1. `verify_email_start` with the address at the site's domain. Free providers (Gmail, Outlook and similar) are refused; that is by design, not an error to work around.

package/skills/cmo-weekly-report/SKILL.md

@@ -7,7 +7,7 @@ metadata:
   tier: "core"
   funnel_stage: "all"
   channels: "cmo.so,google-search,ai-search"
-  version: "0.4.1"
+  version: "0.5.0"
   docs: "https://cmo.so/skills/cmo-weekly-report"
 ---
 # Weekly marketing report
@@ -28,10 +28,11 @@ A plain-language briefing on what Maggie did and what it achieved: posts publish
 
 ### 1. Gather (read-only, no confirmation needed)
 1. `results_summary` with `days: "7"` (or `"30"`): posts published, ideas waiting, AI visibility average.
-2. `gsc_status_get`. If connected, `gsc_performance_get` with `period: "30d"` (it also accepts `"90d"` and `"12m"`, nothing shorter): totals for clicks, impressions, CTR and average position, the previous period and the change, the best day, and up to eight top pages. If it answers `needs_sync`, say the numbers have not been fetched yet. If not connected, note it and continue.
+2. `gsc_status_get`. If connected, `gsc_performance_get` with `period: "30d"` (it also accepts `"90d"` and `"12m"`, nothing shorter): totals for clicks, impressions, CTR and average position, the previous period and the change, the best day, and up to eight top pages. If it answers `needs_sync`, say the numbers have not been fetched yet. If not connected, note it, offer `gsc_connect_link` once (the user signs in with the Google account that manages the site in Search Console), and continue.
 3. `ai_visibility_get`: average score, watched prompts with score, position and cited pages, 30-day trend. If it reports no checks yet, that is "not measured", not zero.
 4. `content_performance_list` with `sort: "clicks"` (top articles), then with `band: "no_traffic"` (tracked articles not getting traffic yet). Each item carries its band (`no_data`, `no_traffic`, `emerging`, `strong`) and a suggested `next_step`; `counts` gives how many articles sit in each band.
 5. `inbox_list`: anything waiting.
+6. Optionally `seo_audit_get` (the app's "Website health"): PageSpeed scores and top technical issues. Mention it only if a score dropped or an issue is new; if it is out of date, say so rather than starting `seo_audit_run` unasked.
 
 For "summarise the month", a quarter, or any 30 / 90-day view, add `report_overview_get` with `range: "30d"` or `"90d"` (`"7d"` also works): blog posts published, split by topic, against the period before, plus Search Console totals, AI visibility and LinkedIn posts sent. Use it as the backbone of the "This week" and "Search" sections for that period and keep `results_summary` for the quick weekly view; do not mix periods from the two in one line.
 

package/skills/cmo-x-growth/SKILL.md

@@ -7,7 +7,7 @@ metadata:
   tier: "standalone"
   funnel_stage: "awareness"
   channels: "x"
-  version: "0.4.1"
+  version: "0.5.0"
   docs: "https://cmo.so/skills/cmo-x-growth"
 ---
 # X (Twitter) growth

package/skills/cmo-youtube/SKILL.md

@@ -7,7 +7,7 @@ metadata:
   tier: "standalone"
   funnel_stage: "awareness"
   channels: "youtube"
-  version: "0.4.1"
+  version: "0.5.0"
   docs: "https://cmo.so/skills/cmo-youtube"
 ---
 # YouTube growth