CtrlK
BlogDocsLog inGet started
Tessl Logo

luma-event-attendees

Find speakers, hosts, and guest profiles at conferences and events on Luma. Two modes - free direct scrape for hosts, or Apify-powered search for full guest profiles with LinkedIn/Twitter/bio.

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/lead-generation/capabilities/luma-event-attendees/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

Highly actionable with executable commands and a clear step-by-step agent workflow, but it is somewhat repetitive, lacks validation checkpoints for batch exports, and keeps reference-grade material inline rather than splitting it into separate files.

Suggestions

Add a validation/checkpoint step for batch exports (e.g., verify the CSV row count and required columns before proceeding to the ICP-qualification step), raising workflow clarity.

Move the full options reference, output column schema, and troubleshooting into a one-level-deep reference file (e.g., references/REFERENCE.md) signaled from a concise overview.

De-duplicate the near-identical command examples between the "Two Modes" and "Usage" sections to tighten conciseness.

DimensionReasoningScore

Conciseness

Mostly efficient with executable commands and little concept-overexplaining, but the "Two Modes" and "Usage" sections repeat near-identical examples and the $29/month cost is stated multiple times, so it could be tightened.

2 / 3

Actionability

Provides fully executable, copy-paste-ready commands throughout, a concrete options reference, and an explicit output column schema — matching the fully-executable anchor.

3 / 3

Workflow Clarity

The AI Agent Workflow is clearly sequenced (Steps 1–5), but batch CSV/JSON export operations lack explicit validation or error-recovery checkpoints, which caps workflow clarity at 2 per the feedback-loops note.

2 / 3

Progressive Disclosure

Bundle scripts (scripts/scrape_event.py) are real and clearly signaled, but the ~236-line SKILL.md inlines reference-grade content (full options table, output schema, troubleshooting, example prompts) that would be better split into one-level-deep reference files.

2 / 3

Total

9

/

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.

A specific, capability-rich description with a clear niche, but it omits an explicit "Use when..." trigger clause and natural attendee-listing phrasings, capping completeness and trigger quality at 2.

Suggestions

Add an explicit 'Use when...' trigger clause naming the situations a user would voice (e.g., 'Use when the user wants to find speakers, hosts, or attendees at a Luma event for outreach prospecting').

Include natural trigger terms users actually say, such as 'event attendees', 'who's going to an event', or 'guest list', alongside the existing keywords.

Keep the two-mode breakdown but ensure the trigger clause applies to both free-scrape and Apify-search use cases.

DimensionReasoningScore

Specificity

Names multiple concrete actions — "Find speakers, hosts, and guest profiles", "direct scrape for hosts", and "Apify-powered search for full guest profiles with LinkedIn/Twitter/bio" — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Clearly answers "what" with concrete capabilities and two modes, but "when to use it" is only implied with no explicit "Use when..." trigger clause, which caps completeness at 2 per the guidelines.

2 / 3

Trigger Term Quality

Has relevant natural terms ("speakers, hosts, guest profiles", "conferences and events", "Luma", "LinkedIn/Twitter/bio") but omits common variations a user would naturally say (e.g., "find attendees", "who's going to an event", "event guest list").

2 / 3

Distinctiveness Conflict Risk

The Luma-event guest-profile niche with its specific data-targets is clearly distinguishable and unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

12

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.