comprehensive-enrichment

Enrich any person or company from any identifier — email, name, LinkedIn URL, domain, company name, Twitter/X handle. Use when asked to enrich, look up, or research a lead, contact, person, or company.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/lead-generation/capabilities/comprehensive-enrichment/SKILL.md

Quality

Content

50%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 thorough, well-sectioned API reference with concrete examples, but is held back by malformed JSON payloads that break executability and the absence of validation checkpoints for a batch operation. It is also monolithic, with Section 4 duplicating earlier content.

Suggestions

Fix the curl examples whose -d JSON bodies are missing the opening brace (Fiber name+company, Sixtyfour enrich-lead, find-phone, scrapegraph, exa, linkup) so every snippet is copy-paste executable.

Add validation/verification checkpoints (e.g., confirm API responses parsed, retry/handle empty results, consensus-check email verification) to lift workflow clarity above 3 for this batch operation.

Remove or compress the verbatim duplication in Section 4 by pointing back to Sections 2-3 with only the end-to-end ordering highlighted, improving token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly efficient reference-style content without padding Claude already knows, but Section 4 re-states nearly the entire API surface from Sections 2-3 verbatim, adding noticeable length that could be tightened.	3 / 5
Actionability	Concrete curl commands are provided throughout, but a meaningful share have malformed JSON bodies (missing opening brace in the name+company Fiber, Sixtyfour enrich-lead, find-phone, scrapegraph, exa, and linkup examples), so they are not copy-paste executable as written.	3 / 5
Workflow Clarity	The detect→person→company→compile→format sequence is clear, but this multi-API batch operation has no validation/verification checkpoints or error-recovery feedback loops, which caps it at 3.	3 / 5
Progressive Disclosure	Well-organized into numbered sections, but the content is monolithic in a single file with no bundle files or external references; the full API catalog and output templates that could live separately are inlined.	3 / 5
	Total	12 / 20 Passed

Description

92%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 concrete, trigger-rich, and explicitly answers both what and when with third-person voice. It is one of the stronger descriptions, with only minor synonym coverage gaps.

Dimension	Reasoning	Score
Specificity	Names multiple specific concrete inputs ("email, name, LinkedIn URL, domain, company name, Twitter/X handle") for the enrichment action, giving comprehensive coverage of identifier types.	5 / 5
Completeness	Explicitly answers what ("Enrich any person or company from any identifier") and when ("Use when asked to enrich, look up, or research a lead, contact, person, or company") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural phrasing ("enrich, look up, or research a lead, contact, person, or company") users would actually say; a few synonyms like "find info on" are absent, keeping it just short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	Clear niche (lead/contact enrichment) with distinct triggers and identifier list, minimal overlap risk with unrelated skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (543 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: gooseworks-ai/goose-skills
Path: skills/lead-generation/capabilities/comprehensive-enrichment/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.