CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

networking-email-drafter

Draft professional follow-up emails to contacts made at conferences - not too pushy, but memorable.

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Academic Writing/networking-email-drafter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The operational core — usage command, parameters, workflow, and error handling — is sound and concrete, but it is buried in roughly 150 lines of generic audit/process boilerplate, and the actual email-drafting guidance is too thin to execute without the script. Trimming boilerplate and adding one worked example email would raise quality on every dimension.

Suggestions

Cut or relocate the boilerplate sections (Key Features, Dependencies, Evaluation Criteria, Security Checklist, Lifecycle Status, Output Requirements, Response Template) into references/ or drop them; consolidate the three duplicated py_compile snippets into one.

Add one complete worked example (sample command plus the resulting draft email with subject line and follow-up timeline) so the 'not too pushy, but memorable' tone is concrete rather than asserted.

Expand 'Email Components' from bare labels into 1-2 sentences each of concrete guidance (e.g. how to phrase a soft ask, what makes a good context reminder), or point to a reference file with that guidance.

DimensionReasoningScore

Conciseness

The body is noticeably verbose: generic boilerplate sections ("Key Features", "Dependencies" noting versions are 'not explicitly version-pinned', "Evaluation Criteria" with 'Standard input → Expected output', "Security Checklist", "Lifecycle Status", "Output Requirements", "Response Template") pad the file, and the py_compile check command is repeated across three sections. It avoids explaining concepts Claude already knows, which keeps it above the severely-verbose anchor, but the several padded sections clearly match the level-2 anchor.

2 / 5

Actionability

There is concrete executable guidance — `python scripts/main.py --contact "Dr. Smith" --topic "CRISPR research" --conference "ASGCT 2024"`, a documented parameter list, and a quick-check command — but the core email-crafting guidance is incomplete: 'Email Components' is five bare bullet labels ('Professional greeting', 'Soft ask') with no example email and no concrete guidance on what 'not too pushy, but memorable' means in practice. This lands on the some-concrete-guidance-but-incomplete anchor.

3 / 5

Workflow Clarity

The 5-step Workflow is clearly sequenced with an explicit early checkpoint (validate the request matches scope and stop early) and a documented fallback path in Error Handling, plus the py_compile Quick Check as an executable validation. It is not a 5 because the steps describe generic skill-invocation process rather than email-drafting-specific feedback loops, but the checkpoints and fallback put it above anchor 3.

4 / 5

Progressive Disclosure

Bundle files exist and the single reference is clearly signaled one level deep ('[references/audit-reference.md]'), but roughly 60 lines of audit, security, evaluation, and lifecycle boilerplate that belongs in the reference file (or nowhere) are inlined in SKILL.md, and audit-reference.md partially duplicates the SKILL.md audit commands. This matches the structure-present-but-inline-content-should-be-separate anchor rather than the well-split anchor 4.

3 / 5

Total

12

/

20

Passed

Description

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

The description communicates a clear, genuinely specific purpose with natural trigger phrasing, but it omits any "Use when..." clause and only lightly enumerates capabilities. Adding explicit trigger conditions and a few synonyms would lift it substantially.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when the user mentions meeting someone at a conference, exchanging business cards, or wanting to follow up with a new professional contact.'

Enumerate 1-2 more concrete actions or outputs (e.g. 'generate subject line options and a suggested follow-up timeline') to strengthen specificity.

Include common synonyms such as 'networking email' or 'thank-you note' so natural user phrasings beyond 'follow-up email' also trigger the skill.

DimensionReasoningScore

Specificity

The description names a specific domain ("follow-up emails to contacts made at conferences") and one concrete action ("Draft professional follow-up emails"), but stops there — no subject lines, tone options, or follow-up timing. This matches the anchor for naming a domain with 1-2 concrete actions without comprehensive coverage, and falls short of the several-specific-actions anchor above.

3 / 5

Completeness

The "what" is clear (draft professional follow-up emails for conference contacts), but there is no "Use when..." clause or equivalent explicit trigger guidance — the rubric caps completeness at 3 in that case. It is not a 4 because the "when" is entirely absent rather than present-but-imprecise.

3 / 5

Trigger Term Quality

"follow-up emails", "contacts", and "conferences" are natural phrases a user would say when they need this skill, but common variations like "networking", "reach out", or "thank-you note" are absent. This sits at the some-relevant-keywords-but-missing-synonyms anchor rather than the good-coverage anchor.

3 / 5

Distinctiveness Conflict Risk

The conference-follow-up niche ("follow-up emails to contacts made at conferences") is mostly distinct, with only minor overlap risk against a generic email-drafting skill. It is not a 5 because it lacks the crisp multi-trigger phrasing of the clear-niche example.

4 / 5

Total

13

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Academic Writing/networking-email-drafter/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.