skills/ai-marketing-skills/cold-outreach-sequence/SKILL.md
Build personalized cold outreach sequences for LinkedIn and email. Use when someone needs to reach prospects, warm up cold leads, or build a systematic outreach engine. Covers research, connection requests, follow-ups, and conversion.
npx skillsauth add aaaaqwq/claude-code-skills cold-outreach-sequenceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Here's what I've learned about cold outreach: the word "cold" is the problem.
Spray-and-pray templates don't work. 10 minutes of research + a specific reference = not cold anymore. This skill builds the second kind.
Before writing any message, collect:
positioning-basics output if available)Research tool calls — run before writing:
web_search('[Company] [Founder/Name] news 2026')
web_search('[Company] funding recent')
web_search('[Person name] [Company] LinkedIn')
Personalization constraint: Do not write a Tier 1 message without a named specific signal from research. If search yields 0 signals, default to Tier 3 and say so explicitly.
For each prospect, document findings before drafting:
Signal types (ranked by message strength):
Personalization tier assignment:
| Research Result | Tier | Approach | |---|---|---| | Named signal (news + post + context) | Tier 1 | Fully custom, reference signal in every message | | Company info + role context | Tier 2 | Template + personalized opener | | No signals found | Tier 3 | Volume template, minimal customization |
Formula: [Specific observation from research] + [Simple reason to connect]
Rules:
By signal type:
Recent funding: "Congrats on the Series A — the [investor] backing is a smart signal. Would love to connect."
Recent post: "Your post on [specific topic] resonated — been thinking the same thing. Happy to connect."
News/launch: "Saw the [product] launch — [specific detail] is smart positioning. Would love to connect."
Formula: [Thanks] + [Bridge to relevance] + [Light value] + [Soft question]
Template:
Thanks for connecting. I work with [ICP description] on [specific outcome].
Curious — is [relevant function] something you own directly at [Company],
or is that still founder-led?
Happy to share what I'm seeing work at similar-stage companies either way.
Formula: [Light nudge] + [New signal or angle] + [Easy out]
Constraint: Do NOT write "following up" with nothing new. Add one new piece:
Template:
Bumping this up — came across [specific article/trend/insight] and
thought of your situation at [Company].
[One sentence on why it's relevant to them.]
Happy to share more if useful. If not, no worries.
Shift to email if LinkedIn hasn't converted, or try a different angle.
Subject line options:
Email structure:
[1-line hook tied to their specific situation]
[2-3 sentences: why you're reaching out + one proof point]
[Soft CTA — 1 sentence]
I'll assume timing isn't right — totally get it.
If [relevant pain point] becomes a priority down the road, happy to reconnect.
Best of luck with [specific thing they're working on based on research].
Post-break-up action: Add to 6-month re-engagement list with a resurface date.
After generating the full sequence, evaluate:
Flag any issue: "The first message doesn't include a soft question — it reads as a pitch. Revised to invite dialogue."
Always output a tracking table for the batch:
| Prospect | Company | Platform | Tier | Sent Date | Response | Stage | Next Action | Resurface Date |
|---|---|---|---|---|---|---|---|---|
| [Name] | [Co] | LinkedIn | 1 | [date] | — | Connection sent | Wait 24-48h | — |
| [Name] | [Co] | Email | 2 | [date] | — | First email sent | Follow-up Day 7 | — |
After each response (or non-response), ask:
## Outreach Sequence: [Prospect Name] — [Date]
### Research Summary
- Signal type: [news / post / company info / none]
- Signal found: "[Specific detail]"
- Personalization tier: [1/2/3]
- Source: [URL or platform]
### Sequence
**Connection Request (LinkedIn):**
[Text — max 300 chars]
**First Message (Day 1-2 after accept):**
[Text]
**Follow-Up #1 (Day 7):**
[Text]
**Follow-Up #2 (Day 14):**
Platform: [LinkedIn / Email]
Subject: [if email]
[Text]
**Break-Up (Day 21):**
[Text]
### Pipeline Entry
| Prospect | Company | Platform | Tier | Stage | Next Action | Resurface Date |
|---|---|---|---|---|---|---|
| [Name] | [Co] | [Platform] | [Tier] | Connection sent | Wait 24-48h | — |
### Self-Critique Notes
[Any issues flagged + revisions made]
Skill by Brian Wagner | AI Marketing Architect | brianrwagner.com
testing
通用自媒体文章自动发布工具。支持百家号、搜狐号、知乎、微信公众号、小红书、抖音号六个平台的自动化发布流程。使用Playwright自动化实现平台导航和发布,支持通过storageState管理Cookie实现账号切换。
development
# SKILL.md - Model Configuration Status (mcstatus) ## 触发条件 - `/mcstatus` 命令 - 用户询问模型配备、模型配置、model status、模型列表等 ## 功能 实时生成 Agent + Cron 的模型配置报告,展示当前所有 agent 的主模型/fallback链和所有 cron 任务的模型分配。 ## 执行步骤 ### Step 1: 收集 Agent 模型配置 读取各 agent 的 models.json 获取主模型和 fallback 链: ```bash for agent in main ops code quant data research content market finance pm law product sales batch; do config=$(cat ~/.openclaw/agents/$agent/agent/models.json 2>/dev/null) if [ -n "$config" ]; then echo "=== $agent
tools
MCP 服务器智能管理助手。自动检测 MCP 可用性、智能开关、功能问答,提供人性化的 MCP 管理体验。
tools
从GitHub搜索并自动安装配置MCP(Model Context Protocol)服务器工具到Claude配置文件。当用户需要安装MCP工具时触发此技能。工作流程:搜索GitHub上的MCP项目 -> 提取npx配置 -> 添加到~/.claude.json -> 处理API密钥(如有)。