CtrlK
BlogDocsLog inGet started
Tessl Logo

email-systems

You are an email systems engineer who has maintained 99.9% deliverability across millions of emails. You've debugged SPF/DKIM/DMARC, dealt with blacklists, and optimized for inbox placement. You know that email is the highest ROI channel when done right, and a spam folder nightmare when done wrong.

44

Quality

46%

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/AI-Agents-Safe-Coding-Skills-claude/skills/email-systems/SKILL.md

The canonical home for this skill is email-systems in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

40%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 well-organized and reasonably lean but offers almost no executable guidance — patterns are abstract descriptions and the Sharp Edges 'solutions' are placeholder labels. No sequenced workflow or validation checkpoints exist for a high-volume, hard-to-reverse operation.

Suggestions

Replace abstract pattern descriptions with concrete, executable guidance — e.g. sample SPF/DKIM/DMARC DNS records, a multipart/alternative MIME skeleton, and an unsubscribe List-Unsubscribe header snippet.

Turn the Sharp Edges 'Solution' column from comment labels into actual instructions, or link to reference files containing the DNS records, IP warm-up schedule, and bounce-handling requirements.

Add a sequenced send workflow with validation checkpoints (authenticate DNS -> warm up IP -> monitor bounce/complaint rates -> halt if thresholds exceeded), and remove the persona intro paragraph that duplicates the frontmatter.

DimensionReasoningScore

Conciseness

Mostly terse one-liners and a compact table, but the opening persona paragraph duplicates the frontmatter description and adds opinion padding ('highest ROI channel', 'infrastructure, not an afterthought').

3 / 5

Actionability

Names concrete topics (transactional queue with retry, bounce handling, IP warm-up) but gives no executable code, commands, or specific steps; the Sharp Edges 'Solution' column entries are comment-style labels rather than real guidance.

2 / 5

Workflow Clarity

Content is organized by category (patterns/anti-patterns/sharp edges) but presents no sequenced workflow or validation checkpoints for what is a batch, hard-to-reverse operation (sending at volume).

2 / 5

Progressive Disclosure

A compact single-file skill (~45 lines) with well-organized sections and no external references needed; the vacuous 'When to Use' section is the only minor organization gap.

4 / 5

Total

11

/

20

Passed

Description

53%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 conveys a clear domain and concrete technical actions but is framed as a second-person persona with no explicit 'Use when' trigger guidance, capping completeness and reducing specificity. Trigger keywords are relevant but jargon-heavy and missing common phrasings.

Suggestions

Rewrite in third person and lead with capabilities rather than persona, e.g. 'Configures SPF/DKIM/DMARC, handles blacklists, and optimizes inbox placement for transactional email.'

Add an explicit 'Use when...' trigger clause naming natural phrasings, e.g. 'Use when emails go to spam, deliverability drops, or the user mentions SPF/DKIM/DMARC, blacklists, or inbox placement.'

Add simpler synonym triggers ('emails going to spam', 'email not delivering') alongside the technical terms to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

Names the email-deliverability domain with several concrete actions ('debugged SPF/DKIM/DMARC, dealt with blacklists, and optimized for inbox placement'), but the second-person persona voice ('You are an email systems engineer') triggers a one-point specificity reduction per the rubric.

3 / 5

Completeness

Conveys the expertise (a 'what' of sorts) but provides no 'Use when...' trigger clause, so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes relevant domain keywords (deliverability, SPF/DKIM/DMARC, blacklists, inbox placement, spam folder) but leans technical and omits simpler natural phrasings and synonyms a user might actually say.

3 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (email deliverability infrastructure) mostly distinct from other skills with only minor overlap against generic email tasks; lacks explicit triggers needed for a 5.

4 / 5

Total

13

/

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.

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
administrakt0r/AI-Agents-Safe-Coding-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.