---
name: seoinsights
description: "ADMIN-only: pull an insight report for a USER (by email) or a SITE (by domain) from the SeoWatcher /seoreport data — activity, skills/MCP used vs available, owners, and GSC metrics. Triggers on /seoinsights. Requires an admin MCP token."
---

# /seoinsights — admin insight reports (SeoWatcher)

For administrators: get a report **per user** or **per site** combining what people
did in Claude Code (from `/seoreport`) with site ownership and GSC metrics — to see
which working methods correlate with SEO outcomes, and what skills/MCP a user has but
doesn't use (recommendation seeds).

> Access is enforced server-side: the underlying MCP tools require an **admin** token.
> A non-admin running this skill will get a role error — the data never leaves the
> server for non-admins.

## Steps (for the assistant)

1. Ask the admin: **"Report for a USER (email), a SITE (domain), or an OVERVIEW of ALL users?"**
   (optionally a GSC/activity window in days, default 28).
2. Call the matching admin MCP tool on the `seowatcher` server:
   - User → `mcp__seowatcher__seoreport_user` with `{ email, days? }`
   - Site → `mcp__seowatcher__seoreport_site` with `{ domain, days? }`
   - All users → `mcp__seowatcher__seoreport_overview` with `{ days?, limit? }` — one row per
     user with activity + skills/MCP used vs available + `recommend_skills`/`recommend_mcp`
     (what to suggest to each person). Render as a table sorted by activity.
   - Dialogs of a user → `mcp__seowatcher__seoreport_sessions` `{ email }` (list + timing + tools
     + first prompt); one transcript → `mcp__seowatcher__seoreport_session` `{ session_id }`.
   - Effectiveness → `mcp__seowatcher__seoreport_effectiveness` `{ by: "skill"|"mcp"|"domain", days? }`
     — per method: success_rate, avg time/messages, errors/interruptions (which tools work best);
     `by:"domain"` also attaches GSC (methods↔SEO).
3. Present the result clearly:
   - **User:** sessions/activity, skills & MCP used, **unused_skills / unused_mcp** (what to recommend), worked domains, owned sites, and GSC overview for those sites.
   - **Site:** who worked on it, methods/skills used, assigned owners, activity timeline, and the site's GSC metrics — note any apparent method↔SEO relationship (carefully: correlation ≠ causation).

## Notes

- Needs the `seowatcher` MCP configured with an **admin** token (`/mcp` connect).
- Data source: `inventory_claude_sessions` (populated by users running `/seoreport`).
- If a user isn't in `inventory_people`, owner-mapped sites will be empty — only
  tagged/detected domains apply.