From agentkits-marketing
Guides a weekly marketing review cycle — collects scope, week period, focus areas, and output preferences via interactive questions to generate a structured review and planning document.
How this command is triggered — by the user, by Claude, or both
Slash command
/agentkits-marketing:weeklyops/The summary Claude sees in its command listing — used to decide when to auto-load this command
## Prerequisites Before running this command, ensure you have: - [ ] Week to review identified - [ ] Access to campaign data - [ ] MCP configured: `google-analytics`, `hubspot` (optional) ## Context Loading Load these files first: 1. `./README.md` - Product context 2. `./docs/ops/weekly/` - Previous weekly reviews 3. `./plans/` - Active campaign plans --- ## Language & Quality Standards **CRITICAL**: Respond in the same language the user is using. If Vietnamese, respond in Vietnamese. If Spanish, respond in Spanish. **Standards**: Token efficiency, sacrifice grammar for concision, li...
Before running this command, ensure you have:
google-analytics, hubspot (optional)Load these files first:
./README.md - Product context./docs/ops/weekly/ - Previous weekly reviews./plans/ - Active campaign plansCRITICAL: Respond in the same language the user is using. If Vietnamese, respond in Vietnamese. If Spanish, respond in Spanish.
Standards: Token efficiency, sacrifice grammar for concision, list unresolved questions at end.
Skills: Activate marketing-fundamentals, analytics-attribution, sales-workflow.md, crm-workflow.md skills.
Components: Reference ./.claude/components/interactive-questions.md and ./.claude/components/date-helpers.md
Execute BEFORE asking any questions:
# Get current date info
CURRENT_DATE=$(date +%Y-%m-%d)
CURRENT_WEEK=$(date +%V)
CURRENT_YEAR=$(date +%Y)
# Week boundaries
WEEK_START=$(date -v-$(($(date +%u)-1))d +%Y-%m-%d 2>/dev/null || date -d "last monday" +%Y-%m-%d)
WEEK_END=$(date -v-$(($(date +%u)-1))d -v+6d +%Y-%m-%d 2>/dev/null || date -d "next sunday" +%Y-%m-%d)
# Previous weeks
PREV_WEEK_START=$(date -v-7d -v-$(($(date +%u)-1))d +%Y-%m-%d 2>/dev/null || date -d "last monday -7 days" +%Y-%m-%d)
PREV_WEEK_END=$(date -v-7d -v-$(($(date +%u)-1))d -v+6d +%Y-%m-%d 2>/dev/null || date -d "last sunday" +%Y-%m-%d)
echo "Current Week: W$CURRENT_WEEK ($WEEK_START to $WEEK_END)"
Question: "What level of weekly review do you need?" Header: "Scope" MultiSelect: false
Options:
Question: "Which week are you reviewing?" Header: "Week" MultiSelect: false
Options (generated from Step 0):
Question: "What areas should we focus on?" Header: "Focus" MultiSelect: true
Options:
Question: "What format do you prefer?" Header: "Format" MultiSelect: false
Options:
Display summary:
## Weekly Review Configuration
| Parameter | Value |
|-----------|-------|
| Week | W[week] ([dates]) |
| Scope | [Basic/Recommended/Complete] |
| Focus Areas | [selected areas] |
| Format | [selected format] |
Question: "Proceed with weekly review?" Header: "Confirm" MultiSelect: false
Options:
CRITICAL: Follow ./workflows/data-reliability-rules.md strictly.
Use MCP for metrics; if unavailable show "⚠️ NOT AVAILABLE":
google-analytics - Traffic, conversionshubspot - Leads, CRM datameta-ads - Ad performancetwitter, tiktok - Social metricsMetrics Compilation
Progress Tracking
Content Planning
Funnel Analysis
| Task | Agent | Trigger |
|---|---|---|
| Metrics compilation | researcher | Weekly review |
| Progress tracking | project-manager | Status update |
| Content planning | planner | Next week prep |
| Funnel analysis | lead-qualifier | Conversion review |
# Weekly Review: W[X] ([Date Range])
## Key Metrics vs Targets
| Metric | Actual | Target | Status |
|--------|--------|--------|--------|
| Traffic | X | X | 🟢/🟡/🔴 |
| Leads | X | X | 🟢/🟡/🔴 |
## Top 3 Wins
1. [Win with data]
## Next Week Priorities
1. [Priority 1]
2. [Priority 2]
[Include Basic + Performance Metrics + Campaign Status + Content Review + Next Week Planning]
[Include all + Content Calendar + Resource Needs + Detailed Analytics + WoW comparison]
Before delivering weekly review:
Save review to: ./docs/ops/weekly/W[XX]-[YYYY].md
After weekly review, consider:
/ops:daily - Daily task management/report:weekly - Client-ready report/campaign:calendar - Content calendar updatenpx claudepluginhub aitytech/agentkits-marketing --plugin agentkits-marketing/weekly-reviewOrchestrates full weekly product review: analytics brief, experiment readouts, opportunity discovery; produces shareable doc with headline, metrics, outcomes, priorities.
/marketing-statusGenerates status report across active marketing initiatives, aggregating campaigns, content, analytics, issues, and recommendations. Supports report types like daily/weekly and focus areas.
/weeklyGenerates weekly pipeline health digest across all active deals, saves full report as Markdown file. Also supports posting condensed summary to Slack.