CtrlK
BlogDocsLog inGet started
Tessl Logo

get-qualified-leads-from-luma

End-to-end lead prospecting from Luma events. Searches Luma for events by topic and location, extracts all attendees/hosts, qualifies them against a qualification prompt, outputs results to a Google Sheet, and sends a Slack alert with top leads. Use this skill whenever someone wants to find qualified leads from events, prospect event attendees, or run an event-based lead gen workflow. Also triggers for "find people at events and qualify them" or "who's attending X events that matches our ICP."

66

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

63%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-sequenced, highly actionable pipeline guide with concrete commands, code, fallbacks, and per-stage reporting. Its weaknesses are token efficiency (duplicated intro and stale time-sensitive pricing) and a monolithic single-file layout where troubleshooting, cost, and template sections would be better as one-level-deep reference files, plus a missing validation loop on subagent qualification output.

Suggestions

Remove the opening paragraph that repeats the frontmatter description verbatim, and move the Cost Estimate table (with its time-sensitive $29/mo and per-lead pricing) into a references/ file or drop it, since stale pricing erodes trust and wastes tokens.

Split detachable sections — Slack message template, Example Prompts, and Troubleshooting — into clearly signaled one-level-deep files under references/ so SKILL.md stays a lean pipeline overview.

Add an explicit validation step after merging parallel qualification batches: check each subagent result parses as the expected JSON array of {id, name, qualified, confidence, reasoning}, and re-run or manually complete any missing/malformed batch before sorting and saving.

DimensionReasoningScore

Conciseness

The opening paragraph repeats the frontmatter description nearly verbatim, and the Cost Estimate table embeds time-sensitive pricing ("$29/mo flat subscription", "~$0.03 per 100 leads") that will go stale and is not placed in a deprecated/old-patterns section. Mostly efficient procedural content, but these are more than minor trims, fitting the 3 anchor rather than 4.

3 / 5

Actionability

Concrete executable bash commands with exact script paths and output files, a runnable urllib.request webhook snippet, an explicit CSV column schema, batch sizes of 15-20, 50-row chunked writes, and a CSV fallback. The Task-tool block and Slack payload are templates with placeholder slots ([Topic], "For each lead:"), keeping it just below fully copy-paste ready.

4 / 5

Workflow Clarity

Clear Step 0-5 sequence with real checkpoints: timeframe filtering, dedup with None-name handling, per-stage user reports, chunk-fail retry, and a Sheets-to-CSV fallback. Validation exists for the batch sheet writes so the batch-operation cap is not triggered, but the parallel subagent qualification batches have no validation of malformed or missing JSON results, which keeps it below the 5 anchor.

4 / 5

Progressive Disclosure

No bundle files exist and the entire ~215-line skill lives inline. Section headers are good, but clearly detachable content (Cost Estimate, the Slack message template, Example Prompts, Troubleshooting) is inlined rather than split into references/, fitting the 3 anchor "content that should be separate is inline"; not 2 because the structure and cross-skill pointers are otherwise clear and well-organized.

3 / 5

Total

14

/

20

Passed

Description

96%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 strong description: concrete, comprehensive action list in third person, an explicit "Use this skill whenever..." trigger clause with natural quoted phrasings users would say, and a clearly framed Luma-event lead-gen niche. The only weakness is minor trigger overlap with the sibling skills it chains.

DimensionReasoningScore

Specificity

"Searches Luma for events by topic and location, extracts all attendees/hosts, qualifies them against a qualification prompt, outputs results to a Google Sheet, and sends a Slack alert with top leads" lists five concrete actions covering the full pipeline comprehensively, matching the top anchor; coverage has no real gaps, so it is not a 4.

5 / 5

Completeness

Explicitly answers both what (the five-action pipeline) and when ("Use this skill whenever someone wants to find qualified leads from events... Also triggers for...") with concrete trigger phrases, matching the top anchor exactly; not a 4 because the when-clause is fully explicit rather than improvable.

5 / 5

Trigger Term Quality

Includes both natural trigger phrasings users would actually say ("find qualified leads from events", "prospect event attendees", "event-based lead gen workflow") and quoted natural-language variants ("find people at events and qualify them", "who's attending X events that matches our ICP"), giving comprehensive synonym coverage; a 4 would lack those natural variants, which this does not.

5 / 5

Distinctiveness Conflict Risk

The "Luma events" lead-gen niche is distinctive, but triggers like "prospect event attendees" and "qualify them" overlap with the closely related luma-event-attendees and lead-qualification skills it orchestrates, fitting the "mostly distinct; minor overlap risk with closely related skills" anchor rather than the minimal-conflict 5.

4 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
gooseworks-ai/goose-skills
Reviewed

Table of Contents

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.