skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from…
Activate for: sequence, outreach sequence, cadence, multi-touch, email sequence, follow-up sequence, drip sequence, nurture sequence, prospecting sequence, sales cadence, outreach plan, touch plan, 6-touch, 8-touch, how many times should I follow up, follow-up schedule. NOT for:
Claude Code
$ npx -y skills add panaversity/agentfactory-business-plugins --skill sequence --agent claude-code
Codex
$ npx skills add panaversity/agentfactory-business-plugins --skill sequence -a codex -y
Cursor
$ npx skills add panaversity/agentfactory-business-plugins --skill sequence -a cursor -y
Gemini CLI
$ npx skills add panaversity/agentfactory-business-plugins --skill sequence -a gemini-cli -y
GitHub Copilot
$ npx skills add panaversity/agentfactory-business-plugins --skill sequence -a github-copilot -y
OpenCode
$ npx skills add panaversity/agentfactory-business-plugins --skill sequence -a opencode -y
Windsurf
$ npx skills add panaversity/agentfactory-business-plugins --skill sequence -a windsurf -y
name: sequence description: > Activate for: sequence, outreach sequence, cadence, multi-touch, email sequence, follow-up sequence, drip sequence, nurture sequence, prospecting sequence, sales cadence, outreach plan, touch plan, 6-touch, 8-touch, how many times should I follow up, follow-up schedule. NOT for: single outreach messages (use outreach), post-meeting follow-ups (use follow-up), sequence lifecycle management (use outreach-sequencing-agent), campaign planning (use campaign-planning).
Before building any sequence, apply these principles:
1. QUALITY OVER VOLUME: Each touch must add value or offer a new angle. Never send "Just checking in." Never repeat the same message. Each touch uses a DISTINCT hook, proof point, or angle not present in any previous touch. Plan the distribution of available hooks across touches before writing — do not front-load all proof points into Touch 1.
2. CHANNEL VARIETY: Mix LinkedIn and email. Different channels reach people at different moments. Phone for HOT leads after Touch 2.
3. VALUE ESCALATION: Early touches are about them. Later touches introduce social proof and specifics. Final touch is graceful exit. Reserve your strongest proof point (case study, customer result) for Touch 3-4, not Touch 1 — social proof converts better after rapport is established.
4. BRANCH ON REPLY: As soon as prospect responds, sequence STOPS. All subsequent communication is human-led, not automated.
5. TIMING: HOT leads -- faster cadence. WARM leads -- slower. Never contact more than once in 3 days on the same channel.
Touch 1 -- Day 1 | Primary channel (LinkedIn or Email) [Personalised first outreach -- see outreach skill]
Touch 2 -- Day 3 | Secondary channel (Email if T1 was LinkedIn; vice versa) [Same hook, different medium. Reference T1 briefly if appropriate. Add one new data point or angle. Repeat the one ask.]
Touch 3 -- Day 7 | Value add -- no ask [Send something genuinely useful: relevant case study, industry stat, short framework. No pitch. "Thought this might be relevant given what you're navigating at [Company]." Opens goodwill without pressure.]
Touch 4 -- Day 10 | Problem reframe -- ask [Share a specific insight about the problem -- not your product. 3 patterns you see in their sector. What your best customers say about the problem before they solved it. End with the ask again.]
Touch 5 -- Day 17 | Trigger check or new signal [If new signal has appeared (news, post, job ad): reference it. If not: "I've reached out a few times -- is this timing off, or not the right priority? Either way, I'm happy to hear it."]
Touch 6 -- Day 21 | Graceful close [Short. Respectful. Leave door open. "I've reached out several times without hearing back -- I'll assume the timing isn't right. If that changes, I'm here. [Name]." No ask. No guilt. Prospect remembers how you left.]
Touch 1 -- Day 1 | Email (lighter personalisation than HOT) Touch 2 -- Day 7 | LinkedIn -- value add Touch 3 -- Day 14 | Email -- problem insight, no pitch Touch 4 -- Day 28 | Email or LinkedIn -- soft check-in Touch 5 -- Day 35 | Graceful close
For prospects who went cold after initial engagement:
Touch 1 -- Day 1 | Reference last interaction specifically ["We spoke about X in [Month] -- I wanted to reconnect because [new signal or development that's changed since then]..."] Touch 2 -- Day 10 | New value: something relevant that has changed Touch 3 -- Day 21 | Graceful close or hand-off
OUTREACH SEQUENCE: [Prospect Name] / [Company]
---
Lead tier: [HOT / WARM / RE-ENGAGE] Sequence: [N] touches over [N] days Goal: [Discovery call / Demo / Re-engagement] Channels: [Mix -- e.g. LinkedIn x3 + Email x3]
TOUCH 1 -- Day [N] | [Channel] [Full message text] Word count: [N]
TOUCH 2 -- Day [N] | [Channel] [Full message text] Word count: [N]
[... all touches ...]
---
BRANCHING RULES:
(not the generic sequence touch)
SEQUENCE COMPLETION:
(even negative) means exit the sequence and go human
something the previous touch did not contain
the relationship for future attempts
(sequences built without personalisation perform at generic template level)
🚀 Marketplace of domain-specific plugins for building enterprise AI agents. Enable AI agents to perform finance, banking, legal, and sales workflows using modular domain plugins.
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from…
Activate for: load context, inject context, cross-domain context, context for this endeavour, relevant background, multi-domain…
Activate for: delegate, delegation record, handoff, delegation brief, follow-up, delegation quality, assign to, hand off to,…
Activate for: daily digest, morning briefing, what's happening today, start of day brief, week ahead, Monday brief, weekly…
Activate for: situation brief, bring me up to speed, prep me for, pre-meeting brief, decision brief, context brief, catch me up,…
Activate for: meeting prep, meeting synthesis, before the meeting, after the meeting, D/A/F/Q/R, meeting brief, stakeholder prep,…
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Also covers…
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling…