intelligence-report
Generate marketing intelligence briefings from compound intelligence across agents — surfaces learnings, cross-agent patterns, confidence distribution, and playbooks. Use when reviewing accumulated marketing learnings, preparing for quarterly planning, onboarding team members, or identifying knowledge gaps.
What this skill does
# /digital-marketing-pro:intelligence-report
## Purpose
Generate a comprehensive intelligence briefing from the brand's compound intelligence system. This command surfaces the accumulated knowledge that agents have built over time — total learnings captured, confidence distribution across insights, top patterns identified across agents and channels, actionable playbooks generated from proven strategies, and intelligence base health metrics showing where the knowledge is strong and where gaps exist. The intelligence report turns raw accumulated data into strategic advantage by synthesizing cross-agent patterns that no single agent would surface alone. Use it for quarterly planning, strategy reviews, onboarding new team members to a brand's marketing intelligence, or identifying which areas need more experimentation and data collection to strengthen decision-making confidence.
## Input Required
The user must provide (or will be prompted for):
- **Focus area (optional)**: A specific channel (email, paid search, social), audience segment, campaign objective (awareness, conversion, retention), or strategic theme to deep-dive. If provided, the report prioritizes patterns, playbooks, and recommendations for that focus area while still including the full intelligence base overview. If omitted, the report covers all dimensions equally
- **Playbook request (optional)**: A specific scenario to generate an actionable playbook for — e.g., "Q2 product launch on paid social", "re-engagement campaign for churned subscribers", or "brand awareness push in new market". The intelligence system synthesizes relevant learnings into a step-by-step playbook grounded in proven patterns from this brand's data
## Process
1. **Load brand context**: Read `~/.claude-marketing/brands/_active-brand.json` for the active slug, then load `~/.claude-marketing/brands/{slug}/profile.json`. Apply brand positioning, channel mix, campaign history, and strategic objectives. Also check for guidelines at `~/.claude-marketing/brands/{slug}/guidelines/_manifest.json` — if present, load restrictions. Check for agency SOPs at `~/.claude-marketing/sops/`. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults.
2. **Get intelligence stats**: Run `intelligence-graph.py get-stats --brand {slug}` to retrieve the intelligence base overview — total learnings captured, learnings by agent and channel, confidence score distribution (high, moderate, low), date range of intelligence, and most recent learning timestamp.
3. **Get cross-agent patterns**: Run `intelligence-graph.py get-patterns --brand {slug}` for key dimensions — channel performance patterns, audience response patterns, timing and seasonality patterns, creative and messaging patterns, and budget efficiency patterns. If a focus area was specified, weight pattern retrieval toward that dimension. Identify patterns that span multiple agents (e.g., a timing pattern confirmed by both the email specialist and social media manager).
4. **Generate playbooks**: If a playbook request was provided, run `intelligence-graph.py export-playbook --brand {slug} --scenario {scenario}` to synthesize relevant learnings into a step-by-step actionable playbook. Each playbook step references the specific learnings and confidence levels that support it. If no playbook was requested, generate a summary of the top three available playbooks based on the strongest pattern clusters.
5. **Identify stale learnings**: Flag learnings that have not been revalidated within their recommended revalidation window — typically 90 days for tactical insights, 180 days for strategic patterns. Stale learnings may still be accurate but their confidence should be discounted. Prioritize revalidation recommendations by impact — stale high-impact learnings get flagged first.
6. **Calculate compound intelligence score**: Compute an overall intelligence maturity score based on total learnings volume, average confidence level, cross-agent pattern density, recency of intelligence, coverage across channels and audiences, and ratio of validated to unvalidated learnings. Score on a 0-100 scale with tier labels — Emerging (0-25), Developing (26-50), Established (51-75), Advanced (76-100).
## Output
A structured intelligence briefing containing:
- **Intelligence base health**: Total learnings captured, breakdown by agent and channel, average confidence score, confidence distribution (percentage at high, moderate, low), date range of intelligence coverage, most recent and oldest learning timestamps, and coverage gaps where channels or audiences have insufficient data
- **Top patterns by channel, audience, and objective**: The highest-confidence cross-agent patterns organized by dimension — what consistently works on each channel, which audiences respond to what approaches, and which objectives have proven playbooks versus which need more experimentation
- **Actionable playbooks**: Step-by-step playbooks for the requested scenario or the top three strongest available playbooks — each step grounded in specific learnings with confidence levels, expected outcomes based on historical patterns, and risk factors to monitor
- **Stale learnings needing revalidation**: Learnings past their revalidation window ranked by impact — with recommended revalidation methods (re-run the test, check latest analytics, update with new campaign data) and estimated effort for each
- **Compound intelligence score**: The 0-100 maturity score with tier label, breakdown by scoring component, trend versus previous assessment, and specific actions to improve the score — e.g., "Run email subject line tests to fill the email optimization gap" or "Validate Q3 social timing patterns with current data"
- **Recommendations for strengthening the intelligence base**: Prioritized list of experiments, analyses, and data collection activities that would most improve intelligence coverage, confidence, and actionability — the highest-ROI investments in marketing knowledge
## Agents Used
- **intelligence-curator** — Cross-agent pattern synthesis and identification of multi-source confirmed insights, playbook generation from proven pattern clusters with confidence-weighted step sequencing, intelligence base health assessment with coverage gap analysis, stale learning identification and revalidation prioritization, compound intelligence score calculation with component breakdown, and strategic recommendations for intelligence base improvement
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.