agentleFS
Tom-BabbTom-Babb/ai-marketing-skills-with-by-tom-babb/skills/conference-vetting/SKILL.md

conference-vetting

Skill30 starsChanged 4 months agoNo licenceView on GitHub

Research and vet inbound conference, summit, expo, awards, and event outreach — a desk check that establishes whether the event is real, an audience check against who you actually sell to, a dossier of the findings, the questions to send the organizer, and a read on their reply. Use this skill whenever someone forwards, pastes, or screenshots a conference invitation, a sponsorship or exhibitor prospectus, a speaking invitation, an awards nomination, or a booth or partnership pitch, and whenever the user asks "is this conference legit", "should we sponsor this", "have you heard of this event", "is this worth our time", "who runs this", or wants an event checked out before replying. Also use it when an organizer's reply to those questions comes back and needs grading. Trigger even when the user shares only a URL or an organizer's name with no framing, and even when they sound like they've already decided — the research is the point.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    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 372,429 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.