event-prospecting-pipeline

Find attendees at conferences/events, research their companies, qualify against ICP, and launch outreach

Quality

72%

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/playbooks/event-prospecting-pipeline/SKILL.md

Quality

Content

78%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 tight, well-organized playbook that sequences a multi-step lead-gen pipeline with concrete per-step skills and human checkpoints. Its main gap is the absence of any executable code or automated validation feedback loops, which keeps actionability and workflow clarity at 4 rather than 5.

Suggestions

Add a short copy-paste example or exact command for at least one step (e.g. the Sheets/CSV export) to push actionability toward 5.

Convert the human checkpoints into explicit validate→fix→retry guidance (e.g. what to check after Step 3 and how to re-qualify) to strengthen feedback loops.

Add a verification step between contact-finding (Step 4) and dedup (Step 5) so missing contacts are caught before dedup.

Dimension	Reasoning	Score
Conciseness	Lean, well-structured body with no padding or explanation of concepts Claude already knows; a few lines (Step 7's agentmail.dev parenthetical, the cross-link blockquote) could be trimmed, keeping it just below the fully-lean 5 anchor.	4 / 5
Actionability	Names the exact skill per step and gives executable decision logic (Step 1's URL/topic/location branching) plus concrete export columns; as an instruction-only skill code absence isn't penalized, but there are no copy-paste commands or examples, capping it at 4 rather than 5.	4 / 5
Workflow Clarity	Clear 7-step sequence with explicit human checkpoints after Steps 3 and 6, so the batch/outreach validation cap does not apply; stays at 4 because checkpoints are human review-gates rather than automated validate→fix→retry feedback loops and dedup has no verification step.	4 / 5
Progressive Disclosure	Under 50 lines with no bundle files and no need for external references, yet cleanly organized into When-to-Use, numbered Steps, and Human Checkpoints with a single one-level-deep cross-link — meeting the simple-skill exception for a 5.	5 / 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.

A solid, specific description of an event-prorospecting pipeline that names concrete actions, but it omits any explicit 'Use when' trigger guidance, which caps completeness. Adding a trigger clause would lift the description from good to excellent.

Suggestions

Add an explicit 'Use when...' clause listing natural triggers, e.g. 'Use when finding leads from a conference/event, researching attendee companies, qualifying them against an ICP, or launching outreach.'

Include a couple of common synonyms (e.g. 'lead gen', 'decision-maker contacts') to broaden trigger-term coverage.

Mention the key sub-steps the description currently omits (deduplication, contact finding, export) so the action list is comprehensive.

Dimension	Reasoning	Score
Specificity	Names the event/conference domain and lists four concrete actions ('find attendees', 'research their companies', 'qualify against ICP', 'launch outreach'), matching the 'several specific actions; minor gaps' anchor; not 5 because research/qualify/outreach stay high-level without enrichment depth or contact-finding detail.	4 / 5
Completeness	Clearly answers 'what' with the four-action pipeline but provides no 'Use when...' or equivalent trigger clause, so per the missing-trigger-rule completeness is capped at 3.	3 / 5
Trigger Term Quality	Includes natural phrases a user would say ('attendees at conferences/events', 'research their companies', 'qualify against ICP', 'launch outreach'); not 5 because common synonyms like 'lead gen' or 'decision-maker contacts' are missing and ICP jargon narrows the audience.	4 / 5
Distinctiveness Conflict Risk	The event-attendee→ICP→outreach niche is fairly distinct and unlikely to fire for unrelated skills, but the cross-link to a sibling Luma skill signals minor overlap risk with closely related lead-gen 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/playbooks/event-prospecting-pipeline/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.