outreach-sequence-builder
Takes a buying signal and generates a personalized multi-channel outreach sequence across email, LinkedIn, and phone. Outputs 4-6 ready-to-send touchpoints over 10-14 days. Optionally drafts email touchpoints via Composio Gmail. Use when asked to write an outreach sequence, build a sales cadence, create a follow-up sequence, personalize outreach for a signal, or generate cold outreach messages. Trigger when a user says "build an outreach sequence for", "write a sales cadence for", "create outreach based on this signal", "they just raised a round write me a sequence", or "generate personalized
npx skills add Varnan-Tech/opendirectory --skill outreach-sequence-builder --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Outreach Sequence Builder Take a buying signal. Generate a personalized multi-channel outreach sequence. Output ready-to-send messages across email, LinkedIn, and phone. --- **Critical rule:** Every message must be filled in completely from the context you load. Only `{{first_name}}` is allowed as a variable. No `[Company Name]` brackets, no `[INSERT PAIN POINT]` placeholders. If you do not have the information to fill something in, ask before writing. Never send a message with an unfilled placeholder. --- ## Step 1: Setup Check Confirm required env vars: ```bash echo "GEMINI_API_KEY: ${GEMINI_API_KEY:+set}" echo "COMPOSIO_API_KEY: ${COMPOSIO_API_KEY:-not set, Gmail drafting will be skipped}" ``` **If GEMINI_API_KEY is missing:** Stop. Tell the user: "GEMINI_API_KEY is required. Get it at aistudio.google.com. Add it to your .env file." **If COMPOSIO_API_KEY is missing:** Continue. Sequences will be output as formatted text for copy-paste. Gmail draft creation is skipped. --- ## Step 2: Load Context Check for an existing ICP file and account files: ```bash ls docs/icp.md 2>/dev/null && echo "icp found" || echo "icp missing" ls docs/accounts/ 2>/dev/null && echo "accounts found" ||
- Step 1: Setup Check
- Step 2: Load Context
- Step 3: Identify the Signal
- Step 4: Develop the Angle
- Step 5: Plan the Channel Sequence
- Step 6: Generate the Sequence
- Step 7: Map Objections
- Step 8: Self-QA
- Step 9: Output and Save
echo "GEMINI_API_KEY: ${GEMINI_API_KEY:+set}"
echo "COMPOSIO_API_KEY: ${COMPOSIO_API_KEY:-not set, Gmail drafting will be skipped}"
ls docs/icp.md 2>/dev/null && echo "icp found" || echo "icp missing"
ls docs/accounts/ 2>/dev/null && echo "accounts found" || echo "accounts missing"
cat > /tmp/outreach-sequence-request.json << 'ENDJSON'
curl -s -X POST \
mkdir -p docs/sequences
cat > docs/sequences/SIGNAL-TYPE.md << 'EOF'
echo "Sequence saved to docs/sequences/SIGNAL-TYPE.md"
The agent calls the GMAIL_CREATE_EMAIL_DRAFT Composio actionWhat does the outreach-sequence-builder skill do?
Takes a buying signal and generates a personalized multi-channel outreach sequence across email, LinkedIn, and phone. Outputs 4-6 ready-to-send touchpoints over 10-14 days. Optionally drafts email touchpoints via Composio Gmail. Use when asked to write an outreach sequence, build a sales cadence, create a follow-up sequence, personalize outreach for a signal, or generate cold outreach messages. Trigger when a user says "build an outreach sequence for", "write a sales cadence for", "create outreach based on this signal", "they just raised a round write me a sequence", or "generate personalized
How do I install it?
Run `npx skills add Varnan-Tech/opendirectory --skill outreach-sequence-builder --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Varnan-Tech/opendirectory, a repository with 571 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
