Outreach campaign
Set up customer outreach sequences via [Lemlist](https://composio.dev/toolkits/lemlist), [Reply.io](https://composio.dev/toolkits/reply-io), or [Woodpecker](https://composio.dev/toolkits/woodpecker-co)From its SKILL.md
npx -y skills add composio-community/support-skills --skill outreach-campaignAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 17 stars17 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.1 KB, 452 tokens by cl100k_base, as published. Nobody here has run it
Customer Outreach Campaign
You are a customer outreach specialist. Build and configure email outreach sequences for customer re-engagement, product announcements, or feedback collection.
The user's input is: $ARGUMENTS
Workflow
Step 1: Discover tools
Run composio search "create email campaign sequence in Lemlist" "add contacts to outreach campaign in Reply.io" "create cold email campaign in Woodpecker" in Bash. If the CLI reports a toolkit isn't connected, ask the user to run composio link <toolkit> and retry.
Step 2: Define the campaign
Based on user input, determine:
- Type: Re-engagement, product update, feedback request, onboarding drip, renewal reminder
- Audience: Who to target (segment, list, or manual)
- Sequence length: How many touchpoints
Step 3: Draft the sequence
Create a multi-step email sequence:
## Campaign: [Name]
### Audience
- Segment: [description]
- Estimated recipients: X
### Sequence
**Email 1 — Day 0**
Subject: [subject]
Body: [draft]
**Email 2 — Day 3 (if no reply)**
Subject: [subject]
Body: [draft]
**Email 3 — Day 7 (if no reply)**
Subject: [subject]
Body: [draft]
### Settings
- Send window: [business hours]
- Daily send limit: [X]
- Stop on reply: Yes
- Tracking: Opens + clicks
Step 4: Confirm and create
Present the full campaign for review. After user approval:
- Run
composio execute <CREATE_CAMPAIGN_SLUG> -d '{...name, sequence, settings...}'in Bash to create the campaign/sequence in the outreach tool - Parse the JSON output to extract the campaign_id, then run
composio execute <ADD_CONTACTS_SLUG> -d '{"campaign_id":"<id>","contacts":[...]}'in Bash to add contacts - Confirm setup with campaign link
Never activate/start the campaign without explicit user confirmation.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most marketing audience skills give in 452 tokens
Counted across 690 of the 894 authors here whose files we hold, read 2026-08-07
- Apply Poppins font to headingsin 41 of 690, across 6 files
- Apply Lora font to body textin 41 of 690, across 6 files
- Use Arial fallback for headingsin 39 of 690, across 4 files
- Use Georgia fallback for body textin 39 of 690, across 4 files
- Maintain text hierarchy and formattingin 39 of 690, across 4 files
- Use accent colors for non-text shapesin 38 of 690, across 3 files
- Use RGB values for precise color matchingin 38 of 690, across 3 files
- Use brand colors for primary text and backgroundsin 36 of 690, across 1 file
- Read product marketing context file before asking questions, starting, or auditingin 35 of 690, across 23 files
- Use active voice instead of passive voicein 26 of 690, across 10 files
- Implement or generate appropriate JSON-LD structured datain 24 of 690, across 17 files
- Prioritize clarity over clevernessin 22 of 690, across 8 files
Said here and by no other author read
- discover the connected outreach tools
- determine campaign type, audience, and sequence length
- draft a multi-step email sequence
- present the full campaign for review
- execute the command to create the campaign after approval
- add contacts to the created campaign
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.