CtrlK
BlogDocsLog inGet started
Tessl Logo

cold-email

When the user wants to write, improve, or build a sequence of B2B cold outreach emails to prospects who haven't asked to hear from them. Use when the user mentions 'cold email,' 'cold outreach,' 'prospecting emails,' 'SDR emails,' 'sales emails,' 'first touch email,' 'follow-up sequence,' or 'email prospecting.' Also use when they share an email draft that sounds too sales-y and needs to be humanized. Distinct from email-sequence (lifecycle/nurture to opted-in subscribers) — this is unsolicited outreach to new prospects. NOT for lifecycle emails, newsletters, or drip campaigns (use email-sequence).

75

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

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.

The body is a well-structured, highly actionable guide that leverages progressive disclosure effectively through verified reference files and an analyzer script. Its main weakness is modest verbosity from stylistic prose and a generic communication section, plus validation checkpoints that are decoupled from the per-mode workflows.

Suggestions

Tighten stylistic narrative prose (e.g., 'Most deals happen in follow-ups. Most follow-ups are useless.') and consider trimming the generic Communication section if it is inherited boilerplate.

Embed the analyzer validation step explicitly within each mode's numbered workflow (e.g., add 'Score with email_sequence_analyzer.py; rewrite any email below 70; re-score' as a final pre-delivery step in Modes 1 and 2) so the feedback loop is visible inline.

Reduce rationale sentences that restate the immediately preceding guidance (e.g., 'The personalization must connect to the reason you're reaching out' repeats the prior example) to recover tokens.

DimensionReasoningScore

Conciseness

The body is dense with actionable domain guidance rather than padding about concepts Claude already knows, but stylistic prose ('Most deals happen in follow-ups. Most follow-ups are useless.') and the generic Communication boilerplate could be trimmed — efficient with minor over-explanation.

4 / 5

Actionability

Provides concrete copy-paste-ready guidance: numbered per-mode workflows, an executable script invocation with output description, good/bad opener examples, specific cadence days, and a breakup email template covering the common cases.

5 / 5

Workflow Clarity

Each of the three modes has a clearly sequenced numbered workflow, and an analyzer-based validation feedback loop ('score → rewrite below 70 → re-score') exists, but validation is stated globally in the Tools section rather than embedded as an explicit checkpoint within each mode's step list — a minor gap.

4 / 5

Progressive Disclosure

SKILL.md serves as a clear overview with well-signaled one-level-deep references (frameworks.md, follow-up-playbook.md, deliverability-guide.md — all verified to exist) and a script, with detail appropriately split out and easy navigation via 'See references/...' lines.

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.

The description is exemplary: it states concrete capabilities, supplies abundant natural trigger terms, covers both what and when, and explicitly distinguishes itself from the related email-sequence skill. No vagueness, fluff, or over-claims present.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'write, improve, or build a sequence of B2B cold outreach emails' plus 'humanized' — giving comprehensive coverage of the skill's scope, matching the score-5 anchor's level of detail.

5 / 5

Completeness

Explicitly answers both 'what' (write/improve/build/humanize B2B cold outreach emails) and 'when' ('Use when the user mentions...') with concrete trigger phrases, matching the score-5 anchor.

5 / 5

Trigger Term Quality

Provides comprehensive natural trigger terms a user would actually say — 'cold email,' 'cold outreach,' 'prospecting emails,' 'SDR emails,' 'sales emails,' 'first touch email,' 'follow-up sequence,' 'email prospecting' — covering synonyms thoroughly.

5 / 5

Distinctiveness Conflict Risk

Establishes a clear niche and explicitly disambiguates from a sibling skill ('Distinct from email-sequence... NOT for lifecycle emails, newsletters, or drip campaigns'), minimizing conflict risk.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
alirezarezvani/claude-skills
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.