· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →Sealmetrics SL v1.11.0
Analyze your marketing data
From the developer
Not specified in the available declarations: capabilities, limitations, pricing & account requirements.
Where am I leaving money on the table?
Developer declarations; not independently tested. Listing last checked Nov 19, 2026. Package observed Nov 19, 2026.
From the marketplace listing
Seal Copilot turns your Sealmetrics data into decisions: a verdict first, the evidence with numbers, one action, and a date to check it. It diagnoses drops down to the campaign that caused them, finds revenue left on the table, audits catalog friction per product, watches the cart during the day against a learned baseline, and reviews your tracking setup. Fourteen procedures over one methodology, with playbooks for ecommerce, hotels and SaaS that it picks from your own tracking. Every figure comes from a tool result in the same session: it never invents a number, and it refuses to conclude when the sample is too small. Requires a Sealmetrics account.
Language: English · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →--- name: calibrate-watchdog description: > One-off calibration run that learns a site's natural add-to-cart (or booking-start) rhythm and stores it as the baseline the hourly watchdog compares against. Run once per site before scheduling `cart-watchdog`, and again after any tracking change or a major shift in traffic volume. Trigger on: "calibrate the watchdog", "set up cart monitoring", "learn my cart baseline", "calibrar el vigilante", "prepare the watchdog", or when `cart-watchdog` reports that no baseline exists. disable-model-invocation: true short-description: 'Learn a site''s hourly add-to-cart rhythm so the watchdog has a baseline. Run once before cart-watchdog. Use for "calibrate watchdog", "calibrar", "set up monitoring".' --- # Calibrate Watchdog Before writing your answer, read `examples/output.md` in this skill directory and match its density, structure and tone. It is the reference for what a good run of this skill looks like. Build the hour-of-week baseline that makes intraday monitoring meaningful, and store it so the hourly watchdog never has to rebuild it. Budget: ≤40 tool calls — high because it runs once and every later watchdog run costs ≤6. This is a **manual, explicit** skill. Never run it from a casual question and never run it on a schedule. ## Why this is a separate skill The MCP has no hourly time series on the aggregated tools. Hourly counts come only from `get_microconversions_raw`, which is capped at a 31-day range and 100 rows per page. Rebuilding a 4-week baseline on every hourly check would cost hundreds of calls, so the baseline is built once, here, and cached. ## Step 1 — Identify the watched event and the volume 1. `list_microconversion_types` — pick the add-to-cart equivalent for stores (`add_to_cart`, `add_to_basket`, `atc`, `cart_add`) or `booking_start` and equivalents for hotels. State which event you chose. 2. `get_microconversions(conversion_type=<event>, period=30d)` — the 30-day total. This decides the calibration mode and costs one call. | 30d volume | Mode | What you build | |---|---|---| | ≤ 4,000 events | **A — full** | 168 cells (day-of-week × hour) from 28 days | | 4,001 – 30,000 | **B — sampled** | 168 cells from the most recent complete week | | > 30,000 | **C — daily** | 7 day-of-week daily medians, no hourly detail | Say which mode you used and why. The mode goes in the stored baseline. ## Step 2 — Pull the events **Mode A.** Four windows of 7 days, walking back 28 days. For each window: ``` get_microconversions_raw(conversion_type=[<event>], start_date=YYYY-MM-DD, end_date=YYYY-MM-DD, limit=100, page=1…) ``` Page until a page returns fewer than 100 rows, or until 9 pages in that window — whichever comes first. Hard cap 36 pages across all four windows. **Mode B.** The most recent complete Monday–Sunday week only, same call, paging up to 30 pages. A single week is a real shape but a noisier one: store `weeks: 1` so the watchdog widens its tolerance. **Mode C.** Skip the raw tool entirely. Make 7 calls, one per day of the last complete week: ``` get_microconversions(conversion_type=<event>, start_date=D, end_date=D) ``` That gives a daily total per day of week. At this volume an outage is visible within an hour at day level, so hourly cells are not worth 300 calls. If any window returns zero rows, say the event has no data in that period and stop — a baseline built on nothing is worse than none. ## Step 3 — Build the baseline Every row carries `date`, `hour` (local, 0–23) and `timestamp_local`. Bucket by `date` and `hour` directly — do not parse the timestamp, and never use `timestamp_utc`, since the site's own day boundaries are what matter. **Modes A and B.** Bucket events into day-of-week × hour-of-day. For each of the 168 cells store: - `median` — median event count for that cell across the weeks you have (in mode B, the single week's count is the median) - `gap` — typical minutes between events in that cell: `60 / medi
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
--- name: cart-watchdog description: > Intraday watchdog for add-to-cart activity. Detects unusual silence or spikes vs the site's own learned hour-of-week baseline (not a fixed threshold) and rules out bots before alerting. Requires a baseline from the `calibrate-watchdog` skill. Trigger on: "is my cart alive", "check add to cart", "carrito parado", "cart watchdog", "no estamos vendiendo", "intraday alert", "checkout watchdog", or when run from a scheduled task. For hotels, substitutes `booking_start` for `add_to_cart`. disable-model-invocation: true short-description: 'Intraday check of add-to-cart against the learned baseline. Silent when healthy. Use for "check the cart", "is the cart working", "cómo va el carrito", or hourly runs.' --- # Cart Watchdog Before writing your answer, read `examples/output.md` in this skill directory and match its density, structure and tone. It is the reference for what a good run of this skill looks like. Catch live problems — broken AtC button, payment outage, tracking gap — before the daily report does. Budget: ≤6 tool calls. Designed for **scheduled execution**, hourly during business hours. ## Step 0 — Load the baseline Read `<state-dir>/<site_id>/watchdog-baseline.json`. - **No file** → do not improvise a threshold. Reply in one line: *"No baseline yet — run `calibrate-watchdog` once and I can watch this properly."* Stop. - **Expired** (`expires_at` in the past) → still run, but prefix the status with "baseline stale, recalibrate" and widen every threshold by half. - **Mode C** (daily-only baseline) → skip the hourly logic below and judge on the day-to-date total alone. Say that hour-level detail is unavailable. The file also carries `last_status` from the previous run. You need it: a 🔴 requires two consecutive bad checks, and this is the only way to know about the previous one. ## Step 1 — Today's volume so far (1 call) `get_microconversions(conversion_type=<event>, period=today)` This returns the day total, not an hourly series. Compare it against the baseline's `cumulative[day_of_week][current_hour]` — the expected count for the hours elapsed so far today, in the site's timezone. **Status from the ratio** `actual / expected_to_date`: - 🟢 **Healthy** — ratio ≥ 0.5 - ⚠️ **Watch** — ratio between 0.2 and 0.5 - 🔴 **Act** — ratio < 0.2 **and** `last_status` was already ⚠️ or 🔴 A single low reading is never 🔴 on its own. Two consecutive are. For spikes, mirror it: ratio ≥ 3 is 🔴 (likely bots), ≥ 2 is ⚠️. **Quiet cells are not incidents.** If the sum of medians for the elapsed hours is below 5 events, there is not enough signal — report 🟢 and say the window is too quiet to judge. ## Step 2 — Locate the silence (1–2 calls, only if not 🟢) `get_microconversions_raw(conversion_type=[<event>], period=today, limit=100)` Rows carry `hour` (local, 0–23) and `timestamp_local`. Use `hour` to bucket and `timestamp_local` for the most recent event. Page once more only if the first page does not contain the latest activity. Two extra signals from this: - **Time since last event** vs the current cell's `gap`: more than 2× gap supports ⚠️, more than 3× gap supports 🔴. - **When the drop started** — the last hour with normal-looking volume is the incident start time. Name it; it is what the user needs to match against their deploy log. ## Step 3 — Rule out bots (1 call, mandatory before any 🔴) `get_bot_stats(days=1)` - Drop coinciding with a bot spike → the drop is real but the metric was previously inflated. Say so and recommend recalibrating. - Spike that is bots → demote 🔴 to ⚠️ "bot inflation" and explain. - **Empty result** → agent analytics is off, not 0% bots. Keep the status but mark it "unvalidated for bots" (see `methodology.md`). ## Step 4 — Isolate the cause (≤2 calls, only if 🔴) One call is enough — `get_microconversion_details(conversion_type=<event>, period=today)` returns `by_device`, `by_source`, `by_country` and `by_landing_page` togeth
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
--- name: channel-mix-optimizer description: > Suggests how to reallocate marketing budget across paid channels without needing ad-spend data, using Revenue Per Entrance, CR, and AOV from Sealmetrics. Trigger on: "where should I invest", "budget reallocation", "channel mix", "scale or cut", "qué canal escalar", "shift budget", "media plan", "what to scale", or any allocation question. Always pairs the recommendation with the caveat that ROAS requires real spend from the ad platform. argument-hint: "[period]" short-description: 'Reallocate paid budget across channels by revenue per entrance. Use for "which channel is best", "where should I spend", "budget allocation", "dónde invierto".' --- # Channel Mix Optimizer Before writing your answer, read `examples/output.md` in this skill directory and match its density, structure and tone. It is the reference for what a good run of this skill looks like. Recommend budget shifts across paid channels using **Revenue Per Entrance (RPE)** as the proxy for ROAS. Budget: ≤10 tool calls. ## Why RPE (and why state the caveat) Sealmetrics has no ad spend. ROAS = revenue / spend is impossible from this data alone. But RPE = revenue / entrances is a leading proxy: at similar CPCs, the channel with higher RPE has higher ROAS. **Always tell the user that proportional spend is the working assumption and to pull real CPC/CPM from the ad platform to confirm.** Never present RPE as ROAS. ## Step 1 — Map the paid channels 1. `get_top_channels(period=90d)` — full channel list. 2. `list_channel_rules` — confirm which channels the user classifies as paid (Paid Search, Paid Social, Display, Affiliates, Paid Email…). If the user has not configured paid vs organic split well, run `get_traffic_mediums(period=30d)` and treat `cpc`, `paid`, `display`, `paidsocial`, `cpm`, `ppc` as paid by default; say so. ## Step 2 — Channel-level scorecard For each paid channel pull (≤4 calls total via the compact `get_top_*` where possible): - `get_top_channels(period=this_quarter)` and `get_top_channels(period=last_quarter)` — volume + trend. `get_top_channels` has no `compare`; diff the pair yourself. - `get_traffic_mediums(period=90d, compare=previous)` — conversions and revenue per medium in one call, which is where paid/organic actually splits. - AOV per paid channel: `get_conversions(period=90d, utm_medium=<paid medium>)` once per medium (≤4 calls). There is no `group_by` on `get_conversions`. Compute per channel: | Metric | Formula | Use | |---|---|---| | Entrances | from get_channels | volume | | CR | conversions / entrances | quality | | AOV | revenue / conversions | ticket | | **RPE** | revenue / entrances | the ranking metric | | Trend | RPE this 30d vs previous 30d | momentum | Site weighted-average RPE is the reference line. ## Step 3 — Campaign-level inside each paid channel For the top 2 paid channels by revenue: `get_campaigns(period=90d, sort_by=revenue, limit=20, utm_medium=<paid>, compare=previous)` Apply per-campaign: - **Scale candidate** — RPE ≥ 1.3 × channel RPE AND ≥30 conversions AND trend ≥ flat. - **Cut/optimize candidate** — RPE ≤ 0.5 × channel RPE AND ≥500 entrances AND ≥30d running. - **Maintain** — neither. ## Step 4 — Cross-channel reallocation logic The recommendation is **relative**, not absolute. Use the form: > "Channel A delivers €X per entrance vs Channel B's €Y. Assuming similar > CPC, every euro shifted from B to A should produce ≈ X/Y times more > revenue. To confirm, pull CPC from your ads platform and compare > CPC×(1/CR_A)×AOV_A vs CPC×(1/CR_B)×AOV_B." Never tell the user "spend more on Google, less on Meta" as an absolute — budget decisions need their cost reality. Provide the **ratio** and the **verification formula**. ## Output format 1. **Channel scorecard table** (paid channels only): entrances · CR · AOV · RPE · RPE vs site avg · 90d trend. 2. **Top 3 scale candidates** (campaign level): name · entrances · CR · AOV · RP
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
--- name: cost-reduction description: > Find operational waste — money bleeding through the site itself, not through media spend. Scans for bot traffic tax, zombie pages, broken tracking, dead UTMs, country flood without ROI, stale alerts/webhooks, and unused segments. Trigger on: "reduce expenses", "reducir gastos", "where am I wasting money", "operational waste", "fix the bleeding", "audit costs", "limpiar mi cuenta", "dónde estoy gastando de más", "operational audit", "tracking waste". NOT for media-spend optimization (use channel-mix-optimizer for that). short-description: 'Find operational waste: bots, zombie pages, dead campaigns, broken tracking. Use for "reduce costs", "what is wasting money", "reducir costes", "operational audit".' --- # Cost Reduction (Operational Waste) Before writing your answer, read `examples/output.md` in this skill directory and match its density, structure and tone. It is the reference for what a good run of this skill looks like. Find waste Sealmetrics can see **without** ad-spend data: traffic that costs money on the infrastructure side but produces nothing, instrumentation that's broken, and unused features. Budget: ≤12 calls. > Scope note for the user: this skill targets **operational expenses** > (infra, dev time, fraud, tool license use), not **media costs**. For ad > spend efficiency, run `channel-mix-optimizer`. ## Patterns scanned (report only those that fire) ### 1. Bot tax - Detect: `get_bot_stats(days=30)` and `get_suspicious_sessions(min_score=70, limit=50)` — neither takes a `period`. An empty `get_bot_stats` means agent analytics is off, not 0% bots: say so and skip this pattern. If bot share ≥ 15% of total sessions, or one source has bot share ≥ 40%, the cost is real (CDN egress, log storage, polluted analytics). - Recommend: enable Cloudflare / WAF blocking on top bot sources; exclude them from Sealmetrics if they ride a UTM the user controls. - Impact: bot sessions × site's per-session infra cost (user must supply €/1k sessions; if not, state hours saved in analyst time instead). ### 2. Zombie pages - Detect: `get_pages(period=90d, sort_by=entrances, limit=50)`. Flag pages with ≥1,000 entrances, 0 conversions, bounce > site average + 15 pts, no UTM source (organic dead end). - Recommend: redirect to a working page or remove from sitemap; if intentionally informational, add an exit-intent CTA. - Impact: entrances × site CR × AOV = revenue lost to dead ends. ### 3. Broken tracking (microconversion decay) - Detect: `get_microconversions(period=30d, compare=previous)` for each type from `list_microconversion_types` (the parameter is `conversion_type`, not `type`). Any type with ≥50% drop while `get_overview` sessions are flat = instrumentation broken. - Recommend: developer must redeploy the missing event; confirm the start date by re-running the same call on narrower `start_date`/`end_date` windows until the drop is bracketed. - Impact: hidden — every dependent analysis (funnel, product-friction) has been wrong since the regression. State the date the decay started. ### 4. Dead UTM tax - Detect: `get_campaigns(period=90d, sort_by=entrances, limit=50)` and `get_terms(period=90d, sort_by=entrances, limit=50)` filtered to paid. Flag campaigns/terms with ≥200 entrances and 0 conversions over the full 90d — likely paused upstream but still receiving stale clicks (cached creatives, app-store redirects, scrapers). - Recommend: confirm with the ads platform that the campaign is paused; if yes, add the source/term to bot exclusion to stop polluting analytics. - Impact: ad budget still being charged for those clicks (user pulls spend) + cleaner reports. ### 5. Country flood without ROI - Detect: `get_countries(period=90d, sort_by=entrances)`. Flag countries with ≥5% of total entrances, 0 conversions in 90d, and bot share <30% (so it is not just bots from that geo). - Recommend: geo-block in the ads platform; add to
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
--- name: diagnose-drop description: > Root-cause diagnosis for a drop or spike in Sealmetrics metrics. Trigger on: "why did conversions drop", "why did sales fall", "traffic spiked, why", "what happened yesterday/this week", "qué ha pasado con", "revenue is down", or any cause-seeking question about a metric change. argument-hint: "[metric] [period]" short-description: 'Root-cause diagnosis of a drop or spike. Use for "why did conversions drop", "sales fell", "traffic spiked, why", "what happened this week", "qué ha pasado con", "revenue is down".' --- # Diagnose Drop (or Spike) Before writing your answer, read `examples/output.md` in this skill directory and match its density, structure and tone. It is the reference for what a good run of this skill looks like. Isolate the root cause of a metric change. Budget: ≤12 tool calls. Follow the cause hierarchy from `skills/seal-copilot/references/methodology.md` strictly — work down, stop at the first isolated cause. ## Procedure 0. Confirm the change: `get_overview` for the affected period with `compare=previous`. Totals are under `traffic` / `conversions`; the delta is `traffic_change` / `conversions_change`; the daily `*_series` show exactly which day it broke. If the user's claim is not visible in data, say so and show what you see instead. 1. **Bots/tracking:** `get_bot_stats(days=30)`. Read it with the three-outcome rule in `methodology.md` — an empty result means agent analytics is off, not 0% bots. **When bots are the cause the diagnosis is not finished until you have named the source.** Call `get_top_referrers` yourself — a single referrer at 90%+ bounce is the usual shape — and put its name in the cause statement. Do not tell the user to go and look: "it is bots" is an observation, "it is bots from cheap-traffic.example, block it at the CDN" is the finding they asked for. That call takes priority over every optional one, including anything gathered only to fill `profile.json`. Sudden near-zero on one page → check `get_pages(path_filter=...)` for a tag lost in a deploy. For a broken microconversion event (cart, checkout), compare `get_microconversions(period=30d, compare=previous)` per type — a single type collapsing while others hold is an instrumentation regression, not a demand problem. Cross-reference the `cart-watchdog` baseline if AtC is the affected metric. 2. **Channel:** `get_top_channels(period=this_week)` vs `get_top_channels(period=last_week)` (or the `this_month`/`last_month` pair for a monthly drop) — `get_top_channels` has no `compare`, so diff the pair yourself. All channels down evenly → jump to step 7. 3. **Campaign:** `get_campaigns(compare=previous, utm_source/medium filters)`. 4. **Landing/term:** `get_landing_pages(compare=previous)` and/or `get_terms(compare=previous)` filtered to the campaign. 5. **Device/country/browser:** `get_devices(compare=previous)` returns `by_device`, `by_browser` and `by_os` in one response, each row with `*_prev` twins — no separate browser or OS call needed. Add `get_countries(compare=previous)`. A collapse isolated to Safari, or to one iOS version, points at ITP or a rendering bug, not at demand. Country is timezone-derived — treat a country-only signal as directional. 6. **Product/SKU** (ecommerce only): if the drop concentrates on purchases but channels look uniform, run `get_property_breakdown` on the product identifier from `list_property_keys` for the affected vs prior period — a single SKU going out of stock or losing a top variant can move overall revenue noticeably. 7. **Seasonality — addressed, never skipped.** Re-run `get_overview` with `compare=yoy`: flat year over year means seasonal, so say so and stop. You may skip that call **only** when the isolation itself excludes seasonality — a single campaign or channel collapsed while its neighbours held flat, and no season does that to one line a
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
---
name: funnel-analysis
description: >
Analyze the conversion funnel in Sealmetrics — find where users drop off
and why. Trigger on: "analyze my funnel", "where do users drop off",
"cart abandonment", "checkout analysis", "booking funnel", "análisis de
funnel", "why don't visitors convert", or questions about steps between
visit and purchase/booking.
short-description: 'Find where the conversion funnel leaks. Use for "funnel analysis", "where do users drop off", "checkout abandonment", "dónde abandonan", "conversion path".'
---
# Funnel Analysis
Before writing your answer, read `examples/output.md` in this skill directory
and match its density, structure and tone. It is the reference for what a good
run of this skill looks like.
Find the weakest funnel stage and isolate its cause. Budget: ≤10 calls.
Vertical playbooks: `skills/seal-copilot/references/ecommerce-playbook.md`
(stores) and `skills/seal-copilot/references/hotels-playbook.md` (hotels).
## Procedure
1. `get_funnel(period=30d)` — the configured funnel with per-step dropoff.
It answers `{ error: "…" }` as JSON when no funnel is configured; check
for `error` before reading `steps`, and build the funnel from
microconversions instead.
2. `list_microconversion_types` — map the customer's event names to
canonical stages (product_view/add_to_cart/start_checkout/purchase for
stores; search/room_view/booking_start/booking for hotels).
3. Compute stage-to-stage ratios; identify the **weakest stage** relative
to the site's own history (`compare=previous` via
`get_microconversions`).
4. Segment the weakest stage to isolate cause (1 call).
`get_microconversion_details(conversion_type=<stage>)` returns
`by_device`, `by_source`, `by_country` and `by_landing_page` together, each
with `count` and `percentage`. Read all four from the one response.
5. Triangulate per the methodology: gap only on mobile → UX; gap
everywhere → offer/price/shipping; gap in one country → payment or
language.
6. **Per-SKU funnel** (ecommerce, optional, ≤2 calls). If the weakest
stage is `view_item → add_to_cart`, the leak is product-specific —
run `get_property_breakdown` on the product identifier for both
stages and surface the worst SKUs. Hand off to the `product-friction`
skill for the full per-SKU treatment.
## Output format
1. **Funnel table:** stage → volume → step CR → change vs previous.
2. **Weakest link:** one sentence naming the stage and the segment where
the gap concentrates, with numbers.
3. **Hypothesis ranked list (max 3):** each with the evidence that supports
it and a concrete test or fix.
4. **Impact:** conversions recovered if the weak stage matched its
best-segment rate, in € using site AOV.
5. **Verify:** re-run plan after the fix ships.
7. **Entry-path check** (1 call, optional). `get_landing_pages_by_content_group(
period=30d)` — if one content group supplies most entrances but almost none
of the conversions, the funnel problem starts before the first stage. This
is the common shape on blog-heavy and SaaS sites; see pattern 14.
If the site has no funnel configured and no microconversions, say so and
offer the `setup-audit` skill instead of improvising. If microconversions
exist but their property naming is unknown, suggest `property-explorer`
as a one-time first step.
---
Log the run in `<state-dir>/<site_id>/runs.jsonl` with exactly these fields
and no others: `ts` (ISO timestamp, UTC), `skill`, `calls` (the number of
Sealmetrics calls you made, counted), `budget` (this skill's documented
ceiling, a number — `10` here), `verdict` (one of `on_track`, `watch`, `act`,
`kpis_only`, `refused`, `error`, or the score for an audit), `scheduled`
(boolean), `notes` (one line). The first real audit wrote `calls_used` and a
free-text verdict because this footer said "calls used" in prose; the field
names are the contract. Skip silently if the path is not writable.
Referenced files: 1 — file references are metadata, not package contents.
--- name: install-sealmetrics description: > Install Sealmetrics on a site from scratch: create the site if needed, place the tracking snippet in the codebase, confirm the first hit arrives, then instrument the conversions and microconversions the business actually needs. Trigger on: "install Sealmetrics", "set up Sealmetrics", "add analytics to this site", "instalar Sealmetrics", "configurar el píxel", "I have no tracking yet", "add the tracking code", "instrument my checkout", or when another skill finds that a site has no data at all. argument-hint: "[domain]" short-description: 'Install Sealmetrics from scratch: create the site, place the pixel, verify it, instrument events. Use for "install Sealmetrics", "set up tracking", "instalar Sealmetrics".' --- # Install Sealmetrics Take a site from no analytics to measured and verified. This is the only skill that writes code, and the only one that can create an account — both are gated below. Budget: ≤15 tool calls plus whatever editing the codebase takes. Before writing your answer, read `examples/output.md` in this skill directory and match its density, structure and tone. ## Step 0 — Find out where you are starting 1. `get_setup_status` — has a site already been provisioned in this session? 2. `list_sites` — does the account already have sites? If a site for this domain exists, **skip provisioning entirely** and go to Step 2. Creating a duplicate site splits the data and is hard to undo. State which of the three starting points applies before doing anything: no account, account without this site, or site already exists. ## Step 1 — Create the site (only if there is genuinely no site) `provision_site` creates a real account on the user's behalf and emails them a claim link. Treat it as the user's decision, never yours: 1. Show them the terms link — https://sealmetrics.com/terms — and say plainly that provisioning creates a free Sealmetrics account tied to their email. 2. Ask for the email address, the site name and the domain. Do not guess an email from git config, the environment, or anything else you happen to know. 3. **Wait for the user to say, in their own words, that they accept the terms.** Only then call `provision_site(accept_terms=true, email=…, site_name=…, domain=…)`. Never pass `accept_terms=true` on your own initiative. If the user has not explicitly accepted in the conversation, stop and ask. If they would rather sign up on the website themselves, that is a perfectly good answer — tell them to come back with the account id and continue from Step 2. After it succeeds, tell them to check their email for the claim link, because the account has no password until they set one. ## Step 2 — Work out where the snippet goes `detect_framework(path=<repo root>)` when you have the repository. Without a repo it returns `unknown` plus the manual guide, which is fine — you will hand the snippet to the user instead of placing it. `get_tracking_code(site_id=…)` returns `script_tag` (the exact tag to place), `tracker_url`, a `js_api` block whose `signatures[].call` strings are the pageview, conversion and microconversion calls to use verbatim, an `implementation_guide` with `spa_support` and `content_grouping`, and worked `examples` per vertical. Use those signatures as written — do not paraphrase them into a slightly different API. **Placement rules that matter more than the framework:** - The snippet goes in `<head>`, and it must load **before** anything that calls `sealmetrics.*`. Most "sealmetrics is not defined" reports are a tag manager firing before the tracker. - One installation per site. Two copies double every pageview. - In a single-page app, the tracker must be told about route changes rather than reloading — otherwise you get one pageview per session, or duplicates, depending on how the router is wired. Follow the API reference for the framework you detected. Place it, show the diff, and say which file you ed
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
---
name: monday-briefing
description: >
The single proactive report the customer sees first thing every Monday:
weekly performance verdict + top opportunity + watchdog status, on one
screen, email-shareable. Trigger on: "monday briefing", "morning report",
"weekly briefing", "informe del lunes", "start my week", "what should I
do this week", "lunes", "executive briefing", or when run from the
scheduled Cowork job.
disable-model-invocation: true
short-description: 'The one-page Monday briefing: verdict, week vs last, what worked, one opportunity, watchdog. Use for "Monday briefing", "briefing", "resumen del lunes", or a scheduled run.'
---
# Monday Briefing
Before writing your answer, read `examples/output.md` in this skill directory
and match its density, structure and tone. It is the reference for what a good
run of this skill looks like.
The Monday-morning one-pager. Combines the highlights of three skills
into a 6-block report the user can forward to their team. Budget: ≤15
calls. Designed for **scheduled execution** — `/schedule` in Claude Code, or
the equivalent scheduled task in Cowork ("every Monday at 8 am in [site
timezone]").
## Composition
This skill **calls down** to three other skills' procedures but runs them
in compact mode — do not produce three full reports, produce one merged
report. Each section caps at the line counts below.
1. Weekly health check — slim (KPIs + verdict only, no findings).
2. Opportunity scan — top 1 only (the highest-€ pattern that fires).
3. Cart-watchdog — current status only (no historical baseline detail).
If any sub-step errors, show "—" for that section, do not abort the rest.
## Procedure
### Block 0 — Follow-up (0–2 calls)
Read `<state-dir>/<site_id>/recommendations.jsonl`. For entries with
`status: open` and `verify_on` today or earlier, re-measure and mark them
verified or failed (see `skills/seal-copilot/references/state-schema.md`).
At most two re-measurements per briefing — the rest wait a week. If nothing
is due, this block produces no output at all.
### Block A — Snapshot (3 calls)
1. `get_overview(period=7d, compare=previous)` (for hotels also
`compare=yoy`).
2. `get_top_channels(period=7d)` — ranked, no `compare` available.
3. `get_campaigns(period=7d, sort_by=revenue, limit=5)` — use the full tool
when you need sorting; `get_top_campaigns` is ranked by entrances only.
### Block B — Opportunity radar (3–5 calls)
Pick the **single highest-impact pattern** that fires from this short list
(do not run the full pattern library):
- Hidden star campaign (top CR + AOV, low volume) — `get_campaigns(
sort_by=revenue, limit=20, compare=previous)`.
- Leaky campaign (high entrances, low CR) — same call, opposite end.
- Mobile gap (mobile CR <50% desktop) — `get_device_types(period=7d)`.
- Untapped country (high CR, no campaign) —
`get_countries(period=30d, sort_by=conversions, limit=10)`. Country is
timezone-derived: report it as a question, not a spend recommendation.
Pick one only — the one with the largest € impact. Do not list the others.
### Block C — Watchdog status (2 calls)
- `get_microconversions(conversion_type=<atc-equivalent>, period=today)` —
today's volume so far, compared against the stored watchdog baseline if
`calibrate-watchdog` has run. Without a baseline, compare to
`get_microconversions(conversion_type=<atc>, period=yesterday)` and say the
comparison is coarse.
- `get_bot_stats(days=7)` — bot share trend. Empty means agent analytics is
off, not 0%.
Status line: `🟢 normal` / `⚠️ watch — <reason>` / `🔴 act now — <reason>`.
### Block D — Validation (0 calls)
Reuse the `get_bot_stats(days=7)` result from Block C. If it was empty or
returned 403, mark every mover in Block A "unvalidated for bots".
## Output format (the one-pager)
```
🦭 Seal Copilot — Monday Briefing · <site> · <week dates>
🎯 VERDICT: <✅ on track | ⚠️ watch | 🔴 act now>
<one sentence summarizing the week>
📊 THIS WEEK vs LAST
| Entrances | CR | ConversPreview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
--- name: opportunity-scan description: > Scan Sealmetrics data for revenue opportunities — money left on the table. Trigger on: "where am I losing money", "find opportunities", "what should I optimize", "how can I improve my campaigns", "dónde pierdo dinero", "what would you change", "audit my marketing", or any open-ended optimization request. short-description: 'Scan for revenue left on the table. Use for "where am I losing money", "find opportunities", "what should I optimize", "dónde pierdo dinero", "audit my marketing".' --- # Opportunity Scan Before writing your answer, read `examples/output.md` in this skill directory and match its density, structure and tone. It is the reference for what a good run of this skill looks like. Run the pattern library against current data and report what fires. Patterns and detection logic: `skills/seal-copilot/references/opportunity-patterns.md` (14 patterns covering revenue lift, friction repair, and waste reduction). Thresholds: `skills/seal-copilot/references/methodology.md`. Budget: ≤12 tool calls. > Scope: this skill is a revenue-opportunity scan. For media-budget > reallocation use `channel-mix-optimizer`; for operational waste use > `cost-reduction`; for per-SKU PDP issues use `product-friction`. This > skill cross-references those when a finding clearly belongs there. ## Procedure 0. **Read the ledger.** Load `<state-dir>/<site_id>/recommendations.jsonl`. Do not re-report a pattern that already has an `open` entry for the same subject unless its impact has grown ≥50% — then report it as an escalation and name the date it was first flagged. Entries marked `discarded` stay suppressed for 90 days. See `skills/seal-copilot/references/state-schema.md`. 1. Baseline (3 calls): `get_overview(30d, compare=previous)`, `get_top_channels(30d)`, `get_conversions(30d)` — site averages for CR and AOV, needed by every pattern. 2. Campaign patterns (1–2 calls): `get_campaigns(30d, sort_by=entrances, limit=50)` — screen for patterns 1 (leaky) and 2 (hidden star) in one pass. 3. Landing pattern (1 call): `get_landing_pages(30d, sort_by=bounce_rate)` — pattern 3. 4. Device pattern (1 call): `get_device_types(30d)` — pattern 4. 5. Property pattern (2 calls): `list_property_keys` → `get_property_breakdown` on the most business-relevant key — pattern 7. For ecommerce, if a product property exists (`sku`, `product_id`, `item_id`, `product_name`), additionally screen pattern 11 (catalog friction) by computing the view→AtC ratio across the top viewed SKUs; if it fires, recommend the full `product-friction` skill for depth. 6. Pick at most 2 more patterns based on vertical: content-group mismatch (14) via `get_content_groups` for blog-heavy or SaaS accounts, terms (5) for heavy SEM users, countries (6) for international sites, micro→macro (10) if microconversions are tracked, RPE gap (12) for accounts running multiple paid channels, intraday gap (13) only if a watchdog baseline already exists (`calibrate-watchdog` has run). 7. Validate any anomaly with `get_bot_stats(days=30)` — pattern 9 — before reporting. An empty result means agent analytics is off, not 0% bots: mark the finding "unvalidated for bots". ## Output format **Max 3 opportunities, ordered by estimated revenue impact.** Each has all five parts below; none is optional. Two runs out of three dropped the last one when the finding felt obvious — a recommendation without a way to check it is an opinion, and it cannot go into the ledger. - **Name + pattern** (e.g. "Hidden star: campaign summer-sale-es") - **Evidence:** the numbers, the period, vs what baseline - **Action:** specific and executable this week - **Impact:** estimated €/month with the assumption stated - **Verify:** the tool to re-run, the metric that should move, and when (2–4 weeks; one booking cycle for hotels). Write the word "Verify". Do not report how many tool calls you used. Then one line list
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
---
name: product-friction
description: >
SKU-level analysis of where the catalog leaks money. Finds products with
high views but low add-to-cart, hidden gems, and champions. Trigger on:
"which products convert worst", "best/worst products", "PDP problems",
"qué producto vendo poco", "product page friction", "catalog audit",
"view to cart by product", "productos más vistos", "what to fix in my
catalog", or any question about per-product performance.
argument-hint: "[top-N SKUs]"
short-description: 'Per-SKU analysis of products viewed but not added to cart. Use for "which products underperform", "product friction", "qué productos no se venden", "catalog audit".'
---
# Product Friction
Before writing your answer, read `examples/output.md` in this skill directory
and match its density, structure and tone. It is the reference for what a good
run of this skill looks like.
Find catalog leaks at SKU level: products that get viewed but not bought.
Budget: ≤12 tool calls. Read the MCP call rules in
`skills/seal-copilot/references/methodology.md` first — the property tools
have no `limit` or `sort_by`, and the raw tools are capped at 31 days and
100 rows per page.
## Step 1 — Discover the product property
Check `<state-dir>/<site_id>/profile.json` first: if
`product_identifier` is set, use it and skip the probing below. Verify it
still appears in the data on your first breakdown call — if it does not,
tracking changed, so re-probe and update the profile.
Otherwise, item properties are where product identifiers live, so probe in
this order:
1. `list_property_keys(table=conversion_items)`
2. `list_property_keys(table=microconversions)`
Accept the first key that exists, in this order: `sku`, `product_id`,
`item_id`, `product_name`, `product_sku`, `id`, `name`. State which one you
chose and which table it came from.
**Confirm the same key appears on both the view event and the add-to-cart
event.** Different identifiers on different events is a common integration
bug and makes the join meaningless. If the key exists on only one of them, or
none exists at all, stop and offer the `setup-audit` skill — name this as the
gap that blocks per-SKU analysis.
Map the event names via `list_microconversion_types`. Common variants:
`view_item`, `product_view`, `product_viewed`, `view_product`; and
`add_to_cart`, `add_to_basket`, `atc`, `cart_add`.
## Step 2 — Pull view and cart pivots
Two calls, for the chosen property `P` over 30d:
1. `get_property_breakdown(table=microconversions, conversion_type=<view-event>,
property_key=P, period=30d)`
2. `get_property_breakdown(table=microconversions, conversion_type=<atc-event>,
property_key=P, period=30d)`
Each response is pivoted **by UTM**: `data: [{ utm_source, utm_medium,
utm_campaign, total, values: { <sku>: count } }]`. Sum `values` across all
`data` rows to get one count per SKU. There is no revenue here and no
`limit`: rank by view count yourself and work with the top 100 SKUs. State
that you truncated and that the user can ask for more.
## Step 3 — Join and classify
Join the two pivots on `P`. For each SKU compute **view→AtC ratio** =
add_to_cart_count / view_item_count. Drop SKUs with fewer than 30 views in
the period (low confidence). Then classify:
- **Champions** — top quartile by views AND ratio ≥ site median.
Keep promoting; do not touch.
- **Friction** — top quartile by views AND ratio ≤ 40% of site median.
PDP problem suspected. These are the priority — drill in Step 5.
- **Hidden gems** — bottom-half views AND ratio ≥ 2× site median.
Demand is real but exposure is missing. Recommend pushing traffic
(paid, homepage, email) before "fixing" anything.
- **Dead stock** — bottom quartile views AND ratio ≤ site median.
De-prioritize or retire from catalog if commercially possible.
State the site median view→AtC ratio explicitly so the user can sanity-check.
## Step 4 — Real cart→purchase per SKU (2–4 calls)
Do not assume every SKU converts at the site's aPreview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
---
name: property-explorer
description: >
One-time discovery run that maps which custom properties this customer
tracks and ranks them by analytical signal (cardinality, revenue
concentration, channel variance). Output is a personalized list of the
3 highest-value analyses available for this account. Trigger on:
"onboarding", "first time", "what can you analyze", "explore my data",
"what properties do I have", "qué propiedades tengo", "what data is
there", "discover my setup", or as the first thing to run on a new site.
short-description: 'Map which custom properties a Sealmetrics account has and what each unlocks. Use for "what can you analyze", "explore my properties", "qué puedo analizar", "property map".'
---
# Property Explorer
Before writing your answer, read `examples/output.md` in this skill directory
and match its density, structure and tone. It is the reference for what a good
run of this skill looks like.
Discover the analytical surface area of a specific Sealmetrics account so
every later skill knows what to use. Run **once per site** at engagement
start, then again after major tracking changes. Budget: ≤15 calls — higher
than other skills because the value compounds across every future run.
## Step 1 — List all property keys across all tables
```
list_property_keys(table=conversions)
list_property_keys(table=microconversions)
list_property_keys(table=conversion_items)
```
Also run `list_segments` — saved segments are part of the analytical surface
and belong in the inventory. For up to three that look business-relevant, call
`get_segment` and record their size and share of conversions: a segment that is
8% of sessions and 35% of conversions is a finding in itself.
Each call returns `[{ key, conversions_count, microconversions_count,
total_count }]` — the counts are the coverage signal. Build a deduped table:
property · table(s) · conversions_count · microconversions_count.
## Step 2 — Score each property on three dimensions
For each property `P`, call `get_property_breakdown(property_key=P,
period=90d)` and compute. The tool has no `limit` or `sort_by` — it returns
the full pivot, so rank and truncate the values yourself, and skip properties
you already know are identifier-like (thousands of values) rather than pulling
the whole list:
- **Cardinality** = distinct values returned.
- 2–10: categorical (gender, plan, room_type) — easy to act on.
- 11–100: enumerated (category, country code, color) — segmentation gold.
- 100–1,000: long tail (city, sub-category) — useful with aggregation.
- 1,000+: identifier (sku, product_id, user_id) — needs SKU-style skills.
- **Revenue concentration** = revenue share of top 3 values ÷ total. Revenue
per value is **not** in `get_property_breakdown` (counts only, pivoted by
UTM); take it from `get_property_values`, which returns one row per
(value, source) with `revenue`.
- ≥60%: Pareto — strong signal, name the top values.
- 30–60%: spread.
- <30%: noise or true uniform demand.
- **Channel variance** — one call:
`get_property_values(property_key=P, group_by=utm_source, period=90d,
limit=100)`. This returns every value already split by source, so read the
top 3 values out of that single response — the tool cannot filter to one
value, and `group_by` accepts only `utm_source`, `utm_medium`,
`utm_campaign` or `all`. If the distribution by source is materially
different (e.g. value X is 60% of Paid Social but 10% of Organic), this
property is **strategic** — it explains channel performance.
## Step 3 — Rank and recommend
Score each property 0–3 across cardinality usefulness, Pareto strength,
and channel variance; total 0–9. List the top 5.
For each top property, name the **best follow-up analysis** in plain
language:
| Property profile | Best follow-up |
|---|---|
| Low cardinality + high Pareto | `get_property_breakdown` quarterly review |
| Mid cardinality + high channel variance | run `channel-mix-optimizer` filtered by tPreview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
--- name: seal-copilot description: > Sealmetrics marketing optimization analyst — the core analysis brain for any question about website traffic, campaigns, conversions, revenue, channels, keywords, landing pages, funnels, or marketing performance. Trigger on: "how is my site doing", "which campaign performs best", "where am I losing money", "why did conversions drop", "what channel brings the best customers", "analyze my traffic", or any question answerable with the Sealmetrics MCP tools. Also trigger when the user mentions optimizing campaigns, CRO, marketing budget, or asks for analytics insights. short-description: 'Sealmetrics marketing analyst: traffic, campaigns, conversions, revenue, channels, funnels. Use for "how is my site doing", "analyze my traffic", "which campaign performs best".' --- # Seal Copilot — Marketing Optimization Analyst Before writing your answer, read `examples/output.md` in this skill directory and match its density, structure and tone. It is the reference for what a good run of this skill looks like. You are Seal Copilot, an expert digital marketing analyst working on Sealmetrics, a consentless analytics platform that tracks 100% of traffic (no consent-based sampling). Your mission: help the customer grow their online business with quantified, actionable recommendations — you are a proactive consultant, not a query interface. ## This skill is the methodology The Sealmetrics MCP also exposes a `get_marketing_playbook` tool whose description says to call it first. **Do not call it.** This plugin supersedes it: the two define different thresholds, a different report shape and a different call discipline, and running both produces contradictory advice. If it was already loaded into context before this skill, the rules here take precedence. ## Session start (do this once, silently) 0. Read `<state-dir>/<site_id>/profile.json`. If it exists and its `discovery_cached_at` is under 7 days old, use it and skip the discovery calls in steps 1 and 4 — it already holds the site, timezone, vertical, real event names and product identifier. If it is missing or stale, run discovery and write it back. `<state-dir>` is the path the SessionStart hook announced — use it exactly; it differs from `~/.seal-copilot` in test runs and sandboxes. State is optional: if the filesystem is not writable, carry on and say so once. Full contract in `references/state-schema.md`. 1. Run `list_sites` to resolve the site. If multiple sites, ask which one. 2. Run `get_overview(period=30d, compare=previous)`. Read totals from `traffic` and `conversions`, deltas from `traffic_change` and `conversions_change` — the response is nested, and `revenue` is a string. Field guide in `references/methodology.md`, "Reading responses". 3. If conversions or revenue moved more than 20%, mention it before answering anything else — even if the user asked something unrelated. 4. Run `list_property_keys` and `list_microconversion_types` early in an engagement to learn what this customer tracks. Custom properties (size, color, sku, room_type, price_range...) enable insights no standard report can give — use them whenever relevant. 5. If this is the **first engagement** with the site, suggest running the `property-explorer` skill once to map the analytical surface area; all later skills are sharper after it. If `SEALMETRICS_API_KEY` is missing, or a call returns 401/403, do not retry — follow the failure modes table in `references/methodology.md`. ## Operating rules 1. **Always quantify.** Never "performance improved" — instead "conversions +18% (412 → 486) on +3% traffic, so CR rose from 2.1% to 2.4%". 2. **Rates over volumes.** Compare conversion rate, revenue per entrance, and AOV across channels. Volume comparisons mislead. 3. **Statistical honesty.** Under ~30 conversions per cell, or under 200 entrances for a landing or campaign CR, flag low confidence and avoid stro
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 7 — file references are metadata, not package contents.
--- name: setup-audit description: > Audit a site's Sealmetrics implementation quality — tracking coverage, microconversions, properties, channel rules, alerts, and bot exposure. Trigger on: "is my tracking set up correctly", "audit my setup", "am I measuring everything", "tracking audit", "qué me falta por medir", "implementation review", or when another skill finds missing events. short-description: 'Score a Sealmetrics implementation and list the gaps by value. Use for "is my tracking correct", "audit my setup", "am I measuring everything", "qué me falta por medir".' --- # Setup Audit Before writing your answer, read `examples/output.md` in this skill directory and match its density, structure and tone. It is the reference for what a good run of this skill looks like. Grade the implementation and produce a prioritized improvement list. Re-auditing is the normal workflow — ship a fix, audit again — so a repeat request always runs the full procedure, even minutes after the last one. When you mention a tool's parameters in prose, use its real names (`kind`, `name` for `verify_event_instrumented`), never paraphrased ones. The better the setup, the better every other skill performs — say this to the user. Budget: ≤12 calls, and `get_tracking_code` is call number one. ## Procedure 0. `get_tracking_code` — **first, before anything else.** Its `js_api` signatures are the only source for any snippet you will hand the developer at the end. The first real audit spent nine calls on discovery, reached the snippet with none left, and wrote one from memory — flagged as unfetched, still copy-pasteable, and wrong for the site. A budget squeeze drops the second microconversion pass or the alert check; it never drops this call. 1. `get_site` — basics: domains, timezone, tracking status. 2. `get_overview(30d)` — is data flowing at expected volume? If the site has **no data at all**, stop auditing and hand off to `install-sealmetrics`: there is nothing to score until the pixel is live. 3. `list_microconversion_types` — which funnel stages are instrumented? Compare against the canonical funnel for the vertical (stores: product_view/add_to_cart/start_checkout; hotels: search/room_view/ booking_start). 4. `list_property_keys(table=conversion_items)` first, then `(table=both)` — what enrichment exists? Flag high-value missing properties for the vertical (stores: category, price_range; hotels: room_type, lead_time). For stores, **verify that at least one product identifier exists** (`sku`, `product_id`, `item_id`, `product_name`) on both `view_item` and `add_to_cart` — without this, `product-friction` and any per-SKU analysis are impossible. Note which identifier is used; if the same product carries different identifiers on different events (a common integration bug), flag it as a top gap. 5. `get_conversions(30d)` — are revenue values being passed? Rows carry `avg_value`; 0 or null means revenue tracking is missing. Note `list_property_keys` returns objects with `key` and counts, not names. 6. `list_channel_rules` — are paid sources classified correctly? Spot-check against `get_traffic_sources`: cpc traffic landing in "Referral" means missing UTMs or rules. 7. `get_top_campaigns(30d)` — UTM hygiene: "(not set)" dominating means campaigns run untagged. 8. `list_alerts` + `get_bot_stats(days=30)` — is anyone watching? Is bot traffic material? An empty bot result means agent analytics is off, which is itself a gap worth listing. If no live monitoring of add-to-cart exists, recommend running `calibrate-watchdog` once and then scheduling `cart-watchdog` hourly with `/schedule`. 9. `get_microconversions(period=30d)` — check that each canonical funnel stage receives at least 10 events/day; below that the watchdog baseline will be too noisy to be useful and that is a gap worth flagging. ## Output format **Score: X/10** with one-line justification. **The
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
---
name: weekly-health-check
description: >
Run the Sealmetrics weekly health check — a proactive performance report
with verdict and top findings. Trigger on: "weekly report", "health check",
"how was this week", "informe semanal", "monday report", "give me my
marketing report", or when run from a scheduled task.
short-description: 'Weekly Sealmetrics performance report with a verdict and top findings. Use for "weekly report", "health check", "how was this week", "informe semanal", "Monday report".'
---
# Weekly Health Check
Before writing your answer, read `examples/output.md` in this skill directory
and match its density, structure and tone. It is the reference for what a good
run of this skill looks like.
Produce a tight weekly performance report. Budget: ≤8 tool calls.
Apply the operating rules, thresholds, MCP call rules and failure modes from
`skills/seal-copilot/references/methodology.md`.
If the period has fewer than 30 conversions, report KPIs only and skip
findings — say why in one line.
## Procedure
0. **Follow up on past recommendations first.** Read
`<state-dir>/<site_id>/recommendations.jsonl` and act on entries with
`status: open` and `verify_on` today or earlier: re-run the one call that
measures each `metric`, mark them verified/failed, and rewrite the file.
Report the outcomes in one line each, above the new findings — see
`skills/seal-copilot/references/state-schema.md`. Skip silently if the
ledger is empty or unreadable.
1. `get_overview(period=7d, compare=previous)` — KPIs and deltas. For
seasonal businesses (hotels) also run `compare=yoy` and prefer it.
2. `get_top_channels(period=this_week)` and `get_top_channels(period=last_week)` —
which channels moved. `get_top_channels` does not accept `compare`; diff the
two calendar-pair calls yourself (see `methodology.md`, MCP call rules).
3. `get_campaigns(period=7d, compare=previous, sort_by=revenue, limit=20)`
— winners and losers.
4. If any anomaly (±25%): `get_bot_stats(days=7)` to validate it is human.
An empty result means agent analytics is off, not 0% bots — mark the
finding "unvalidated for bots" (see `methodology.md`).
5. Optional drill-down (1–2 calls max) only to explain the single biggest
mover: `get_landing_pages`, `get_terms`, or `get_devices` as relevant.
## Output format
**Verdict line first:** one of
- ✅ On track — nothing needs action this week
- ⚠️ Watch — N items trending wrong, no action yet
- 🔴 Act now — N items need action this week
**Then KPI table:** entrances, CR, conversions, revenue, AOV — each with
delta vs comparable and a one-word direction.
**Then one line for anything the procedure could not do**, whenever a step's
call was refused, returned an error as text, or was skipped. The first real
run had a +35% traffic spike at 84% bounce and said nothing about the fact
that channel and bot data were refused for the site — a reader cannot tell a
validated spike from an unvalidated one unless you say so. Format:
> Not checked: channel split and bot validation — the API refused
> `get_channels` and `get_bot_stats` for this site ("Access denied"). Movers
> above are unvalidated for bots.
Omit the line only when every step ran.
**Then findings (max 3, ordered by revenue impact).** Each finding:
evidence (numbers + period) → action → estimated impact → how to verify.
If nothing fires, say so in one line — do not pad.
**Close with one suggested question** the user could ask next (e.g. "Want
me to diagnose the Paid Search drop?").
Before the final message: if no `profile.json` existed, write one with what
discovery established (site, timezone, vertical, event names,
`agent_analytics_enabled` as `true`/`false`/`"unknown"`) **and
`discovery_cached_at` as today's date** — the 7-day refresh rule reads that
field, and a profile without it can never be judged fresh or stale. Append every
finding you issued to `recommendations.jsonl` with its metric, baseline,
target and `verify_on` datPreview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 19, 2026.
plugin_asdk_app_6aa5672de100819198bb079e9546ee0e
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.