event-prospecting-pipeline

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

Quality

83%

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

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is an exemplar orchestration playbook: concise, with concrete skill-routing logic, an explicit output schema, and well-placed human checkpoints. It appropriately delegates detail to specialized sub-skills rather than duplicating it inline.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-structured with no padding or explanation of concepts Claude already knows; every section earns its place, matching the 3 anchor.	3 / 3
Actionability	Concrete per-input routing ("If user provides a Luma event URL... use luma-event-attendees") and an explicit output column schema give specific, executable guidance; absence of inline code is appropriate for an orchestration playbook that delegates to named skills.	3 / 3
Workflow Clarity	A clearly sequenced 7-step pipeline with explicit human validation checkpoints after Steps 3 and 6; the batch-outreach cap does not apply because verification gates are present.	3 / 3
Progressive Disclosure	A well-organized composite overview that points one level deep to clearly signaled specialized skills ("Skill:" labels) rather than inlining their detail; no bundle files are needed for a playbook of this size.	3 / 3
	Total	12 / 12 Passed

Description

67%

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 specific and occupies a clear niche, but it omits explicit "Use when" trigger guidance and leans on jargon ("ICP") while missing common user terms like "leads". Adding a trigger clause and natural synonyms would raise completeness and trigger quality.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user wants leads or prospects from a conference, event, or attendee list."

Replace or augment "qualify against ICP" with plain terms (e.g., "score leads against a target customer profile") and add common variations like "leads", "prospects", and "decision-maker contacts".

Keep third-person imperative voice (already correct) while folding in the trigger guidance to satisfy completeness at level 3.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Find attendees at conferences/events", "research their companies", "qualify against ICP", and "launch outreach" — matching the multi-action 3 anchor.	3 / 3
Completeness	It clearly answers what the skill does but lacks any "Use when..." trigger clause, so per the guideline completeness is capped at 2.	2 / 3
Trigger Term Quality	Natural terms like "attendees", "conferences/events", and "outreach" are present, but "qualify against ICP" is jargon and common variations such as "leads", "prospects", or "contacts" are missing.	2 / 3
Distinctiveness Conflict Risk	The event-attendee prospecting plus ICP qualification plus outreach niche is distinct with specific triggers unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 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/playbooks/event-prospecting-pipeline/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.