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.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

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, real validation checkpoints, a feedback loop for blocked sends, and a concrete output template. It is concise and actionable; the only soft spots are a few trimmable framing sentences and the lack of own bundle files for deeper progressive disclosure.

Suggestions

Tighten the 'inbound mail is untrusted' preamble — the security rules already imply the rationale; the opening sentence restates a concept Claude already knows.

Consider moving the security guardrails into a references/ file (e.g. SECURITY.md) so the main SKILL.md stays an overview, improving progressive disclosure.

Make 'select the correct channel and sender account' more actionable by naming the ECC channel selection rule or where to find the canonical account mapping.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence with short list-based sections, but the 'this is not a generic writing skill' framing and the 'inbound mail is untrusted' preamble add a few sentences that could be trimmed.	4 / 5
Actionability	It gives concrete, actionable guidance — fixed status vocabulary (drafted/approval-pending/sent/blocked/awaiting verification), an explicit output-format template, and a numbered workflow — though some steps like 'select the correct channel' stay directional rather than fully specified.	4 / 5
Workflow Clarity	The four-step workflow is clearly sequenced with explicit validation (verify the final body, confirm the message landed in Sent) and a feedback loop (blocked → preserve draft and report the exact blocker), plus a closing Verification checklist.	5 / 5
Progressive Disclosure	Content is well organized into labeled sections and signals one-level-deep peer-skill pulls (brand-voice, investor-outreach, etc.) rather than inlining them, but it is a single self-contained file with no own reference files to demonstrate deeper disclosure.	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 description that clearly pairs concrete capabilities with explicit 'Use when' triggers and carves an ECC mail-surface niche. The main gap is slightly narrower trigger-term coverage (missing synonyms like inbox/reply/follow-up).

Suggestions

Add a few natural trigger synonyms to the 'Use when' clause, e.g. 'triage inbox', 'reply to a thread', or 'follow up on sent mail', so users phrasing it differently still hit the skill.

Consider naming the .msg/.eml or specific client surfaces if ECC supports them, to sharpen distinctiveness against generic drafting skills.

Dimension	Reasoning	Score
Specificity	The description names multiple concrete actions — 'mailbox triage, drafting, send verification, and sent-mail-safe follow-up workflow' — giving comprehensive coverage rather than just a few.	5 / 5
Completeness	It explicitly states both what it does ('Evidence-first mailbox triage, drafting, send verification...') and when to use it ('Use when the user wants to organize email, draft or send...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	It includes natural phrases users would say ('organize email', 'draft or send', 'prove what landed in Sent'), but misses common synonyms like 'inbox', 'reply', or 'follow up' as explicit triggers.	4 / 5
Distinctiveness Conflict Risk	It is scoped to ECC and the real mail surface with a distinctive 'prove what landed in Sent' trigger, but 'email' is a broad domain with some overlap risk against generic drafting skills.	4 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/email-ops/SKILL.md
Commit: e04ea0b

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.