company-contact-finder

Find decision-makers at a specific company using Apollo, Crustdata, Fiber, and PDL people search via Gooseworks MCP. Given a company name and target titles, returns a list of contacts with name, title, LinkedIn URL, and location.

Quality

73%

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/company-contact-finder/SKILL.md

Quality

Content

88%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.

A well-structured, highly actionable skill body with a clear layered-fallback workflow, explicit validation checkpoints, and concrete executable tool calls; its main weakness is mild redundancy (cost info repeated) and inline reference material that could be split out.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient and assumes Claude's competence, but per-provider cost figures appear twice (inline in each step and again in the 'Cost Comparison' table), which is minor redundancy that could be trimmed.	4 / 5
Actionability	Provides fully executable, copy-paste-ready MCP tool calls with concrete parameters (e.g., apollo_person_search with person_titles, organization_domains, per_page), plus worked examples and an explicit output JSON schema covering the common cases.	5 / 5
Workflow Clarity	Steps 1–7 are explicitly sequenced with decision checkpoints at every fallback ('If 3+ quality matches: skip to Step 7; If fewer: proceed to Step 4') and a validation step (Step 3 quality checks, dedup by LinkedIn URL), satisfying the feedback-loop requirement for batch/paid operations.	5 / 5
Progressive Disclosure	Content is well-organized into clearly signaled sections (Inputs, Procedure, Tools Reference, Examples, Troubleshooting, Metadata) with no nested references, but the ~290-line body inlines reference-style material (full tool reference, examples) that could be split into separate files.	4 / 5
	Total	18 / 20 Passed

Description

58%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.

A specific, well-scoped description that clearly states what the skill does and which providers it uses, but it lacks an explicit 'Use when...' trigger clause, which caps its completeness and weakens trigger guidance.

Suggestions

Add an explicit trigger clause such as 'Use when the user asks to find decision-makers, executives, or contacts at a specific company.'

Include natural user phrasings and synonyms (e.g., 'find leads at', 'who works at', 'executives at') to broaden trigger coverage.

Mention the output shape briefly as a trigger cue (e.g., 'returns a contact list with name, title, and LinkedIn URL').

Dimension	Reasoning	Score
Specificity	Names concrete actions ('Find decision-makers at a specific company') plus the specific providers (Apollo, Crustdata, Fiber, PDL) and explicit output fields (name, title, LinkedIn URL, location), though the action set is essentially one task with named tools rather than multiple distinct actions.	4 / 5
Completeness	The 'what' is clearly stated (find decision-makers, return contacts with named fields), but there is no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes relevant natural terms ('decision-makers at a specific company', 'people search', 'contacts', 'target titles'), but misses common user phrasings like 'find leads at X' or 'who works at X' and synonyms a user might actually say.	3 / 5
Distinctiveness Conflict Risk	The niche is clear — finding decision-makers at a named company via specific MCP providers — making it largely distinct from other skills, with only minor overlap risk against generic lead-generation or enrichment 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: gooseworks-ai/goose-skills
Path: skills/lead-generation/capabilities/company-contact-finder/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.