email-finder-hunter

Email finder and verifier - find emails, verify deliverability, discover companies

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/lead-generation/capabilities/email-finder-hunter/SKILL.md

Quality

Content

82%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 body is a well-organized, highly actionable API catalog with executable curl examples for every endpoint and a clear setup sequence with a credential fallback. Minor conciseness gains are available by deduping the capability descriptions, and the all-inline structure is acceptable for a single-purpose API skill.

Suggestions

Remove the 'Capabilities' bullet list or the per-section intro lines to eliminate the duplicated capability descriptions.

Consider extracting the full per-endpoint parameter tables into a references/ file so SKILL.md stays a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean curl examples with parameter lists and little concept explanation, but the 'Capabilities' bullet list duplicates each section's intro line, a minor redundancy that could be trimmed.	4 / 5
Actionability	Every capability ships with a complete, copy-paste-ready curl command using real endpoint paths, auth headers, and sample parameters, fully covering the common cases.	5 / 5
Workflow Clarity	Setup is sequenced with an explicit credential-existence check and a fallback ('tell the user to run npx gooseworks login'), and per-endpoint usage is unambiguous; only minor validation gaps remain for a read-only API.	4 / 5
Progressive Disclosure	Content is well-sectioned per capability with a 'Discover More' block signaling where deeper endpoint detail lives; no nested references, though all endpoint examples are inlined with no separate reference file.	4 / 5
	Total	17 / 20 Passed

Description

66%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 specific and distinguishable, naming concrete email actions users would naturally say, but it lacks any explicit 'when to use' trigger guidance and undersells the skill's full capability set. Adding a 'Use when...' clause would raise completeness and trigger discoverability.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user needs to find, verify, or enrich email addresses and company domains.'

Expand the action list to cover the skill's other capabilities (e.g. domain search, email/person/company enrichment, email count) for fuller coverage.

Include common synonyms like 'email lookup', 'email validation', and 'deliverability check' to improve trigger-term match rate.

Dimension	Reasoning	Score
Specificity	Lists three concrete actions — 'find emails, verify deliverability, discover companies' — matching the several-specific-actions anchor, though it omits several of the skill's actual capabilities (enrichment, domain search, company enrichment).	4 / 5
Completeness	The 'what' is clear (email finder and verifier with three actions) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Natural user phrases like 'find emails', 'verify deliverability', and 'email finder and verifier' give good coverage, but common synonyms such as 'email lookup', 'email search', and 'email validation' are missing.	4 / 5
Distinctiveness Conflict Risk	'Email finder and verifier' carves a clear email-intelligence niche with distinct triggers, with only minor overlap risk against broader contact or sales-enrichment skills.	4 / 5
	Total	15 / 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: gooseworks-ai/goose-skills
Path: skills/lead-generation/capabilities/email-finder-hunter/SKILL.md
Commit: 2523432

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