CtrlK
BlogDocsLog inGet started
Tessl Logo

ai-cold-outreach

When the user wants to build an AI-powered outreach system, write cold emails, improve deliverability, or scale personalized outreach. Also use when the user mentions 'cold email,' 'cold outreach,' 'outreach automation,' 'Instantly,' 'Smartlead,' 'Clay,' 'email sequences,' 'deliverability,' 'personalization at scale,' 'reply rate,' or 'outreach stack.' This skill covers the complete AI cold outreach system from signal detection through conversion. Do NOT use for technical implementation, code review, or software architecture.

72

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

A highly actionable, well-sequenced guide rich in concrete domain data and validation checkpoints, but it is verbose and keeps substantial detail inline that could move to the existing reference files. Tightening the body and offloading the platform-comparison tables would lift its weakest dimensions.

Suggestions

Trim the large ASCII pipeline diagrams and editorial sentences (e.g. 'Cold email without signals is spam with extra steps') to reduce tokens without losing guidance.

Move the Instantly vs. Smartlead comparison table and per-mailbox/domain sizing tables into references, leaving a brief decision framework inline — this addresses both conciseness and progressive_disclosure.

Relocate time-sensitive framing ('highest-performing cold emails in 2026', 'Data from 2025 shows') into a dated/deprecated reference section so the main body stays evergreen and concise.

DimensionReasoningScore

Conciseness

Mostly efficient and information-dense, but the ~470-line body includes large decorative ASCII pipeline diagrams and editorializing ('Cold email without signals is spam with extra steps') plus time-sensitive framing ('highest-performing cold emails in 2026', 'Data from 2025') that could be tightened; not the lean score-3 anchor and not the padded score-1 anchor.

2 / 3

Actionability

Provides fully executable guidance — 'Domains needed = daily_volume / 150', '25-30/day' sending limits, the DMARC rollout sequence, the authentication checklist, and the A/B testing priority table — copy-paste ready rather than abstract.

3 / 3

Workflow Clarity

The six-stage pipeline (Signal -> Enrichment -> Personalization -> Sequencing -> Sending -> Follow-up) is clearly sequenced with explicit validation checkpoints — 'Run every email through verification... before sending', 'Bounce rate must stay under 2%', and the weekly warmup/DMARC progressions — so the batch-operation cap does not apply.

3 / 3

Progressive Disclosure

Two real, well-signaled one-level-deep references exist (references/benchmarks-deliverability-tactics.md and references/quick-reference.md), but the SKILL.md itself is a large monolithic body with the full platform-comparison tables and sending-infra details inline; 'content that should be separate is inline' pulls it below the score-3 anchor.

2 / 3

Total

10

/

12

Passed

Description

100%

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, third-person description that names concrete capabilities, lists a wide range of natural trigger terms, and gives explicit use/avoid guidance. It clearly distinguishes the skill from adjacent technical skills via the Do-NOT-use clause.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'build an AI-powered outreach system, write cold emails, improve deliverability, or scale personalized outreach' — matching the multi-action anchor rather than the single-domain score-2 example.

3 / 3

Completeness

Explicitly answers both what ('covers the complete AI cold outreach system from signal detection through conversion') and when ('Also use when the user mentions...'), with an explicit 'Do NOT use' exclusion; not the level below where 'when' is only implied.

3 / 3

Trigger Term Quality

Broad coverage of natural terms a user would actually say — 'cold email,' 'cold outreach,' 'Instantly,' 'Smartlead,' 'Clay,' 'email sequences,' 'deliverability,' 'reply rate,' 'outreach stack' — matching the good-coverage anchor.

3 / 3

Distinctiveness Conflict Risk

A clear niche with distinct triggers plus an explicit exclusion ('Do NOT use for technical implementation, code review, or software architecture') makes conflict with adjacent skills unlikely.

3 / 3

Total

12

/

12

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
tech-leads-club/agent-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.