CtrlK
BlogDocsLog inGet started
Tessl Logo

email-ops

邮件操作技能。代替用户起草并发送邮件。

55

Quality

63%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/email-ops/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

The body is highly actionable with a clear sequenced workflow, explicit validation checkpoints, and concrete send-command and per-type prompt templates, but it carries some repeated boilerplate and a large inline template library that could be offloaded to reference files.

Suggestions

Move the six full email-type prompt templates into a reference file (e.g. references/prompts.md) and keep SKILL.md as an overview pointing to them, improving progressive disclosure.

Dedupe the shared format/return-format boilerplate across the per-type templates by stating it once and referencing it, to tighten conciseness.

Consider adding a brief one-line example output per template type so the expected result format is unambiguous without repeating the full boilerplate.

DimensionReasoningScore

Conciseness

The body is dense and avoids over-explaining concepts Claude knows, but the six per-type prompt templates repeat boilerplate (format/return-format blocks) that could be tightened, matching the mostly-efficient anchor.

2 / 3

Actionability

It provides copy-paste-ready guidance: a concrete `email-ops --to ... --subject ... --body ...` command and complete LLM prompt templates with explicit field placeholders and return formats for all six email types, matching the fully-executable anchor.

3 / 3

Workflow Clarity

A clear six-step sequence is given with explicit validation (Sent-folder confirmation), an error-handling table, a default-don't-send guardrail, and feedback for verification failure, matching the anchor for clear sequence with explicit validation and error-recovery loops.

3 / 3

Progressive Disclosure

The one script (scripts/send_email.py) is referenced cleanly one level deep via the PATH wrapper, but the six substantial inline prompt templates are content that arguably belongs in separate reference files, which do not exist, matching the anchor where inline content should be split out.

2 / 3

Total

10

/

12

Passed

Description

50%

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 is concise and uses correct third-person voice, but it only states what the skill does without an explicit 'when to use' trigger clause or broad natural trigger terms, capping most dimensions at 2.

Suggestions

Add an explicit 'Use when...' clause listing natural trigger situations (e.g. use when the user asks to draft, send, reply to, or follow up on emails).

Broaden trigger-term coverage to include common phrasings users would actually say such as '帮我发邮件', '回复邮件', '跟进', and '写封邮件给'.

Expand the capability list slightly (e.g. drafting different email types, follow-ups, meeting confirmations) to lift specificity toward the multi-action anchor.

DimensionReasoningScore

Specificity

It names the email domain and two concrete actions ("起草并发送邮件") but does not list multiple specific operations, matching the anchor that names a domain with some actions.

2 / 3

Completeness

It states what the skill does ("代替用户起草并发送邮件") but provides no 'Use when...' or equivalent explicit trigger clause; per the guidelines a missing trigger clause caps completeness at 2.

2 / 3

Trigger Term Quality

It includes relevant terms ("邮件操作", "起草...邮件", "发送邮件") but lacks common natural variations users would say (e.g. "帮我发邮件", "回复", "跟进"), matching the anchor for some keywords with missing variations.

2 / 3

Distinctiveness Conflict Risk

The email-ops niche is identifiable and unlikely to conflict with most skills, but the terse description and generic email trigger surface could overlap with other communication skills, matching the somewhat-specific anchor.

2 / 3

Total

8

/

12

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

description_field

'description' is very short (19 chars), consider making it more detailed

Warning

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

13

/

16

Passed

Repository
TeamWiseFlow/xiaobei
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.