CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cold-email

Write and run B2B cold outbound that gets replies, from cold emails and follow-ups to sending setup, LinkedIn, multichannel cadences, and reply handling. Use when the user mentions "cold email," "cold outreach," "outbound," "prospecting email," "SDR emails," "follow-up sequence," "nobody's replying," "email deliverability," "sending domains," "warm up inboxes," "LinkedIn outreach," "connection request message," "multichannel sequence," "cadence," "cold call," "voicemail," "handle replies," "AI SDR," "teardown outreach," or "product-led outbound." Send from secondary domains, verify lists first, turn off open tracking, and stop every channel when a prospect replies. Copy avoids AI tells like 'it's not X, it's Y' reveals. For building the list and account research, see prospecting. For lifecycle email, see emails. For call scripts and sales collateral, see sales-enablement.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable overview that keeps SKILL.md as a navigable index and pushes detail one level deep into real, well-organized reference files. The two imperfections are minor: a redundant consolidated reference index that duplicates inline links, and an implicit (section-ordered rather than explicit) workflow with error-recovery detail deferred to references.

Suggestions

Trim the 'Data & Benchmarks' section: the ten references are already linked in context in their own sections, so a consolidated re-listing duplicates ~12 lines — either drop the section or keep only the inline links plus a one-line pointer that references contain performance data.

Make the end-to-end workflow sequence explicit (e.g., a short numbered 'How this skill runs' list: gather context → write → pre-send deliverability check → sequence → handle replies), and surface the one or two key stop-loss/recovery thresholds inline in 'Before You Send' instead of only in deliverability.md.

DimensionReasoningScore

Conciseness

The body is lean and prescriptive throughout — "Cold email is ruthlessly short. If a sentence doesn't move the reader toward replying, cut it" — with no explanation of concepts Claude already knows. Minor trimming opportunities remain: the "Data & Benchmarks" section re-lists all ten references already linked inline in their own sections, and the AI-tells guidance appears in three places (Voice & Tone, What to Avoid, plus the deferred copywriting reference). This sits at the 4-anchor ("efficient; minor instances that could be trimmed") rather than the 5-anchor ("every token earns its place").

4 / 5

Actionability

For an instruction-only skill the guidance is fully executable: named frameworks with example copy ("Observation → Problem → Proof → Ask — You noticed X, which usually means Y challenge... Interested?"), concrete subject-line specs ("2-4 words, lowercase" with examples like "reply rates," "hiring ops"), quantified deliverability rules ("mailboxes warmed for 3–4 weeks," "bounces under 2%"), ready-to-use CTA phrasing, and a pre-send checklist. This matches the 5-anchor's "specific examples cover the common cases"; per the rubric's scoring note, absence of code is not penalized for instruction-only skills.

5 / 5

Workflow Clarity

Sections form a coherent end-to-end sequence (Before Writing → Writing → Before You Send → Follow-ups → When They Reply) with a pre-send checklist and an explicit Quality Check before presenting, and batch-send risk is covered by concrete validation ("Verify every list right before upload and keep bounces under 2%"), so the destructive/batch cap does not apply. However, the sequence is implicit in section order rather than explicit steps, and error-recovery feedback loops (stop-loss thresholds, monitoring) are deferred to deliverability.md rather than stated inline — the 4-anchor ("clear sequence with most checkpoints present; minor validation gaps") is the best fit.

4 / 5

Progressive Disclosure

SKILL.md is a genuine overview (~210 lines) with ten one-level-deep references, each clearly signaled at its point of use ("See [subject-lines.md](references/subject-lines.md) for the full data") and all verified to exist in references/. Cross-links between reference files are lateral sibling links, not nested chains, and bulk detail (benchmarks, full framework catalog, tool setup) is appropriately split out. This matches the 5-anchor ("clear overview with well-signaled one-level-deep references; easy navigation").

5 / 5

Total

18

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: concrete action inventory, an explicit Use-when clause with ~20 natural trigger phrases including colloquial variants, and explicit boundary routing to adjacent skills that minimizes mis-triggering. Dense rather than padded — every clause carries capability or trigger information.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with comprehensive coverage of the domain: "Write and run B2B cold outbound... from cold emails and follow-ups to sending setup, LinkedIn, multichannel cadences, and reply handling" plus operational directives like "Send from secondary domains, verify lists first, turn off open tracking." Anti-drift check against the 4-anchor ("several specific actions; minor gaps") finds no meaningful gap within the skill's stated scope, so the 5-anchor "comprehensive coverage" is the best fit.

5 / 5

Completeness

It explicitly answers both questions: "what" via "Write and run B2B cold outbound that gets replies... LinkedIn, multichannel cadences, and reply handling" and "when" via the explicit "Use when the user mentions" clause with concrete trigger phrases. This is a direct match to the 5-anchor example pattern and clearly above the 4-anchor ("'when' could be more explicit").

5 / 5

Trigger Term Quality

It includes ~20 natural trigger phrases — "cold email," "cold outreach," "SDR emails," "follow-up sequence," "nobody's replying," "warm up inboxes," "connection request message," "AI SDR" — covering synonyms, colloquial user phrasings, and adjacent channel terms. This matches the 5-anchor "comprehensive coverage of natural terms including synonyms"; the 4-anchor ("a few natural terms missing") would understate the breadth.

5 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (B2B cold outbound) with distinct triggers and actively reduces conflict risk by routing edge cases to sibling skills: "For building the list and account research, see prospecting. For lifecycle email, see emails. For call scripts and sales collateral, see sales-enablement." This meets the 5-anchor ("clear niche with distinct triggers; minimal conflict risk") rather than the 4-anchor, which only tolerates unresolved minor overlap.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

coreyhaines31/marketingskills

Path

skills/cold-email/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.