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

Securityby

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

Quality

Content

60%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 content is actionable and well-referenced with real bundle files and executable commands, but is notably verbose and padded with redundant, generic process sections that dilute the actual email-drafting guidance.

Suggestions

Consolidate the redundant process sections (When to Use, Implementation Details, Workflow, Output Requirements, Error Handling, Input Validation, Response Template) into a single concise workflow; remove 'See ## X above' filler.

Cut generic statements Claude already knows (e.g. about reproducible outputs, assumptions, bounded scope) and keep only email-drafting-specific guidance.

Lead with the concrete usage example and Email Components near the top so the core skill surface is immediately visible.

Dimension	Reasoning	Score
Conciseness	The body spans ~25 sections with noticeable padding and redundancy — restated descriptions, generic process prose Claude already knows, and filler cross-references like 'See ## Prerequisites above' — placing it noticeably below the midpoint.	2 / 5
Actionability	Concrete executable commands ('python -m py_compile scripts/main.py', 'python scripts/main.py --help') and a copy-paste usage example with real arguments are present, with only minor gaps in coverage.	4 / 5
Workflow Clarity	The 5-step Workflow has a stop-early validation checkpoint and an explicit fallback on failure; as a non-destructive single-purpose skill it is not subject to the batch/destructive cap, with only minor validation gaps.	4 / 5
Progressive Disclosure	Both bundle paths referenced in the body (scripts/main.py and references/audit-reference.md) are real, one-level-deep, and clearly signaled, giving good structure with minor organization gaps.	4 / 5
	Total	14 / 20 Passed

Description

61%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 is clear and reasonably specific about the task, but lacks an explicit 'when to use' trigger clause and comprehensive capability coverage. It is distinct as a niche but could be more trigger-rich.

Suggestions

Add an explicit 'Use when...' clause naming trigger phrases users would say, e.g. 'Use when following up with conference contacts, sending networking or thank-you emails after meeting someone.'

Expand the action list beyond 'Draft' (e.g. 'Draft, tailor tone, and suggest subject lines and follow-up timing for networking emails').

Include common synonyms like 'networking email', 'reach out', and 'thank-you note' to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('follow-up emails to contacts made at conferences') and one concrete action ('Draft') but offers no comprehensive list of capabilities, fitting the '1-2 concrete actions' anchor.	3 / 5
Completeness	A clear 'what' is present but there is no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Natural phrases like 'follow-up emails', 'contacts', and 'conferences' appear, but common synonyms such as 'networking', 'reach out', or 'thank-you email' are missing, so it is above the midpoint but not comprehensive.	4 / 5
Distinctiveness Conflict Risk	The conference-follow-up niche with the 'not too pushy, but memorable' framing is mostly distinct with only minor overlap risk against general email-drafting skills.	4 / 5
	Total	14 / 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
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
Commit: 63c61d3

Reviewed: 13 hours 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.