Skip to main content
command CX Codex

analyze-sequences — Claude Code command: what it does, how to install

analyze-sequences reviews a running or finished email sequence and reports performance, deliverability and test results, with a prioritized action plan.

Apache-2.0 ★ 450 updated 2026-04-03

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/analyze-sequences.md
Open on GitHub

What analyze-sequences does

The command runs a report on an email sequence: it pulls metrics from the MAP and the CRM for the window you give, checks KPI attainment, and looks for drop-off points, inbox placement problems and signs of list fatigue. It handles sequences that are still live and ones already closed.

Scope comes from flags. --sequence names the program or its ID, --window takes 7d, 14d, 30d or a custom date range, --detail picks summary or full, --segment narrows to a persona, tier or region, and --compare_to sets a baseline sequence or control group. After that comes the experiment readout with confidence intervals and a prioritized plan: adjust cadence, refresh copy, escalate what broke.

You get a dashboard snapshot with KPIs split by touch, persona and mailbox provider, an alert summary for deliverability that points at deliverability-lead incident logs, and a memo on the experiments. Both the MAP and the CRM feed those numbers, so a gap in either system leaves holes in the readout. Work is partly handed to the experiment-analyst and deliverability-lead agents and the cadence-design skill.

What it helps with

  • Find the step where a sequence loses replies
  • Trace an engagement dip back to a mailbox provider
  • Close out a running test and decide what to roll out
  • Catch list fatigue before the numbers drop
  • Hand architects and ops a recap with backlog updates

Example prompts for the agent

  • Run /email-sequence-orchestration:analyze-sequences --sequence "Expansion Play" --window 14d --detail full and walk me through the whole readout.
  • Compare the onboarding sequence against control over the last 30 days: /email-sequence-orchestration:analyze-sequences --sequence "Onboarding" --window 30d --compare_to "Control" --detail summary.
  • Check deliverability and fatigue for the Enterprise segment: /email-sequence-orchestration:analyze-sequences --sequence "Expansion Play" --window 7d --segment "Enterprise" --detail summary.

How to install analyze-sequences

Manually: put the files in place

.claude/commands/analyze-sequences.md

Call it with /analyze-sequences. For all projects use ~/.claude/commands/

Questions about analyze-sequences

How do I install analyze-sequences in Claude Code?

Copy the command file to .claude/commands/analyze-sequences.md in your project. Claude picks it up there, and you call it as /email-sequence-orchestration:analyze-sequences.

What does analyze-sequences do?

It gathers sequence metrics from the MAP and CRM, checks deliverability and drop-off points, reads out experiments, and returns a prioritized list of actions.

What data does it need to work?

MAP and CRM metrics for the chosen window. Set the window, audience and baseline with --window, --segment and --compare_to.

Source text

analyze-sequences.md · Apache-2.0
---
name: analyze-sequences
description: Evaluates live or completed email sequences, highlighting performance, deliverability, and experiment results.
usage: /email-sequence-orchestration:analyze-sequences --sequence "Expansion Play" --window 14d --detail full
---

# Command: analyze-sequences

## Inputs
- **sequence** – program name or ID to analyze.
- **window** – time horizon (7d, 14d, 30d, custom date range).
- **detail** – summary | full to control verbosity.
- **segment** – optional audience filter (persona, tier, region).
- **compare_to** – optional baseline sequence or control group.

## Workflow
1. **Data Pull** – collect MAP + CRM metrics (deliverability, engagement, pipeline impact) within specified window.
2. **Health Diagnostics** – evaluate KPI attainment, drop-off points, inbox placement, and fatigue risk.
3. **Experiment Readout** – summarize running/closed tests with confidence intervals and recommended actions.
4. **Insights & Actions** – generate prioritized playbook (optimize cadence, refresh content, escalate issues).
5. **Handoff** – prepare recap doc plus suggested backlog updates for architect + ops teams.

## Outputs
- Performance dashboard snapshot with KPIs by touch, persona, mailbox provider.
- Deliverability + QA alert summary referencing `deliverability-lead` incident logs.
- Experiment insights memo (winners, next tests, rollout guidance).

## Agent/Skill Invocations
- `experiment-analyst` – interprets tests and recommends next experiments.
- `deliverability-lead` – correlates reputation signals with performance dips.
- `cadence-design` skill – flags pacing issues causing fatigue.

---

© gtmagents · Apache-2.0 · gtmagents/gtm-agents

Similar slash commands

All slash commands for Marketing and content →

From the same set224

The whole set →
signal-intel signal-intel is a Claude Code skill that combines account intent, product usage, and engagement signals to prioritize ABM actions. It supports account monitoring and signal-driven sales workflows. CX Codex +1 ★ 450repo stars run-deal-health-review run-deal-health-review writes an executive status memo for one manufacturing pursuit: risk register, forecast confidence and the action plan. CX Codex +1 ★ 450repo stars plan-channel-roadmap plan-channel-roadmap generates quarterly social channel roadmaps with concrete targets, content themes, and testing priorities. Useful when balancing paid budgets and cross-network deliverables. CX Codex +1 ★ 450repo stars analyze-enrollment-funnel analyze-enrollment-funnel audits the path from inquiry to enrollment, breaking results down by channel and other segments. Use it to spot drop-offs and plan enrollment experiments. CX Codex +1 ★ 450repo stars launch-coaching-program launch-coaching-program is a Claude Code command that plans and launches multi-week sales coaching cohorts. It schedules sessions, drafts communications, and tracks cohort outcome metrics. CX Codex +1 ★ 450repo stars launch-in-app-experiments launch-in-app-experiments is a Claude Code command that plans in-app tests for activation, engagement, monetization, or retention. CX Codex +1 ★ 450repo stars plan-merchandising-campaign plan-merchandising-campaign builds an omni-channel merchandising campaign plan with offers, creative, and a QA checklist. CX Codex +1 ★ 450repo stars monitor-retention monitor-retention generates cohort retention dashboards, risk signal summaries, and customer save plays directly in Claude Code. CX Codex +1 ★ 450repo stars

Project sponsors

Companies that keep this analytics open