whatsapp-outreach-run
Automatic WhatsApp outreach agent run
What this skill does
# WhatsApp Outreach Agent - Run Skill
> Run the agent for mass WhatsApp message sending
## When to use
- "run WhatsApp outreach for X"
- "send WhatsApp messages for campaign Y"
- "build and run WhatsApp campaign"
## Before running
1. **Check WhatsApp session:**
```bash
ls $SALES_PATH/whatsapp/baileys_session/
```
If empty -> authenticate first:
```bash
cd $SALES_PATH/whatsapp
node index.js
# Scan QR code
```
2. **Check setup:**
```bash
cd $AGENTS_PATH/whatsapp-outreach
python3 test_setup.py
```
## How to run
### Step 1: Create or select a campaign
If no campaign exists -- create a config:
```yaml
# $AGENTS_PATH/campaigns/my-campaign.yaml
campaign_name: "Campaign Name"
filters:
company_id: ["comp-XXX"] # Optional
product_id: ["prod-XXX"] # Optional
stage: ["new", "qualified"] # Optional
preferred_channel: "whatsapp" # Optional
message_template: |
Hi, {first_name}!
This is Ivan from WeLabelData.
Your message here...
variables:
custom_var: "value"
```
### Step 2: Dry-run (mandatory!)
```bash
cd $AGENTS_PATH/whatsapp-outreach
python3 whatsapp_outreach_agent.py \
--dry-run \
--campaign campaigns/my-campaign.yaml
```
Check:
- Number of recipients
- Message personalization
- Filters are working correctly
### Step 3: Test with one recipient
```bash
python3 whatsapp_outreach_agent.py \
--test-recipient p-XXX
```
Check:
- Message was sent
- Activity was logged
- Git branch was created
### Step 4: Small batch (3 people)
```bash
python3 whatsapp_outreach_agent.py \
--limit 3 \
--campaign campaigns/my-campaign.yaml
```
Check:
- 60 second delay is working
- All activities were logged
- Git branch is correct
### Step 5: Full run
```bash
python3 whatsapp_outreach_agent.py \
--campaign campaigns/my-campaign.yaml
```
- Agent shows preview (first 3 messages)
- Agent asks for confirmation: `[y/N]`
- If `y` -> starts sending
- Progress: `[X/Y] Name → +phone... OK/FAIL`
### Step 6: Review and merge
```bash
cd $PROJECT_ROOT
# Check changes
git diff main
# If OK -> merge
git checkout main
git merge whatsapp-outreach-YYYY-MM-DD-HHMM
# If NOT OK -> delete branch
git branch -D whatsapp-outreach-YYYY-MM-DD-HHMM
```
## Flags
| Flag | Description |
|------|-------------|
| `--campaign FILE` | Path to campaign config (YAML) |
| `--dry-run` | Test run (no sending) |
| `--auto-approve` | Skip human approval (use with caution!) |
| `--test-recipient p-XXX` | Send to one person only |
| `--limit N` | Limit to N recipients |
## Environment Variables
```bash
# Delay between messages (seconds)
export WHATSAPP_DELAY_SECONDS=60
# Daily message limit
export WHATSAPP_DAILY_LIMIT=20
# Lookback for idempotency (days)
export IDEMPOTENCY_LOOKBACK_DAYS=7
```
## Output
### Logs
`$AGENTS_PATH/logs/whatsapp_outreach_YYYY-MM-DD_HH-MM.md`
### Git branch
`whatsapp-outreach-YYYY-MM-DD-HHMM`
### CRM changes
- `sales/crm/activities.csv` — added activities
- `sales/crm/relationships/leads.csv` — updated last_contact_date
- `sales/crm/contacts/people.csv` — added notes (if failed)
## Troubleshooting
### "WhatsApp session expired"
```bash
cd $SALES_PATH/whatsapp
node index.js
# Scan QR code
```
### "FloodWait error"
- Increase `WHATSAPP_DELAY_SECONDS`
- Decrease `WHATSAPP_DAILY_LIMIT`
- Wait 24 hours
### "No recipients found"
- Check filters in campaign config
- Check CRM data (people.csv, leads.csv)
- Check phone numbers in people.csv
### Git branch not created
- Check if there were successful sends
- Check `git status` in $PROJECT_ROOT
- Possibly all sends failed
## Examples
### Client D training reminder
```bash
python3 whatsapp_outreach_agent.py \
--campaign campaigns/clientd-training-reminder.yaml
```
### Quick test
```bash
python3 whatsapp_outreach_agent.py \
--dry-run \
--limit 1 \
--campaign campaigns/example-whatsapp.yaml
```
## Related files
- **Spec:** `$AGENTS_PATH/specs/whatsapp-outreach.spec.md`
- **README:** `$AGENTS_PATH/whatsapp-outreach/README.md`
- **Implementation:** `$AGENTS_PATH/whatsapp-outreach/IMPLEMENTATION.md`
## Important
- **Always --dry-run first**
- **Never --auto-approve without testing**
- **Max 20 messages per day** (WhatsApp may ban)
- **Human approval required** (per owner decision)
- **Review git branch before merge**
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.