Quick Ref / Command

Marketing Kit

/ak:analyze

Analyze Reports

Generate focused analytics and performance reports for traffic, campaigns, conversions, funnels, content, and engagement using real data where available.

01

Parse type

02

Gather data

03

Fallback locally

04

Run type lens

Rule 01

Start from the requested analysis type so the report has a sharp lens.

Rule 02

Use real GA4 or Search Console metrics when available; otherwise analyze existing project data honestly.

Rule 03

Benchmark before recommending so numbers are interpreted in context.

Rule 04

The output is a useful report, not a generic metrics dump.

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Parse type Read the requested analysis type from arguments: traffic, campaigns, conversions, funnel, content, engagement, or report with daily, weekly, monthly, or quarterly.
  2. 2 Gather data Use the analytics-analyst role, activate analytics frameworks, and pull GA4 or Search Console metrics when integrations are available.
02

Work

Agent / skill execution

  1. 3 Fallback locally When external MCP data is not available, analyze available project data, campaign exports, documents, or existing reports instead of fabricating metrics.
  2. 4 Run type lens For traffic inspect sources, pages, and trends; for campaigns inspect ROI, conversions, and cost; for conversions and funnel inspect stages and drop-offs.
03

Verify

Gate, review, validation

  1. 5 Analyze content For content and engagement reports, evaluate shares, time on page, audience interaction, and performance against goals.
  2. 6 Benchmark goals Compare metrics to campaign goals, historical baselines, channel expectations, and funnel targets.
04

Close

Report, handoff, artifact

  1. 7 Generate insights Identify trends, patterns, anomalies, bottlenecks, and likely drivers before recommending actions.
  2. 8 Write report Save standard analyses to reports/analytics/{date}-{type}.md and report-route output to reports/periodic/{date}-{period}.md.

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Traffic report Recommended
/ak:analyze traffic
Use when:
You need sources, pages, and trend analysis.
Expected:
A traffic report grounded in available metrics with trends and recommendations.
Campaign overview
/ak:analyze campaigns
Use when:
Campaign ROI, conversions, and costs need review.
Expected:
A campaign-performance overview with benchmarks, anomalies, and next actions.
Periodic report
/ak:analyze report weekly
Use when:
You need a documented daily, weekly, monthly, or quarterly report route.
Expected:
The report reference writes reports/periodic/{date}-{period}.md with available metrics, gaps, and recommendations.

Handled Scope

  • Traffic analysis
  • Campaign performance
  • Conversion funnels
  • Content performance
  • Engagement metrics
  • Periodic reports

Artifacts Produced

Analytics report

Pattern

reports/analytics/{date}-{type}.md and reports/periodic/{date}-{period}.md

The skill writes type-specific analytics reports and periodic report-route outputs with insights and recommendations.

Related skills

Next