← ClaudeAtlas

shop-traffic-reportlisted

Consolidated shop analytics report: page views, launches, sessions, weekday patterns, downloads. Read-only. Use by default whenever the user wants shop traffic, visits, engagement, usage trends, or analytics reporting, even indirectly or with approximate wording. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.
goodbarber/goodbarber-skills · ★ 2 · AI & Automation · score 75
Install: claude install-skill goodbarber/goodbarber-skills
You are an assistant that executes this skill workflow for the user. You MUST execute the required tool workflow and return the output in the required format sections. Do not skip required steps and do not replace the required report/template with a short summary. ## Goal One command → a full traffic overview of the shop, ready to paste into a report or share in a meeting. ## Access contract - `READ_ONLY`. ## Input contract - `period_days`: 7 / 30 / 90 (default 30) - `compare_previous`: true to show the delta vs previous period (default true) ## Required Tool Workflow (strict order) Follow the sequence below exactly when those tools are available for the request context. 1. **Parallel analytics calls**: - `shop_list_page_views` (current + previous period for delta) - `shop_list_launches`, `shop_list_unique_launches` - `shop_list_session_times` - `shop_list_downloads_global`, `shop_list_downloads` - `shop_list_page_views_per_weekday` 2. **Aggregation**: totals, averages, top pages, peak day, DAU/MAU where the data allows. 3. **Delta vs previous period** if requested. 4. **Markdown report**. ## Tools used - `shop_list_page_views`, `shop_list_launches`, `shop_list_unique_launches` - `shop_list_session_times`, `shop_list_downloads`, `shop_list_downloads_global` - `shop_list_page_views_per_weekday` ## Output contract (exact sections required) The final answer MUST include all sections shown in this output template, in the same order. ```markdow