email-finder-tomba

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

Quality

69%

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

72%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 skill is highly actionable — every endpoint has an executable, realistic curl example — and free of padding. Its weaknesses are example/parameter mismatches in Domain Search and Find Phone, and a large inlined API reference that has no bundled reference file to split into.

Suggestions

Fix the Domain Search example to include the documented required `company` and pagination/filter params, and reconcile Find Phone's example with its listed parameters (email/domain/linkedin/full).

Move the per-endpoint curl reference into a references/ file (e.g. ENDPOINTS.md) and keep SKILL.md as a concise overview pointing to it, improving progressive disclosure.

Remove the stray duplicated summary line (line 23) and the trailing "List all endpoints" text appended mid-curl (line 344) for tighter conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with no concept over-explanation; each endpoint is a terse description plus an executable curl. Minor redundancy from the verbatim curl-header boilerplate repeated across 20 sections and a stray duplicated summary line (line 23).	4 / 5
Actionability	Every capability ships a complete, copy-paste-ready curl command with auth headers, real endpoint paths, and realistic example payloads, plus per-endpoint parameter lists — fully executable across the common cases.	5 / 5
Workflow Clarity	Setup → Capabilities → Usage → Use Cases → Discover More is a coherent sequence, but the Domain Search example omits its documented required `company*` and filter params, and Find Phone's example uses `first_name`/`last_name` which are not listed as parameters — concrete gaps that undermine the workflow.	3 / 5
Progressive Disclosure	Sections are well-organized with clear headers and a one-level "Discover More" pointer, but ~350 lines of per-endpoint API reference are inlined in a single SKILL.md with no bundle files to offload the bulk, matching the "API reference that could be in a separate file" anchor.	3 / 5
	Total	15 / 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 concise, action-oriented, and clearly distinct, naming concrete sources a user would naturally mention. Its main weakness is the absence of an explicit "Use when..." trigger clause, which leaves the "when to use" half of completeness implicit.

Suggestions

Add an explicit trigger clause, e.g. "Use when finding or verifying contact emails from a domain, LinkedIn profile, or company name."

Include common synonyms to improve trigger matching (e.g. "verify email", "email address", "B2B leads").

Dimension	Reasoning	Score
Specificity	"find emails from domains, LinkedIn, or company search" names multiple concrete actions (find, verify) across three distinct input sources, but "company search" is slightly generic and it omits breadth like enrichment/phone lookup.	4 / 5
Completeness	The "what" is clear (find and verify emails from domains/LinkedIn/company search), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Natural terms users would say are present ("emails", "domains", "LinkedIn", "company search"), but synonyms like "verify email", "email address", or "B2B leads" are missing.	4 / 5
Distinctiveness Conflict Risk	"Email finder and verifier" with Tomba-specific sources (domains, LinkedIn, company search) carves a distinct niche with only minor overlap risk against generic contact/CRM 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-tomba/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.