CtrlK
BlogDocsLog inGet started
Tessl Logo

email-ops

Evidence-first mailbox triage, drafting, send verification, and sent-mail-safe follow-up workflow for ECC. Use when the user wants to organize email, draft or send through the real mail surface, or prove what landed in Sent.

69

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is tdg-personal/email-ops

SKILL.md
Quality
Evals
Security

Quality

Content

81%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.

A well-structured operator workflow with clear sequencing, explicit verification checkpoints, and concrete output guidance. Minor trimming of redundant Pitfalls/Guardrails and possible extraction of reference material would tighten it further.

Suggestions

Consolidate Guardrails and Pitfalls to remove restated items (e.g., 'do not claim send success without a sent-copy check' appears in both).

If the Skill Stack or Output Format grows, move detailed templates into a references file and link one level deep to support progressive disclosure.

Add 'inbox' and 'reply' as explicit trigger terms in the description to broaden natural keyword coverage.

DimensionReasoningScore

Conciseness

Lean bullet-driven workflow with no concept over-explanation; the Pitfalls section partly restates Guardrails and could be trimmed.

4 / 5

Actionability

Concrete guidance throughout — exact status words, an output-format template, and specific per-step instructions — with only minor gaps for an instruction-only skill.

4 / 5

Workflow Clarity

A clearly sequenced 4-step workflow with explicit validation ('verify the exact final body first', 'confirm the message landed in Sent') and a feedback loop for the blocked state.

5 / 5

Progressive Disclosure

Well-organized into clearly labeled sections and self-contained with no nested references; at ~115 lines it slightly exceeds the simple-skill threshold and has no external file split.

4 / 5

Total

17

/

20

Passed

Description

88%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.

A strong, third-person description that names concrete capabilities and gives explicit 'Use when' trigger guidance with natural phrasing. Slight room to add common synonyms like 'inbox' or 'reply'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'mailbox triage, drafting, send verification, and sent-mail-safe follow-up workflow' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly states both what ('Evidence-first mailbox triage, drafting, send verification...') and when ('Use when the user wants to organize email, draft or send...').

5 / 5

Trigger Term Quality

Natural phrases like 'organize email, draft or send through the real mail surface, or prove what landed in Sent' map to user speech; a few common synonyms (e.g., 'inbox', 'reply') are absent.

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche around send verification and Sent-folder proof; minor overlap risk with generic email or messaging skills.

4 / 5

Total

18

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.