CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-cold-mail-1-template

A proven Dutch cold-mail template for SME outreach using the no-price, demo-first framework. Use when: Draft a Dutch cold outreach email for local SMEs; Implement the Nex demo-first outreach rule; Create a website-audit hook for technical sales.

Quality

57%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/nex-business-operations/skills/nex-cold-mail-1-template/SKILL.md

The canonical home for this skill is nex-cold-mail-1-template in NexaiGuy/nex-ai-skills

SKILL.md
Quality
Evals
Security

Quality

Content

28%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 reads as a marketplace product page rather than an operational skill: it describes benefits and answers sales FAQs but omits the actual Dutch template, which it points to via a nonexistent assets file. Without the template, the variables, or any usage steps, Claude could not execute the skill's single task.

Suggestions

Include the full Dutch cold-mail template inline (or restore assets/cold_mail_1.txt) so the dangling '[Template continues in assets/cold_mail_1.txt...]' reference resolves to real content.

Add a short usage workflow: collect lead fields, map them to {{BEDRIJFSNAAM}}/{{VOORNAAM}} and any other documented variables, apply the no-price demo-first structure, and append the mandatory opt-out line and single CTA.

Remove the marketing sections ('The problem', 'Why this beats prompting it yourself', the FAQ) and keep only instructional content to reclaim the token budget.

DimensionReasoningScore

Conciseness

Several sections are promotional padding rather than instruction: 'Why this beats prompting it yourself' sells the skill, and the FAQ answers ('You will receive the structured template framework...', 'available to you through your marketplace library') are marketplace copy with no operational value. It is above 1 because it does not extensively explain concepts Claude already knows, but clearly below 3 given the volume of non-instructional text.

2 / 5

Actionability

The core deliverable is withheld: the example cuts off at '[Template continues in assets/cold_mail_1.txt with AI-search hook and no-price demo offer]', that file does not exist in the bundle, and the body states 'Scripts, extension source, and templates from the original package are not in this folder.' The template variables {{BEDRIJFSNAAM}} and {{VOORNAAM}} are never documented, leaving only high-level hints (no-price rule, opt-out line, single CTA) without executable specifics. It is not 1 because the example fragment and named rules are minimal concrete guidance.

2 / 5

Workflow Clarity

No sequence exists for actually producing the email: there are no steps for gathering lead details, filling the variables, constructing the website-audit hook, or placing the opt-out line. The simple-skill exception does not apply because the single action's output (the template) is absent, so the action is ambiguous; a rough direction ('no-price, demo-first', 'single clear call-to-action') keeps it above 1.

2 / 5

Progressive Disclosure

The body is short with clear section headers and no nested references, but its only bundle reference, assets/cold_mail_1.txt, is dangling — the assets directory does not exist — so navigation to the key content fails. Structure is present yet fails at the point it matters, which fits anchor 3 better than 4 ('references mostly clear') or 2 (content is not inlined; it is missing).

3 / 5

Total

9

/

20

Passed

Description

70%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 has a clear niche with an explicit and well-structured 'Use when' clause, so completeness and distinctiveness are strong. Weaknesses are the noun-phrase 'what' with promotional language ('proven') instead of concrete action verbs, and a trigger list where one entry is proprietary jargon.

Suggestions

Replace the noun-phrase 'what' with concrete third-person actions, e.g. 'Generates a Dutch cold outreach email for local SMEs using the no-price, demo-first framework'.

Drop 'proven' and brand-specific triggers like 'Implement the Nex demo-first outreach rule' in favor of natural user phrasings such as 'cold email for Belgian or Dutch SMEs' or 'B2B prospecting email'.

DimensionReasoningScore

Specificity

The description names the domain ('Dutch cold-mail template for SME outreach using the no-price, demo-first framework') but is a noun phrase with the marketing adjective 'proven' rather than a list of concrete actions, and the 'Use when' triggers use imperative (second-person) voice rather than third-person gerunds, which the guidelines penalize. It sits above 1 (domain and framework are concrete) but below 3 (no action verbs like 'Generates' or 'Drafts' describing what it does).

2 / 5

Completeness

It explicitly answers both what ('A proven Dutch cold-mail template for SME outreach using the no-price, demo-first framework') and when ('Use when: Draft a Dutch cold outreach email...; Create a website-audit hook...') with three concrete trigger phrases, matching the anchor-5 pattern. It is not 4 because the 'when' clause is already explicit and specific rather than merely present.

5 / 5

Trigger Term Quality

'Draft a Dutch cold outreach email for local SMEs' is a natural phrase a user would say, but 'Implement the Nex demo-first outreach rule' is proprietary brand jargon and common synonyms (B2B, prospecting, Belgian, follow-up) are absent. It does not reach 4 because a third of the trigger list is jargon no user would naturally say.

3 / 5

Distinctiveness Conflict Risk

'Dutch cold-mail template', 'no-price, demo-first', 'website-audit hook', and 'local SMEs' carve out a clear niche with distinct triggers and minimal overlap with generic outreach or copywriting skills. No neighboring anchor fits better.

5 / 5

Total

15

/

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

NexaiGuy/nex-ai-skills

Path

plugins/nex-business-operations/skills/nex-cold-mail-1-template/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.