{"id":26500,"plugin_id":"plugin_asdk_app_6abd741d819481918aba420a975bc576","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-05T06:02:34.557Z","digest":"12f35c7de89ed16602ee227ec0b095ed3a6e4f3e6f9e236e94d7630957cfc66c","against":null,"payload":{"description":"Run a weekly review of an Attri workspace — what moved in traffic and search, which findings are new or resolved, what to do next — and plan the chosen actions. Use on a schedule or when a person asks for a weekly summary.","included_files":[],"name":"attri-weekly-review","skill_md_contents":"---\nname: attri-weekly-review\ndescription: Run a weekly review of an Attri workspace — what moved in traffic and search, which findings are new or resolved, what to do next — and plan the chosen actions. Use on a schedule or when a person asks for a weekly summary.\n---\n\n# Attri weekly review\n\nA routine, not a report. The output is three decisions the person can take this week, with the numbers behind them, and the findings marked as planned when they agree.\n\n## Steps\n\n1. **Scope.** `list_workspaces`; run the review per workspace if several are enabled.\n2. **What moved.** `get_site_overview` for the last 7 days versus the prior 7 (set `date_from` and `date_to`). Note visitors, sessions and conversions with the change, and the channel mix. Then `get_search_overview` for the same window: clicks, impressions, position, and Attri's search sessions and conversions.\n3. **Why it moved.** `list_search_queries` sorted by clicks with the prior period for the biggest gains and losses; `list_top_pages` and `list_sources` for the site side. Name at most three movers each way.\n4. **Findings.** `list_findings` with status `open`; call out `new_this_week`. For anything already `planned`, ask whether it shipped; if it did, it should be marked `done`.\n5. **Decide.** Pick three findings in score order, skipping `rising`. For each, `get_finding` and turn the evidence into one sentence and one action, following the attri-search-analyst skill for kind-specific advice.\n6. **Plan.** If the person agrees and the connection has `findings:write`, `set_finding_status` to `planned` with a note like \"weekly review 2026-09-29: rewrite title, target 'utm builder'\". Otherwise list them as proposed.\n\n## Output\n\nKeep it to one screen:\n\n- **Week in numbers:** visitors, sessions, conversions, search clicks, search impressions, with the change against the prior week.\n- **Moved:** up to three gains and three losses, each with the query or page and the number.\n- **Do next:** three findings, each with title, the number that justifies it, the action, the measure.\n- **Watching:** rising queries, one line.\n- **Housekeeping:** planned findings awaiting a done, anything resolved on its own.\n\n## Rules\n\n- Same rules as the analyst skill: no invented findings, real numbers, say the range.\n- If Search Console is not connected, do the site half and say the search half is unavailable.\n- Do not plan more than three findings in one review; the loop only works if the list stays short.\n- Never mark anything `done` on your own; only the person knows what shipped.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}