CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cold-email

Write B2B cold emails, subject lines, and follow-up sequences that read like a person wrote them. Use when the user wants a cold outreach email or a follow-up, or asks why an opener, a reason to reach out, or an email gets no replies.

Quality

89%

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.

An excellent instruction-oriented skill body: concrete, opinionated guidance with specific phrases, numbers, and templates, and a clean one-level-deep reference structure verified against the bundle. Only minor trims are possible (duplicate reference links, the roleplay opener) and the workflow could make its step sequence and reply-handling branch more explicit.

DimensionReasoningScore

Conciseness

The body is dense and prescriptive with no explanations of concepts Claude already knows, but the trailing References section duplicates links already given inline and the "You are an expert in cold outbound" opener is mild padding.

4 / 5

Actionability

For an instruction-only skill the guidance is fully actionable: fill-in framework templates ("You noticed X, which usually means Y challenge. We helped Z with that. Interested?"), exact subject-line specs ("2-4 words, lowercase"), ready-to-use CTA phrasings ("Worth exploring?"), a specific AI-tells avoid list, and numeric thresholds (bounces under 2%, 3-4 week warmup).

5 / 5

Workflow Clarity

A coherent implicit sequence (gather context, write, quality-check, send, handle replies) with an explicit Quality Check checklist and batch-send validation (verify lists, bounce rate under 2%), so the batch-operation cap does not apply; however the sequence is conveyed by section order rather than explicit steps and reply handling is compressed into a single sentence.

4 / 5

Progressive Disclosure

Verified against the actual bundle: all four referenced files (personalization.md, subject-lines.md, follow-up-sequences.md, frameworks.md) exist, each is linked inline with a summary of its contents, and none contains further nested references — a clean one-level-deep structure with SKILL.md as the overview.

5 / 5

Total

18

/

20

Passed

Description

87%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.

A strong description that clearly states its deliverables and pairs them with an explicit, naturally-phrased "Use when" trigger clause. The only gaps are minor: a few missing synonyms (prospecting, sales email) and unmentioned capabilities like reply handling that the skill body actually covers.

DimensionReasoningScore

Specificity

"Write B2B cold emails, subject lines, and follow-up sequences" names three concrete deliverables with a clear quality bar ("read like a person wrote them"), but capabilities the body covers (reply handling, deliverability) are absent from the description, leaving minor gaps in coverage.

4 / 5

Completeness

Explicitly answers both what ("Write B2B cold emails, subject lines, and follow-up sequences") and when ("Use when the user wants a cold outreach email or a follow-up, or asks why an opener... or an email gets no replies") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural user phrasings like "cold outreach email," "follow-up," "opener," and "email gets no replies" are present, but common synonyms such as "prospecting" or "sales email" are missing.

4 / 5

Distinctiveness Conflict Risk

"B2B cold emails" and "cold outreach" carve out a clear niche with distinct triggers; minimal risk of firing for a generic email-writing or marketing skill.

5 / 5

Total

18

/

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

n8n-io/n8n

Path

packages/frontend/editor-ui/src/experiments/recommendedSkills/content/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.