CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

email-concierge

Local AI email assistant that automates unread-mail processing, offline-safe classification and reply drafting, local draft editing/approval queues, calendar conflict checks, voice transcription, and confirmed SMTP sending when connectivity returns. Use when the user wants to manage email, check inbox, draft or edit replies, queue messages offline, approve/send email, handle meeting invites, or mentions email assistant, IMAP, SMTP, voice memo, local AI email.

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 highly actionable, well-gated operational guide whose workflows and safety confirmations are concrete and executable. Its weaknesses are repetition that inflates token cost and a monolithic single-file structure that inlines installation, configuration, and troubleshooting detail instead of splitting them into referenced files.

Suggestions

Deduplicate the body: state SKILL_DIR resolution once, merge the repeated reinstall-preservation notes, and consolidate the overlapping commands in Tools Reference and Workflow Examples into a single command reference — this alone would cut noticeable tokens (conciseness).

Move the multi-platform installation details, PortAudio per-distro commands, and the troubleshooting table into a references/ file (e.g. INSTALL.md and TROUBLESHOOTING.md) linked from short sections, keeping SKILL.md as an overview (progressive_disclosure).

Use the venv interpreter consistently in every example (venv/bin/python vs venv\Scripts\python.exe) so commands are copy-paste ready on all platforms, matching the skill's own troubleshooting guidance (actionability).

DimensionReasoningScore

Conciseness

The body is information-dense but noticeably redundant: SKILL_DIR resolution is stated twice ("Resolve SKILL_DIR from the loaded SKILL.md; never assume a Windows path" and "Resolve this SKILL.md directory as SKILL_DIR"), reinstall-preservation of config/state is repeated in the install section, and tool commands (--inbox, --check-cal, --record, --transcribe) appear in both the Tools Reference and Workflow Examples sections. This matches "mostly efficient but includes some unnecessary explanation or could be tightened" rather than the minor-trim level-4 anchor.

3 / 5

Actionability

Nearly all guidance is executable with exact per-platform commands (setup, diagnose, inbox, queue/edit/approve/send, calendar, voice), matching "mostly executable guidance with concrete code or commands and minor gaps". It falls short of 5 because Tools Reference and Workflow Examples use bare `python email_concierge.py` while the skill itself mandates the venv interpreter ("Use venv\Scripts\python.exe directly, not python"), so several examples are not copy-paste ready on Windows.

4 / 5

Workflow Clarity

The sequence is clear and risky operations are gated: setup → "Run --diagnose --json after setup" → --inbox → inspect queue → --approve → "--send --confirm-send", satisfying the validation requirement for batch/sending workflows. It stays at 4 rather than 5 because there is no explicit inspect-the-queue checkpoint woven into the workflow narrative (the user is told to "inspect and approve drafts first" only in passing) and error-recovery loops live in the Troubleshooting table rather than in the workflow itself.

4 / 5

Progressive Disclosure

The single ~280-line SKILL.md inlines substantial content that clearly belongs in separate files — multi-platform installer instructions, the PortAudio per-distro commands, the configuration/env-var reference, the transcription setup, and the troubleshooting table — with no reference files at all (no references/, scripts/, or assets/ directories exist). Good section headers provide structure, so this matches "some structure but content that should be separate is inline" rather than the header-less level-2 anchor.

3 / 5

Total

14

/

20

Passed

Description

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

An exemplary description: concrete capability list in third person, explicit 'Use when' triggers with natural keywords, and a distinct local-AI/offline niche. Only minor trigger-synonym gaps keep trigger term quality from the top anchor.

DimensionReasoningScore

Specificity

"automates unread-mail processing, offline-safe classification and reply drafting, local draft editing/approval queues, calendar conflict checks, voice transcription, and confirmed SMTP sending when connectivity returns" lists multiple specific concrete actions with comprehensive coverage of the skill's capabilities, matching the level-5 anchor; it is not the level-4 anchor because there are no meaningful coverage gaps.

5 / 5

Completeness

The first sentence explicitly answers 'what' (six concrete capabilities including offline behavior) and the second explicitly answers 'when' with an explicit "Use when the user wants to..." clause listing concrete trigger phrases, matching the level-5 anchor; it does not fall to 4 because both what and when are fully explicit.

5 / 5

Trigger Term Quality

"manage email, check inbox, draft or edit replies, queue messages offline, approve/send email, handle meeting invites, or mentions email assistant, IMAP, SMTP, voice memo, local AI email" gives good keyword coverage with synonym pairs (draft/edit, approve/send), but a few natural user phrasings are missing (e.g. "compose a reply", "unread emails", "backlog") and phrases like "queue messages offline" are less natural, so it sits between the 4 and 5 anchors rather than clearly at 5.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (local, offline-first email assistant) with distinct technical triggers ("IMAP, SMTP, voice memo, local AI email") and a privacy/local-inference framing, giving minimal conflict risk with unrelated skills; it does not fall to 4 because generic terms like "manage email" are anchored by the domain-specific qualifiers around them.

5 / 5

Total

19

/

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

anbeime/skill

Path

skills/email-concierge/SKILL.md

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.