2.13.0-beta.20). Features may change before the next stable release.Switch to stable →Skills
Route a marketing report with ak:analyze
Select a supported analysis type or reporting period, gather approved data, and produce a qualified marketing report.
Use ak:analyze as a broad Marketing report router. It accepts one of six
analysis types—traffic, campaigns, conversions, funnel, content, or
engagement—or the report subcommand with daily, weekly, monthly, or
quarterly. It gathers data that is actually available, applies the Marketing
analytics framework, and reports findings, gaps, and recommendations.
Choose ak:analyze for routing, not an assumed connector
Use ak:analyze when
- You know the supported analysis type or periodic-report cadence you need.
- Approved project data or authorized provider access is available.
- You want a cross-channel overview before choosing a deeper investigation.
Choose another workflow when
- You need a custom KPI, attribution, cohort, or experiment method. Use
ak:analyticsdirectly. - You need to add tracking, change an account, or operate a campaign. This Skill produces analysis; it does not grant mutation, publishing, or spend authority.
- Your request does not map to a listed type. Define the question and measures first rather than relying on the generic name.
Prepare the reporting contract
Provide the exact type or period, date range, timezone, currency, goals, comparison period, source list, and metric definitions. The workflow can use project data and may fetch GA4 or Search Console evidence when a compatible MCP, credentials, permissions, and current provider behavior exist. Provider names in the Skill are not proof that a connector is configured.
Minimize personal data. Account, property, campaign, page, query, email, CRM, and conversion identifiers can expose people or business-sensitive activity. Use aggregate exports, redact secrets and direct identifiers, and record sampling, consent, retention, and missing-source limits.
| Runtime | Invocation | Availability boundary |
|---|---|---|
| Claude Code | /ak:analyze ... | Uses the packaged Skill through native or explicit plugin delivery. Data access remains session-specific. |
| Cursor | /ak:analyze ... | Slash invocation is user-verified; connector and automation parity are not implied. |
| Codex | $ak:analyze ... | Uses native Skill discovery; available tools and Marketing Hooks can differ. |
Run the Skill
/ak:analyze campaigns "Use only the approved channel exports for 2026-07-01 through 2026-07-31. Compare with goals, identify missing fields, and make no account changes"/ak:analyze campaigns "Use only the approved channel exports for 2026-07-01 through 2026-07-31. Compare with goals, identify missing fields, and make no account changes"$ak:analyze campaigns "Use only the approved channel exports for 2026-07-01 through 2026-07-31. Compare with goals, identify missing fields, and make no account changes"For a periodic report, put report first so the Skill can route the remaining
argument:
/ak:analyze report weeklyUnderstand the stages
- Parse the analysis type or
reportperiod. - Inventory available sources and distinguish fetched, supplied, and missing data.
- Apply type-specific measures: traffic sources and trends; campaign cost, conversion, and ROI; funnel stages and drop-offs; or content and engagement.
- Compare with approved goals and a genuinely comparable prior period.
- Separate observations, anomalies, assumptions, and recommendations in the report.
Keep decisions and mutations with you
A report is guidance, not operating authority
Do not let a recommendation automatically change tracking, budgets, campaigns, content, accounts, or live pages. Each external mutation needs a separate scope, data review, provider permission, cost check, and approval.
Verify output and evidence
Standard analysis writes reports/analytics/{date}-{type}.md. The report
route writes reports/periodic/{date}-{period}.md. Expect an executive summary,
key metrics, relevant channel or funnel detail, goal progress, source and
period comparison, findings, limitations, and recommendations. Verify formulas,
totals, attribution windows, identifiers, and citations against the originals.
Troubleshoot and know the limits
| Symptom | Safe next step |
|---|---|
| Type is ambiguous | Select exactly traffic, campaigns, conversions, funnel, content, or engagement. |
| Periodic report does not route | Use report daily, report weekly, report monthly, or report quarterly. |
| A named provider is unavailable | Use an approved export or configure access separately; do not invent data. |
| Metrics conflict | Reconcile definitions, periods, timezone, currency, and deduplication before interpreting. |
| Runtime cannot find the Skill | Follow Runtime cannot find a Skill or Agent. |
The Skill does not guarantee source coverage, connector availability, attribution accuracy, statistical significance, revenue, or performance gains. See Marketing Kit and Runtime adapters.
Measure marketing performance with ak:analytics
Turn approved marketing data into a KPI, attribution, experiment, funnel, or recurring performance report without treating estimates as facts.
Operate the local dashboard with ak:dashboard
Start, build, check, or stop the current local Marketing Dashboard while respecting its process, storage, and network boundaries.