CtrlK
BlogDocsLog inGet started
Tessl Logo

email-writer

Draft clear, well-structured emails — replies, outreach, and follow-ups — in the right tone.

62

Quality

72%

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 ./apps/desktop/electron/default-skills/email-writer/SKILL.md
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.

The body is a tight, well-structured instruction skill with concrete heuristics and a clear workflow; its main gap is the absence of a full worked example that would make the guidance fully copy-ready.

Suggestions

Add one short worked example (subject + body) showing the principles applied end-to-end to lift actionability.

Tighten the opening paragraph and any editorial phrasing in Principles to push conciseness toward fully lean.

Consider a one-line self-check in 'How to work' (e.g. 'Confirm the ask, deadline, and next step are all explicit before sending') to add a lightweight validation checkpoint.

DimensionReasoningScore

Conciseness

The 31-line body is lean, assumes Claude's competence, and avoids explaining generic concepts; rated 4 rather than 5 because the opening paragraph and a few principles carry light editorial framing that could be trimmed further.

4 / 5

Actionability

Provides concrete, executable guidance with specific do/don't examples ('Cut throat-clearing ("I hope this finds you well…")', 'not "let me know your thoughts"') and a defined output format; not a 5 because it lacks a complete worked example email to copy.

4 / 5

Workflow Clarity

The 'How to work' section gives a clear 4-step sequence (goal/recipient/tone → subject → body → trim) appropriate to a simple non-destructive skill; held at 4 because steps remain slightly abstract and there are no explicit self-check points.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references, and organized into clear, well-labeled sections (When to use, Principles, How to work, Output format), matching the rubric's simple-skill exception for a top score.

5 / 5

Total

17

/

20

Passed

Description

66%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 specific and reasonably distinct, naming concrete email types and natural trigger terms, but it omits any explicit 'when to use' guidance, which caps its completeness.

Suggestions

Add an explicit 'Use when...' clause naming trigger phrases (e.g. 'Use when drafting or rewriting a reply, outreach, or follow-up email').

Include common variant phrasings such as 'email', 'reply', and 'follow up' alongside the current plural forms to broaden trigger coverage.

Optionally signal the boundary with adjacent skills (e.g. 'not for marketing sequences or team announcements') to reduce conflict risk.

DimensionReasoningScore

Specificity

Names the email domain and several concrete action types — 'Draft clear, well-structured emails', 'replies, outreach, and follow-ups' — matching the 'several specific actions; minor gaps' anchor; not a 5 because coverage of email kinds is not comprehensive.

4 / 5

Completeness

Clearly states what the skill does ('Draft clear, well-structured emails') but has no explicit 'Use when...' trigger clause; per the rubric guideline a missing trigger clause caps completeness at 3, and it is not a 4 because 'when' is only weakly implied.

3 / 5

Trigger Term Quality

Includes natural terms users say ('emails', 'replies', 'outreach', 'follow-ups') but misses common singular/variant phrasings like 'email', 'reply', 'follow up', fitting the 'good coverage; a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

Scoped to transactional one-to-one emails (replies, outreach, follow-ups), giving it a clear niche with only minor overlap risk against broader writing/comms skills; not a 5 because the description alone does not explicitly contrast adjacent skills.

4 / 5

Total

15

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
holaboss-ai/holaOS
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.