CtrlK
BlogDocsLog inGet started
Tessl Logo

email-drafter

Use this skill when the user wants to draft, improve, or respond to emails — cold outreach, follow-ups, escalations, team announcements, or any professional communication.

67

Quality

80%

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

61%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 content is concrete and code-driven with a clean section structure, but it hardcodes a stale-prone model version, leaves the choice between its three entry points implicit, and lacks validation checkpoints. It is solidly above the midpoint but not top-tier.

Suggestions

Remove the hardcoded model="claude-opus-4-6" pins (or move them to a deprecated/old-patterns note) so the skill does not carry time-sensitive version info in the main body.

Add a short decision guide stating when to use draft_by_type versus draft_email versus improve_email, so the intended workflow is explicit rather than inferred.

Drop the Quick Reference table or the EMAIL_CONTEXTS dict to remove the redundancy, or keep the table inline and move the full dict to a reference file.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's competence, but hardcodes a time-sensitive model version ("claude-opus-4-6", twice) outside any deprecated section and the Quick Reference table partly duplicates the EMAIL_CONTEXTS dict, so it could be tightened.

3 / 5

Actionability

Three concrete, executable Python functions (draft_email, draft_by_type, improve_email) with real API calls are mostly copy-paste ready; minor gaps include improve_email relying on a module-level client and undocumented include_variants behavior.

4 / 5

Workflow Clarity

Three entry points are presented without explicit guidance on when to use draft_email vs draft_by_type vs improve_email, and there are no validation/error-handling checkpoints, leaving the intended sequence implicit.

3 / 5

Progressive Disclosure

The single self-contained file is well-organized into clear sections (Overview, Draft Email, Email Types, Improve, Quick Reference) with no nested references; it slightly exceeds 50 lines but needs no external files, so structure is good with only minor organization gaps.

4 / 5

Total

14

/

20

Passed

Description

100%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 is exemplary: third-person voice, explicit "Use when" trigger, concrete actions, and a rich set of natural trigger terms with low conflict risk. It hits the top anchor on every dimension.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ("draft, improve, or respond to emails") and enumerates a comprehensive set of email types (cold outreach, follow-ups, escalations, team announcements), matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers both what ("draft, improve, or respond to emails") and when ("Use this skill when the user wants to...") with concrete trigger phrases, hitting the top anchor.

5 / 5

Trigger Term Quality

Natural user phrases abound — "draft, improve, or respond to emails" plus synonyms like cold outreach, follow-ups, escalations, and team announcements — giving comprehensive coverage of terms a user would actually say.

5 / 5

Distinctiveness Conflict Risk

Email drafting is a clear niche with distinct triggers (cold outreach, follow-ups, escalations) and minimal overlap risk with other skills; the broad "professional communication" tail is scoped to emails.

5 / 5

Total

20

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ProwlrBot/prowlr-marketplace
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.