agentleFS
Sign inStart free
latour-ailatour-ai/skills/conference-attendee-screen/SKILL.md

conference-attendee-screen

Skill69 starsChanged 26 days agoNo licenceView on GitHub

Screen a deal conference's attendee or delegate list — sector summits, sponsor-lender events, industry trade shows — against a firm's live investment themes and CRM. Enriches each attendee company from public sources (what it actually does, revenue or headcount signals, ownership status, recent transaction news), scores it against the themes as strong fit, adjacent, or no fit with a one-line reason, and cross-references CRM history so the team knows who it already covers, who owns each relationship, and who is genuinely new. Output is a tiered meeting target list capped at a workable number, a draft outreach note per tier-1 name that references something specific about the business, and an explicit no-fit list with reasons so the same names never get re-screened. For PE and private credit origination teams, business development, and deal professionals working a conference for deal flow. Trigger on phrases like "screen this attendee list," "who should we meet at [conference]," "run the delegate list against our themes," "conference target list," "who's worth meeting here," "sort this exhibitor list," or when a user uploads an attendee list alongside investment themes. Do NOT use for preparing an LP or fundraising conference schedule — use the conference-prep-planner skill. Do NOT use for a deep brief on one individual before a meeting — use the professional-profile-brief skill. Attendee lists and CRM exports are confidential; assume a firm-approved AI environment.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free