CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cold-email

Write B2B cold emails and follow-up sequences that earn replies. Use when creating outbound prospecting emails, SDR outreach, personalized opening lines, subject lines, CTAs, and multi-touch follow-up sequences.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%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-crafted, instruction-only skill body: lean, idiomatic, and actionable, with concrete rules and examples instead of abstract advice, a clear context-gather-write-check workflow, and exemplary one-level-deep reference structure where every linked file exists. Remaining gaps are minor: slight list redundancy, no inline worked example email, and heuristic rather than explicit validation loops.

DimensionReasoningScore

Conciseness

The body is efficient throughout: short sections, punchy bullets, no explanation of concepts Claude already knows (no "what is a cold email" padding), and idiomatic craft guidance like "The best cold emails feel like they could have been shorter, not longer". It misses the 5 anchor only through minor redundancy — the "What it should NOT sound like" list and the "What to Avoid" section overlap on AI-tell phrases and jargon, and the Related Skills section is optional overhead.

4 / 5

Actionability

Guidance is concrete and executable for a writing task: exact subject-line rules ("2-4 words, lowercase, no punctuation tricks") with real examples ("reply rates," "hiring ops"), specific CTA phrasings ("Worth exploring?"), four named framework shapes with worked micro-flows, and a concrete banned-phrase list. It stops short of the 5 anchor because no complete worked example email is shown inline — the full examples are deferred to references, leaving a minor gap for the most common case.

4 / 5

Workflow Clarity

The sequence is clear and ordered: check for product-marketing context first, gather the five situational inputs (with an explicit don't-block-on-missing-inputs rule), apply writing principles, then run the pre-delivery "Quality Check" gut-list. This is a coherent flow with a checkpoint before presenting. It is not 5 because the checkpoints are heuristic gut-checks rather than explicit validate-and-fix feedback loops, and there is no guidance on iterating when the quality check fails.

4 / 5

Progressive Disclosure

SKILL.md is a lean overview that splits detail appropriately: each topic links to a real one-level-deep reference file (all five referenced files exist — personalization.md, frameworks.md, subject-lines.md, follow-up-sequences.md, benchmarks.md), links are made in context where each topic is discussed, and the "Data & Benchmarks" section doubles as a consolidated annotated index. No nested references, no dangling links, no inlined bulk content.

5 / 5

Total

17

/

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: it answers what and when explicitly, in third person, with concrete natural-language triggers covering the cold-outreach niche. The only weaknesses are a slightly thin 'what' clause and a few missing synonyms (e.g., "cold outreach").

DimensionReasoningScore

Specificity

The description lists several specific deliverables — "Write B2B cold emails and follow-up sequences that earn replies" plus enumerated components ("personalized opening lines, subject lines, CTAs, and multi-touch follow-up sequences") — matching the anchor for several specific actions with minor gaps. It falls short of the 5 anchor because the core 'what' names only two actions (cold emails, follow-up sequences), with the rest of the component list carried by the 'when' clause.

4 / 5

Completeness

Both questions are explicitly answered: 'what' is stated concretely ("Write B2B cold emails and follow-up sequences that earn replies") and 'when' is explicit with concrete trigger phrases ("Use when creating outbound prospecting emails, SDR outreach, personalized opening lines, subject lines, CTAs, and multi-touch follow-up sequences"). This mirrors the 5-anchor example structure almost exactly; the 4 anchor would require a weaker or less specific 'when' clause.

5 / 5

Trigger Term Quality

Natural trigger phrases are well covered: "B2B cold emails", "outbound prospecting emails", "SDR outreach", "subject lines", "CTAs", "multi-touch follow-up sequences" — users would plausibly say most of these. A few common variations are missing (e.g., "cold outreach", "sales outreach", "prospecting sequence"), which fits the 'good keyword coverage; a few natural terms missing' anchor rather than the comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

"B2B cold emails", "outbound prospecting", and "SDR outreach" form a clear niche with distinct triggers, and the description consistently scopes to outbound-to-strangers (replies, prospecting) rather than general email or copywriting. Minimal conflict risk with related copywriting or lifecycle-email skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

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.