email-triage

Scan and process unread emails. Scores by priority (VIP, urgency, deadlines), classifies, saves relevant emails as vault notes, and generates a triage report. Triggers: EN: "check my email", "what's in my inbox", "process emails", "email triage", "anything urgent in email?", "save important emails". IT: "controlla le email", "cosa c'è nella mia inbox", "triage email", "processa le email", "email urgenti". FR: "vérifier mes emails", "trier mes emails". ES: "revisar mi correo", "triaje de emails". DE: "E-Mails prüfen", "Posteingang sichten". PT: "verificar meus emails", "triagem de emails".

Quality

82%

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

65%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable content with concrete commands, a precise priority-scoring rubric, and complete templates, but it is long and monolithic. Tightening the inline templates and adding explicit batch-validation checkpoints would lift the weaker dimensions.

Suggestions

Fix the duplicate '3.' step in the Procedure (both 'Read messages' and 'Priority scoring' are numbered 3) so the sequence reads 1–8 cleanly.

Add an explicit validation checkpoint for the batch operation — e.g., after note creation, verify each saved note exists in {{inbox}}/ and re-run on any write failure before producing the final report — to clear the workflow_clarity batch-validation cap.

Move the five full note templates and the final-report example into a bundled references/ file (e.g., templates.md) and link to it one level deep, trimming the inline SKILL.md body and improving progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly actionable specifics with no concept-explanation fluff, but at ~460 lines it embeds five full templates inline plus a complete final-report mock block and repeats an `<!-- Expected values for {{source}} -->` comment in every template — content that could be tightened or moved to references, fitting 'mostly efficient but could be tightened' rather than 'every token earns its place'.	2 / 3
Actionability	Provides fully concrete guidance — exact commands (`gws gmail users messages list`, `hey box imbox --json`), numeric scoring rules ('VIP contact (+3), action required (+3)'), named scripts, and complete copy-paste-ready note templates — matching the 'fully executable; copy-paste ready' anchor.	3 / 3
Workflow Clarity	The Procedure is a clear numbered sequence, but step numbering is broken (two '3.' steps) and for a batch operation validation checkpoints are only implicit (final-report summary, 'flag ambiguous rather than guess') with no explicit verify step; the rubric caps batch operations lacking validation at 2.	2 / 3
Progressive Disclosure	No bundle files exist and the skill is a well-sectioned but monolithic ~460-line file with five templates and the orchestration protocol inline rather than split into one-level-deep reference files, fitting 'content that should be separate is inline'.	2 / 3
	Total	9 / 12 Passed

Description

100%Weight 40%Scale 1-3

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: concrete capabilities, explicit natural-language triggers in multiple languages, and a clear niche. It answers both what the skill does and when to invoke it without verbosity.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Scan and process unread emails', 'Scores by priority (VIP, urgency, deadlines), classifies, saves relevant emails as vault notes, and generates a triage report' — matching the 'lists multiple specific concrete actions' anchor; not level 2 which only names a domain and some actions.	3 / 3
Completeness	Explicitly answers what (scan/score/classify/save/report) and when via the explicit 'Triggers:' trigger guidance, which is equivalent to a 'Use when...' clause and therefore not capped at 2.	3 / 3
Trigger Term Quality	Provides extensive natural phrases users would say — 'check my email', 'what's in my inbox', 'anything urgent in email?', 'email triage' — across six languages, exceeding the 'some relevant keywords' bar of level 2.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (email triage routed into vault notes) with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: gnekt/My-Brain-Is-Full-Crew
Path: skills/email-triage/SKILL.md
Commit: 238ae8c

Reviewed: 23 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.