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
66%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./skills/lead-generation/capabilities/luma-event-attendees/SKILL.mdLow
Low-risk findings.
2 low severity findings. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
In `scripts/scrape_event.py` the AI agent supplies free-text via `--search`, which is passed into `LumaApifyClient.search_events()` and then used to run the Apify actor (`lexis-solutions/lu-ma-scraper`) that returns `featured_guests`/bios that the workflow parses and exports.
W012: Unverifiable external dependency detected (runtime URL that controls agent).
What this means
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
Why it was flagged
The code invokes a remote Apify actor at runtime via the Apify API endpoints (e.g., "https://api.apify.com/v2" and optionally the proxy "https://api.gooseworks.ai"), which causes remote code (the lexis-solutions/lu-ma-scraper actor) to execute and is required for the --search mode.
- Repository
- gooseworks-ai/goose-skills
- Commit
8866b2a
- Audited
- Security analysis
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.