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."

68

Quality

84%

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

68%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 content is a well-structured, mostly actionable pipeline with good code examples and organization. Its main weakness is the absence of explicit validation/verification checkpoints across a batch pipeline that writes to external services.

Suggestions

Add explicit validation checkpoints between steps (e.g., verify CSV row count after dedup, confirm qualification result count equals attendee count before writing to Sheets) with a fix-and-retry path.

Trim the Cost Estimate and Example Prompts sections or move them to a separate reference file to improve token efficiency.

Make the Task-tool qualification block fully executable — specify the exact subagent invocation and JSON input format rather than schematic 'Task: ...' placeholders.

DimensionReasoningScore

Conciseness

The body is largely efficient with executable code and tables, but the Cost Estimate table, Example Prompts, and a few explanatory asides ('writing large datasets to Sheets mid-process is slow and error-prone') could be trimmed; it is noticeably above the midpoint but not fully lean.

4 / 5

Actionability

Provides concrete, mostly copy-paste-ready bash and python snippets, a specific CSV column table, named tools (Rube MCP, luma-event-attendees), and a CSV fallback; minor gaps remain in the Task-qualification block which is partly schematic.

4 / 5

Workflow Clarity

The 5-step sequence is clear with upfront clarifying questions, parallel execution, and merge/dedup steps, but this batch/external pipeline lacks explicit validation checkpoints or validate→fix→retry feedback loops, capping it per the batch-operations rule.

3 / 5

Progressive Disclosure

No bundle files are present; the single SKILL.md is well-organized with clear section headers and clearly signaled references to external skills, keeping content one level deep with easy navigation.

4 / 5

Total

15

/

20

Passed

Description

100%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 comprehensive and well-structured, naming concrete pipeline actions and providing explicit, natural-language trigger phrases. It cleanly answers both what the skill does and when to use it.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — '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' — giving comprehensive coverage of the pipeline.

5 / 5

Completeness

Explicitly answers both what (the full search→extract→qualify→Sheet→Slack pipeline) and when ('Use this skill whenever someone wants to find qualified leads from events ... Also triggers for ...'), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user phrases and synonyms — 'find qualified leads from events', 'prospect event attendees', 'find people at events and qualify them', "who's attending X events that matches our ICP" — covering the realistic ways a user would phrase this need.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Luma event-based lead generation) with distinct, specific triggers that are unlikely to collide with unrelated skills.

5 / 5

Total

20

/

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.

Validation15 / 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.