Agent skill
btl-messaging
Writes cold emails targeted at Managers and Individual Contributors (Below-the-Line).
Filed under Positioning and messaging.
From Frontal-so/outbound-skills · 73 skills · 4 · pushed 2026-07-14
What it does when it runs
Writes cold emails targeted at Managers and Individual Contributors (Below-the-Line). Use when the user asks to "email a manager", "email an IC", "email an end user", "below the line", "BTL messaging", "operational email", or targets someone with a Manager/Specialist/Analyst/Coordinator title. Also triggers on "tactical messaging", "user-level email", "bottom-up outreach", "champion building email". Do NOT use for emails targeting VP/C-Level/Directors (use atl-messaging), general email writing without a specified persona, or deliverability questions.
Read from the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- frontal.so
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/Frontal-so/outbound-skills.git /tmp/outbound-skills git -C /tmp/outbound-skills sparse-checkout set "master-skills/cold-email/.claude/skills/btl-messaging" mkdir -p ~/.claude/skills/btl-messaging cp -R "/tmp/outbound-skills/master-skills/cold-email/.claude/skills/btl-messaging/." ~/.claude/skills/btl-messaging/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from Frontal-so/outbound-skills/blob/27cd847be5ce7e9b749b1d672cbfb29935d911db/master-skills/cold-email/.claude/skills/btl-messaging/SKILL.md, which is licensed MIT (repository). 425 words, 8 headings.
Below-the-Line (BTL) Messaging
You write cold emails for Managers, Individual Contributors, and End-Users. BTL targets think present (tactical), want problems solved immediately, and care about daily workflow -- not strategic vision.
Process
- Confirm BTL target -- Manager, Specialist, Analyst, Coordinator, or IC. If unclear, ask.
- Identify daily pain -- What frustrates them every day? What wastes their time?
- Draft email -- 3-4 sentences. Operational language. Specific time/effort savings.
Reference
Read {SKILL_BASE}/resources/frameworks/atl-btl-messaging.md — focus on the Below-the-Line (BTL) Messaging section for the operational language guide, decision framework, and fatal mistakes. Ignore the ATL section.
BTL Rules
- 3-4 sentences acceptable -- More detail than ATL, but still concise
- Operational language -- "Stop spending 3 hours on...", "Eliminate the manual work of...", "Save X hours/week"
- Lead with daily pain -- Name the specific frustration they deal with regularly
- Quantify time/effort savings -- "70% less time on reporting" resonates more than "improved efficiency"
- Make them look good to their boss -- BTL personas care about performance perception
What BTL Personas Care About
- Daily pain points
- Time savings
- Workflow improvements
- Making their job easier
- Looking good to their boss
Fatal Mistake
Talking about ROI, strategic impact, and board-level priorities to a manager or IC = does not resonate. It is too abstract. They do not think in those terms. You will get ignored.
When to Target BTL
- Product-led growth motion
- User adoption drives expansion
- Bottom-up sale
- Need an internal champion first
Examples
Example 1: Marketing Ops Manager
Subject: 3 hours back
Hey {{firstName}},
Stop spending 3 hours every week fighting with Excel to build campaign reports.
We helped {{similar_company}}'s ops team cut their reporting time by 70%.
Want to see how?
Example 2: SDR Team Lead
Subject: manual prospecting
Hey {{firstName}},
How much time does your team spend on manual list building each week?
Most SDR leads I talk to say 5-6 hours per rep.
We helped {{similar_company}} automate that down to 30 minutes -- their reps booked 40% more meetings.
Worth a quick look?
Example 3: Data Analyst
Subject: data cleanup
Hey {{firstName}},
If you're anything like other {{title}}s at {{industry}} companies, you're spending 10+ hours/week cleaning and merging data from different sources.
{{similar_company}}'s data team got that down to 2 hours after switching to us.
Want to see the workflow?
Part of Frontal — free, open GTM skills for your AI agent. Browse the library →
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- disqualification-messaging by louisblythe · 136
- brand-messaging-and-positioning by manojbajaj95 · 92
- product-messaging by realjaymes · 55
- product-messaging by matteotitta · 51
- positioning-messaging-designer by NEON-Rutger · 45
- gtm-messaging by taizen-ai · 8
- messaging-positioning by taizen-ai · 8
- messaging-positioning by composio-community · 2
Need help setting it up?
This page tells you what btl-messaging does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.