agentleFS
guerrilla2799guerrilla2799/event-and-scale-os/skills/conference-activation/SKILL.md

conference-activation

Skill2 starsChanged 3 months agoMITView on GitHub

Use for any conference you are sponsoring or attending, or when the user says "work the conference", "booth strategy", "what do we do at the show", "trade show plan", "we're going to [conference]", "private suite". Turns a conference into pre-booked meetings: booth against suite, staffing, the hallway motion, and what to do in the last hour. Writes workspace/events/<event>/activation-plan.md.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After a sponsorship is signed, or after deciding to attend without sponsoring

    line 12
  2. Distinctive:

    Read the agenda before you arrive and assign sessions:

    line 51
  3. Distinctive:

    Keep 20 to 30% of calendars open for same-day booking

    line 60
  4. Distinctive:

    If the conference is the reason a cluster of target accounts is in one city, the side event is frequently worth more than the sponsorship.

    line 69

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Conference Activation

Somebody else's event, your pipeline. The plan for turning attendance into meetings, whether or not you paid for a stand.

When to use

  • After a sponsorship is signed, or after deciding to attend without sponsoring
  • Planning a private suite or hospitality alongside a conference
  • A conference is next month and there is no plan

Inputs

  • Reads: workspace/events/<event>/contract.md, workspace/events/<event>/meetings.csv, workspace/events/<event>/budget.md
  • Needs from user: who is going and for how long, the agenda, what the sponsorship includes, and whether a side event is happening

Workflow

1. Decide the physical footprint

Three options, and the most expensive one is frequently the worst.

OptionCostBest for
Stand or boothHighestShows where the floor is genuinely the venue for conversation, and where the package included stage and seats
Private suite or nearby roomModerateHour-long conversations with named accounts and customers. Frequently better value than a booth
No footprintLowestMost events, most of the time. Two people, pre-booked meetings, the hallway

The suite option is under-used. A hotel suite or a private room near the venue, with pre-booked hour-long conversations and the offer to cover a customer's room, produces deeper conversations than any booth. It is also where the customer-facing team should invite their own accounts, since an invitation from an account manager outperforms one from marketing.

2. If there is a stand, get the reality first

From sponsorship-negotiation: literal dimensions, height cap, what is supplied, and what is charged extra. A "premium exhibition stand" is frequently a table-sized footprint with a table, two chairs, power, and wifi. That is a banner and a table throw, not a build, and treating it as a build wastes thousands.

What actually earns its place on a small stand:

  • A banner readable from twenty feet with one sentence on it, not a feature list
  • A screen with a silent, looping, captioned demo or animation
  • Something that gives people a reason to stop that is not a raffle
  • One piece of collateral worth taking, and a way to capture a name

Booth position selection frequently opens on a fixed date with tier priority. Put it in the calendar and take the slot.

3. Staff it properly

  • Never leave the stand unstaffed, and never staff it with everyone at once
  • Two-hour shifts. Attention degrades badly after that
  • Nobody sits down. Nobody eats at the stand. Nobody stands in a group talking to each other, which is the single most common failure and it makes the stand unapproachable
  • The rest of the team is in meetings or in the hallway

4. Work the agenda

Read the agenda before you arrive and assign sessions:

  • Sessions where your target accounts are speaking. Attend, listen, and reference it afterward. That is the best conversation opener at any conference
  • Sessions in your category, for competitive intelligence and the questions the room asks
  • Networking blocks, which are meetings by another name

5. Run the hallway

Most conference value is unstructured. Make it slightly less unstructured:

  • Each person carries their target list on their phone
  • A shared channel for real-time sightings: "X from Y is at the coffee station"
  • Keep 20 to 30% of calendars open for same-day booking
  • Same-day notes on every conversation

6. Do not pack up early

The final hour, when the drinks come out, is the highest-quality hour of the day. The senior people who were in sessions all day finally walk the floor, and most sponsors are breaking down their stands. Stay. Print return labels in advance so breakdown takes ten minutes when it does happen.

7. Plan the side event

A dinner the night before or the evening of compounds everything. Guests arrive already knowing you, and a stage appearance the next morning becomes something they show up for. Run it with executive-dinner.

If the conference is the reason a cluster of target accounts is in one city, the side event is frequently worth more than the sponsorship.

8. Capture the attendee list

Post-event you usually receive the contacts of everyone you scanned, and frequently a full attendee list with company, name, and title but no emails. That second list is an enrichment job the next morning, not a dead end. Route it into the target list so the next event starts warmer.

Output

  • Writes: workspace/events/<event>/activation-plan.md with the footprint decision, stand plan, staffing rota, agenda assignments, hallway protocol, and the side event
  • Prints: the footprint recommendation with reasoning, the staffing rota, the session assignments, and the pre-booked meeting position

Rules & quality bar

  • Get literal booth dimensions before designing anything
  • The stand is never unstaffed and never crowded with your own people
  • Two-hour shifts. Nobody sits, nobody eats at the stand
  • 20 to 30% of calendars stay open
  • Nobody packs up early
  • Same-day notes on every conversation
  • The attendee list gets enriched, not filed
  • A suite is considered seriously every time. It frequently beats a booth on cost and depth

Related skills

  • Reads: sponsorship-negotiation, meeting-engine
  • Pairs with: executive-dinner (the side event), speaking-and-stage, staffing-and-briefing
  • See also: docs/operations-runbook.md sections 7 and 8

Download now (ZIP)

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.