CtrlK
BlogDocsLog inGet started
Tessl Logo

professional-email-drafting

Use this skill when drafting emails, Slack messages, announcements, or any external/internal communication. Apply professional structure and appropriate tone before writing any message.

73

Quality

91%

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

100%Weight 40%Scale 1-3

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

A well-crafted, compact instruction skill: concise, concrete, and clearly organized into actionable sections with a usable subject-line template and audience-specific tone rules, with no wasted tokens.

DimensionReasoningScore

Conciseness

The body is lean — roughly twelve lines, no padding, no explaining concepts Claude already knows (it never defines what an email is), and every line carries actionable guidance, so every token earns its place.

3 / 3

Actionability

It gives concrete, executable guidance: a five-part structure, a copy-paste subject-line template ('[Action needed] Deadline for X by Friday'), explicit tone rules per audience, and a concrete length rule ('One screen or less'). For an instruction-only skill this is actionable without needing code.

3 / 3

Workflow Clarity

The composition process is a clear five-step sequence (subject, opening, body, ask, closing); this is a simple, non-destructive single task, so the simple-skills note applies and the unambiguous sequence scores full marks without requiring validation checkpoints.

3 / 3

Progressive Disclosure

The skill is under fifty lines, needs no external references, and is organized into clearly labeled sections (Structure, Tone calibration, Length), satisfying the small-skill exception for progressive disclosure.

3 / 3

Total

12

/

12

Passed

Description

82%Weight 40%Scale 1-3

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 with an explicit 'Use when' trigger and natural keyword coverage, weakened slightly by abstract secondary actions ('appropriate tone') and an overly broad catch-all phrase that raises conflict risk.

Suggestions

Replace the abstract 'appropriate tone' with concrete actions (e.g., 'match register to audience, set formality level, adjust greeting and sign-off') to raise specificity.

Tighten the catch-all 'or any external/internal communication' to specific channels (e.g., 'client emails, internal team updates, all-hands announcements') to reduce overlap with other communication skills.

DimensionReasoningScore

Specificity

It names the domain and several specific communication types ('drafting emails, Slack messages, announcements'), but the actual verbs are limited to 'drafting' and the secondary actions ('Apply professional structure and appropriate tone') are abstract — 'appropriate tone' is vague, so it does not reach the multiple-concrete-actions anchor.

2 / 3

Completeness

It explicitly answers both halves: what ('Apply professional structure and appropriate tone before writing any message') and when ('Use this skill when drafting emails, Slack messages, announcements...'), with an explicit trigger clause.

3 / 3

Trigger Term Quality

It surfaces natural terms a user would actually say — 'emails', 'Slack messages', 'announcements', 'external/internal communication' — giving good coverage of common phrasings.

3 / 3

Distinctiveness Conflict Risk

The core triggers (emails, Slack, announcements) are distinct, but the catch-all 'or any external/internal communication' broadens scope enough that it could overlap with other communication-related skills, keeping it just short of a clear conflict-free niche.

2 / 3

Total

10

/

12

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.

Validation15 / 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
aiming-lab/MetaClaw
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.