email-finder-tomba

Email finder and verifier - find emails from domains, LinkedIn, or company search

Quality

61%

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-tomba/SKILL.md

Quality

Content

65%

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 ready-to-run curl examples for every endpoint, but it is a monolithic, repetitive catalog lacking response-validation guidance and any split-out reference structure. Factoring shared boilerplate and moving the endpoint reference behind a navigation pointer would improve it.

Suggestions

Factor the repeated curl headers/base URL into a single documented template and show only the differing path/query per endpoint to cut repetition.

Add a brief error-handling note (check HTTP status / response errors, retry on rate limits) for batch email-finding and verification operations.

Move the per-endpoint reference into a separate reference file (or lean on the existing /search and /details endpoints) and keep SKILL.md as a concise overview with a capabilities index.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining concepts Claude already knows, but repeats the full curl boilerplate (headers, base URL, api field) across all twenty endpoints instead of factoring it into a shared template, so it could be tightened.	2 / 3
Actionability	Each capability ships a complete, copy-paste-ready curl command with real example values (stripe.com, john@stripe.com) and documented typed parameters, which is fully executable guidance.	3 / 3
Workflow Clarity	The setup sequence (read credentials, export vars, fall back to login) is clear, but there are no validation checkpoints or error-handling guidance for API responses, and batch email operations warrant feedback loops that are absent.	2 / 3
Progressive Disclosure	The ~340-line endpoint catalog lives entirely inline in SKILL.md with no reference files, and while the 'Discover More' section offers a dynamic lookup, the bulk reference material that should be split out is not.	2 / 3
	Total	9 / 12 Passed

Description

57%

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 conveys a clear, distinctive purpose with natural trigger terms, but it only hints at the full capability set and omits explicit 'when to use' guidance. Adding a 'Use when...' clause and a few more action terms would raise it.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user needs to find, verify, or enrich email addresses from a domain, LinkedIn profile, or company name.'

Broaden trigger terms to include natural variations like 'email address', 'contact info', 'B2B leads', and 'verify email deliverability'.

Mention a couple more concrete actions (e.g. enrich, verify deliverability, find phone numbers) to improve specificity beyond just 'find' and 'verify'.

Dimension	Reasoning	Score
Specificity	Quotes 'find emails' and 'verifier' name concrete actions across input sources (domains, LinkedIn, company search), but only cover two of the skill's roughly twenty capabilities, so it is not comprehensive.	2 / 3
Completeness	It states what the skill does ('Email finder and verifier - find emails from domains, LinkedIn, or company search') but lacks any 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 2.	2 / 3
Trigger Term Quality	'find emails', 'domains', 'LinkedIn', and 'company search' are natural terms a user might say, but common variations like 'email address', 'contact info', 'B2B leads', or 'verify email deliverability' are missing.	2 / 3
Distinctiveness Conflict Risk	The email-finding/verification niche with domain, LinkedIn, and company-search triggers is clearly distinct and unlikely to collide with unrelated skills.	3 / 3
	Total	9 / 12 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-tomba/SKILL.md
Commit: 8866b2a

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