samber/dev-event-organizer-skills / skills/event-speaker-cold-outreach
event-speaker-cold-outreach
VerifiedWrite and sequence the cold invitation to a speaker a shortlist already picked - the message, not the search. Covers what a first invitation must disclose up front (event basics, honest budget and travel terms, the answer deadline, how you found them), personalization built from the shortlist's own "why", ranked first-touch channels, follow-up cadences that add a new angle instead of bumping, and the fee conversation where speakers have no rate card. Use whenever the user mentions writing a speaker invitation, pitching a keynote candidate, following up on an unanswered invitation, or a speaker who asks for a fee - even if they never say "outreach". Do NOT use to find or qualify candidates - use samber/dev-event-organizer-skills@event-speaker-sourcing instead.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 28.7 KB |
| evals/evals.json | config | 34.2 KB |
| references/cadence-and-fee-conversation.md | markdown | 9.7 KB |
| references/invitation-message-craft.md | markdown | 7.1 KB |
evals/evals.json
View on GitHub{
"skill_name": "event-speaker-cold-outreach",
"evals": [
{
"id": 1,
"prompt": "I run NordHack Day, a single-track community conference in Tallinn, around 320 attendees, mostly backend and infra people. Top of our shortlist for the 30-minute closing session is Dara Okonjo - she gave a talk at a Kubernetes meetup in Riga last month about why her team deleted their service mesh, and that is exactly the argument our room keeps having in the hallway. We can cover a train ticket and one night in a hotel, nothing else, no fee at all. Event is 12 May and I need to know by 3 March. Write the email.",
"expected_output": "A drafted first invitation of roughly 150 words with a short specific subject line, opening on the Riga talk, stating Tallinn/320/12 May, stating plainly that the event covers train and one night and pays no fee, naming 3 March as the answer date, carrying no links or attachments, and closing with a dated next step - plus an instruction to humanize and review the draft before sending.",
"files": [],
"expectations": [
"The drafted email body runs at roughly 150 words or fewer.",
"The email opens by naming Dara's specific recent work - the Riga meetup talk about deleting their service mesh - rather than complimenting her reputation or standing in the field.",
"That opening line also states how she was found, making the discovery route explicit in the message itself.",
"The email states the event basics: roughly 320 attendees, Tallinn, and the 12 May date.",
"The email states plainly, in this first message, that the event covers a train ticket and one night's lodging and pays no speaker fee - the money is not deferred to a later touch or to a call.",
"The email names 3 March as the date an answer is needed.",
"The email contains no links, no attachments and no images, and the response explains that corporate filters auto-trash mail carrying them so those wait for a later touch.",
"A subject line is supplied, under 50 characters, naming the specific theme or angle rather than a generic 'Speaking invitation' or 'Invitation to speak at NordHack Day' shape.",
"None of these words appears anywhere in the email: revolutionary, disruptive, game-changing, best-in-class, cutting-edge, thought leader, rockstar, ninja, guru.",
"The email makes no superlative claim about the candidate such as 'leading expert', 'the best voice on', or 'one of the top names in'.",
"The email closes with a specific low-friction next step carrying a proposed date, never an open-ended 'let me know if you're interested'.",
"The email frames the value as the audience, the room and the conversation she would get, not as what the program needs from her.",
"The response tells the user to run the draft through a humanizer pass before sending, and to review the draft themselves before it goes out."
]
},
{
"id": 2,
"prompt": "Marcus Vandenberg replied to our invitation for the opening keynote at DeltaConf - community-run, 450 people, Lyon, October - and said his rate for a keynote is EUR 2,500 plus business-class travel. We budgeted zero for speaker fees. We can do economy flights and two nights' lodging. I do not control the budget anyway, our treasurer Ines does, and she is back from leave on Wednesday. What do I write back?",
"expected_output": "A reply that names no market rate, answers from the event's own budget, names Ines as the decider with a committed date to come back, asks what the EUR 2,500 is covering, and offers concessions from a list fixed before the first message - never a counter-offer figure.",
"files": [],
"expectations": [
"The response states or implies no market rate, going rate, industry standard or benchmark for keynote speaker fees.",
"The response explicitly warns against countering with an invented figure, and frames 'I don't have a benchmark for this, here is our budget' as both the honest and the stronger answer.",
"The drafted reply answers from the event's own budget: economy flights and two nights' lodging, and no fee.",
"The response states that the fee decision is not the user's to make, and the drafted reply names Ines as the person who decides.",
"The drafted reply commits to a specific date for coming back to Marcus and commits to answering either way rather than only if the answer is yes.",
"The response warns that an unexplained silence from the organizer's side cools a warm candidate, and that the follow-up cadence has no rung for 'waiting on us'.",
"The response advises asking what the EUR 2,500 is actually covering - travel, preparation time, lost billable days - rather than treating it as a single indivisible fee.",
"The response offers concessions by name from a fixed list, drawing on options such as travel dates, slot length, remote delivery, a co-speaker seat, a companion ticket, recording and publication terms, session time of day, or an introduction to someone in the room.",
"The response states that the concession list is fixed before the first message goes out and that anything not on it is not available, whatever the negotiation does.",
"The response warns against promising anything the user cannot actually deliver.",
"If a real fee were ever agreed, the response routes the payment through whoever handles the event's money and contracts, citing tax, visa, or conflict-of-interest and employment complications rather than the organizer paying a speaker directly.",
"The response keeps the community-run posture explicit: the invitation cannot honestly offer a fee and says so plainly, rather than hinting money might appear later."
]
},
{
"id": 3,
"prompt": "We sent our invitation to Priyanka Rao on the 2nd for a 40-minute slot at ShipIt Berlin. Nothing back and it is now the 11th. Since we wrote, two other speakers confirmed and one of them works on exactly the same problem she does. Our answer deadline is the 25th. What do I send?",
"expected_output": "A follow-up built on the newly confirmed co-speaker as a genuinely new angle, never a bump, inside a capped three-touch sequence, with a close-out message for the final touch and a rule for treating silence past the cap as a no.",
"files": [],
"expectations": [
"The response refuses a bump: no 'just bumping this up', no 'did you see my email', no 'following up on my last message', and no re-sending of the same pitch reformatted.",
"The follow-up is built around a genuinely new angle, specifically the newly confirmed co-speaker working on the same problem.",
"The response identifies a confirmed co-speaker as the strongest angle available among the options.",
"The response names other legitimate angles available for rotation - a program detail that landed since, a specific audience question her work answers, a constraint update, or a narrowed ask - rather than offering only one.",
"The response caps the sequence at three touches in total and stops after the third rather than continuing indefinitely.",
"The response states that a follow-up with nothing new to carry should not be sent at all, and that the gap itself is the message.",
"The response supplies or describes a close-out message for the final touch.",
"The close-out separates 'no to this slot' from 'no to this event' and asks for the reason behind any decline.",
"The close-out carries no guilt, no manufactured deadline pressure, and is not a further touch disguised as a goodbye.",
"The response requires every angle used to be true, and forbids inventing a confirmation or manufacturing urgency to create momentum.",
"The response says that silence past the cap is recorded as a no, the slot is released, and the next candidate is approached.",
"The response warns that a bumped invitation costs the event's reputation in a community whose members talk to each other."
]
},
{
"id": 4,
"prompt": "We have one 45-minute slot left at Cascadia Infra Days - Portland, 6 November, about 500 people - and three ranked candidates for it: Tomas in Barcelona, Wen in Seattle, and Rafi in Bangalore. Today is 3 October. We announce the full program on 20 October. Travel budget is confirmed for exactly one international flight. How do I run this?",
"expected_output": "A per-candidate plan that flags the travel lead-time problem for the two international candidates, names that constraint inside the invitation, forces an explicit sequential-versus-parallel decision with a two-yeses plan, forbids CC and mail-merge, and picks a compressed cadence against the 20 October date.",
"files": [],
"expectations": [
"The response applies a four-to-six-week travel lead-time floor and flags that the 20 October answer date leaves the international candidates inside or under it.",
"The response requires that constraint to be named inside the invitation itself rather than left for the candidate to discover.",
"The response states that an invitation sent under the travel floor without naming the constraint is functionally a request to decline.",
"The response identifies Wen in Seattle as the candidate the travel floor does not bind, and treats that as a reason to weigh her differently.",
"The response forces an explicit decision between approaching the three sequentially and approaching them in parallel, rather than defaulting silently to one.",
"If parallel approaches are chosen, the response requires deciding in advance what happens on two yeses, including where a second yes could honestly be placed.",
"The response forbids CCing two candidates on the same thread and requires one candidate per slot per thread.",
"The response forbids a mail-merge or single templated blast to all three candidates.",
"The response rules out a long-runway cadence for this deadline and picks a compressed sequence instead, explaining that a hard date promotes the faster options.",
"The response weighs the cost of holding the slot open behind an unanswered candidate when choosing between sequential and parallel.",
"The response accounts for only one international flight being funded and keeps the budget line in the invitation honest about that for the two international candidates.",
"The response promises no flight, slot or term the user has not confirmed they control."
]
},
{
"id": 5,
"prompt": "I want Kestrel Mbeki for our security track at Fieldnotes Conf. She lists no email address anywhere I can find. She is very active in the #general channel of her project's Discord and files GitHub issues on that project constantly. One of our program committee members went to university with her but says they have not spoken in years. She does have a contact form on her site and open DMs on her Mastodon profile. How do I reach her?",
"expected_output": "A channel decision that rules out the project's Discord and issue tracker and any guessed address outright, tries the committee member's introduction first, and otherwise writes to a route Kestrel published, with the discovery route stated in the message.",
"files": [],
"expectations": [
"The response rules out contacting her inside the project's Discord or its issue tracker entirely, not as a lower-ranked or last-resort option.",
"The response gives the reason: many community codes of conduct treat recruiting and solicitation in their spaces as off-limits, the breach is public, and it cannot be walked back.",
"The response rules out guessing or scraping a work email address entirely rather than keeping it as a cheap fallback.",
"The response directs the approach to a route Kestrel herself published - her Mastodon DM or her site's contact form.",
"The response treats the committee member's university connection as a possible referrer-relayed introduction and says to exhaust that path first where it exists.",
"The response explains that a referrer-relayed introduction is the cheapest strong option because a vouch arrives attached and nobody is contacted until the candidate answers.",
"The response states that a published profile or directory listing is consent to be found, never consent to be pitched.",
"The response requires the message to state how she was found.",
"The response notes that a DM and an email are the same act in effort and in consent or e-marketing exposure, and that the channel changes the character limit rather than the work.",
"The response ranks a direct email above a published DM on quality of answer, because a DM invites a fast reflexive reply to a request needing a calendar check and often an employer's sign-off.",
"The response does not treat an in-person ask as the default, and if it raises one at all it ties it to a named promotion condition such as a headline slot, an already-unanswered written approach, or an event both will attend before the answer date.",
"The response does not suggest asking the mutual contact to hand over her private email address in place of using a route she published."
]
},
{
"id": 6,
"prompt": "Eight names came out of our shortlist for six slots at Handoff. Third edition, and we fully intend to keep running it every year. Two of the eight are scored Hot, four Warm, two Cold. One of the six slots is our closing keynote and honestly the whole program hangs off it. I am the only person writing these invitations and I have maybe three hours this week. How do I spend them?",
"expected_output": "An effort allocation tiered by score: the recorded shortlist reason as the default depth for everyone, fresh research for the two Hot candidates, and the deepest program-shaped ask reserved for the closing keynote - with the mail-merge blast refused outright.",
"files": [],
"expectations": [
"The response allocates effort by the Hot/Warm/Cold score rather than spreading three hours evenly across the eight candidates.",
"The response makes the reason already recorded on the shortlist the default depth for every candidate, on the grounds that the evidence is already paid for and reusing it costs one sentence.",
"The response promotes both Hot candidates to fresh personalization built on work published since the shortlist was compiled.",
"The response promotes the closing-keynote candidate to the deepest option: an invitation restructured around a talk only that person could give, naming the gap in the program their work fills.",
"The response justifies that promotion by the slot concentrating the program's risk or by it being a keynote, not by the candidate's score alone.",
"The response notes that the event's annual, compounding nature is itself a reason to spend more on the relationship, because a candidate who declines with the relationship intact is next year's first call.",
"The response states that the deepest option is never what an efficiency ordering picks on its own, and that it is promoted only by a named condition.",
"The response warns against sending a generic slot-brief-only invitation to candidates chosen specifically, because it throws away the qualification that put them on the list.",
"The response forbids a merge-field or mail-merge blast to the shortlist outright rather than ranking it last.",
"The response notes that the deeper options mean researching a named individual past what the shortlist recorded, and flags the line between reading someone's public work and assembling a file on them.",
"The response does not claim that the deepest personalization is simply the best choice for every candidate."
]
},
{
"id": 7,
"prompt": "Two things landed on me today. Our platinum sponsor emailed asking us to put their VP of Engineering on the main stage - they have paid EUR 12,000. Separately my co-organizer dropped a name in Slack, 'Jonas Weller, he'd be great for the data track', with no other context at all. Both need invitations from me. We are a volunteer-run community conference. Go.",
"expected_output": "A refusal to treat sponsorship as a purchased speaking slot, a refusal to write an invitation to a bare name, and a list of what a candidate hand-off must carry before any message gets drafted.",
"files": [],
"expectations": [
"The response refuses to treat the platinum sponsorship as buying a speaking slot at a community-run event.",
"The response states that a candidate arriving through a sponsor relationship is invited on the same terms as anyone else, or not at all.",
"The response does not draft a main-stage invitation to the VP on the strength of the sponsorship.",
"The response refuses to write an invitation to Jonas Weller from a bare name with no recorded reason behind it.",
"The response sends the Jonas request back for qualification rather than inventing a reason or writing around the gap.",
"The response states that an invitation unable to answer 'why me, why this event, why now' is a form letter sent to someone chosen specifically.",
"The response names what a candidate hand-off must carry before an invitation can be written: the evidence-backed reason, a fit score, availability and travel constraints, the honest budget line, the published contact route, and which review lane applies.",
"The response does not substitute a compliment about reputation or seniority for the missing evidence.",
"The response keeps the community-run posture explicit and notes the invitation trades on the audience and the peer group rather than on money.",
"The response addresses what to tell the sponsor, and that answer does not include granting stage time in exchange for the sponsorship."
]
},
{
"id": 8,
"prompt": "Good news - Aurelie Fontaine said yes on a call just now for our 25-minute slot at Runtime Days, 14 February in Ghent. On the call she asked for an afternoon slot rather than a morning one because of childcare, and she wants to bring a colleague to co-present. I said yes to both. She also asked whether we record and publish sessions and I said I would check. What now?",
"expected_output": "A same-day written confirmation carrying slot, date, start time, length, format, what is and is not paid, travel and lodging terms with who books what, recording terms, the title/abstract deadline, the review lane, and both agreed conditions - then a handoff to the post-yes speaker care work.",
"files": [],
"expectations": [
"The response requires a written confirmation sent the same day as the yes.",
"The confirmation states the slot, date, start time, length and format.",
"The confirmation states what the event pays and, explicitly, what it does not.",
"The confirmation states travel and lodging terms including who books what.",
"The confirmation resolves and states the recording and publication terms rather than leaving that question open.",
"The confirmation names the deadline for the title and abstract.",
"The confirmation states which review lane the invited proposal goes through rather than leaving it to be guessed.",
"Both conditions agreed on the call - the afternoon slot and the co-presenter seat - are written into the confirmation message.",
"The response states that a condition agreed in a call and absent from the confirmation is a condition nobody agreed.",
"The response checks both conditions against a concession list fixed before the invitation went out, and flags that agreeing on the spot to anything outside that list is the failure to avoid.",
"The response names the real cost of each granted concession - a schedule rebalance, and one extra ticket or a shared slot - rather than treating them as free goodwill.",
"The response hands the confirmed speaker onward to the post-yes briefing, travel and on-site care work rather than continuing to run it here."
]
},
{
"id": 9,
"prompt": "We just finished our second edition of Backbone Summit. Of the 14 speaker invitations we sent, 6 said yes, 3 said no, and 5 never replied at all. My co-chair wants to put a target in our organizer handbook - she found a stat saying good cold outreach converts at 15-20% and thinks we should hold ourselves to that. What should we actually be tracking?",
"expected_output": "A rejection of the imported 15-20% figure, a small set of self-set metrics computed from this event's own numbers, decline-reason capture named as the one metric with a real threshold, and the 5 non-replies recorded as nos with the slots released.",
"files": [],
"expectations": [
"The response rejects importing the 15-20% cold-outreach conversion figure as a target for speaker invitations.",
"The response states that acceptance rate, reply rate and time-to-answer are self-set numbers that only mean something across editions of this same event.",
"The response computes or references the event's own invitation-to-acceptance rate from the 14 sent and 6 accepted, and recommends tracking it per slot type.",
"The response recommends tracking time-to-answer split by channel, and explains that this is what re-ranks the first-touch channel choice for this organizer.",
"The response names decline-reason capture as the metric with a real threshold: every decline carries a recorded reason.",
"The response explains that without recorded decline reasons the next edition's candidate search repeats the mistake that produced them.",
"The response names slot-holding time - days a slot spends behind an unanswered candidate - as a metric worth tracking.",
"The response recommends picking a small number of metrics, around two, and writing down what each one would change next edition, rather than adopting the whole list.",
"The response treats the 5 non-replies as recorded nos with the slots released, not as still pending."
]
}
],
"trigger_queries": [
{
"query": "Write the invitation email to our top keynote candidate - we can cover travel but there is no fee.",
"should_trigger": true
},
{
"query": "How do I word the first message to someone I want on stage at our conference?",
"should_trigger": true
},
{
"query": "Our speaker invite has had no reply for nine days. What do I send next?",
"should_trigger": true
},
{
"query": "A speaker we invited came back asking for EUR 2,000 and we have no fee budget. How do I answer?",
"should_trigger": true
},
{
"query": "We have three people in mind for one slot and six weeks until the program announcement. How do I approach them?",
"should_trigger": true
},
{
"query": "Draft a cold email to a developer I want to keynote our platform day.",
"should_trigger": true
},
{
"query": "What should the subject line be on a speaker invitation?",
"should_trigger": true
},
{
"query": "Is it fine to attach our speaker prospectus to the first email?",
"should_trigger": true
},
{
"query": "Someone turned down our invitation. What do I do with that?",
"should_trigger": true
},
{
"query": "How many times can I follow up with a speaker who has not replied?",
"should_trigger": true
},
{
"query": "I want to DM this person on Mastodon about speaking - is that the right channel?",
"should_trigger": true
},
{
"query": "Our shortlist is done. Now what do I actually say to them?",
"should_trigger": true
},
{
"query": "How much should we offer a keynote as an honorarium?",
"should_trigger": true
},
{
"query": "The person I want has to fly in from Singapore and our event is in five weeks. Is that doable?",
"should_trigger": true
},
{
"query": "Write me a follow-up that is not just 'checking in'.",
"should_trigger": true
},
{
"query": "We have eight names and about two hours to write to all of them. How do I split the effort?",
"should_trigger": true
},
{
"query": "Can I just mail-merge the same invite to the whole shortlist?",
"should_trigger": true
},
{
"query": "A candidate said yes but wants to present remotely. What do I send back?",
"should_trigger": true
},
{
"query": "Should I tell them we have no budget in the first email, or wait until they are interested?",
"should_trigger": true
},
{
"query": "How do I ask someone to speak without it sounding like spam?",
"should_trigger": true
},
{
"query": "Our sponsor gave us a name from their team they would like on stage. How do I handle that invite?",
"should_trigger": true
},
{
"query": "What goes in the confirmation message once a speaker agrees?",
"should_trigger": true
},
{
"query": "I found her address on her GitHub profile. Fine to use?",
"should_trigger": true
},
{
"query": "Help me write to a person whose talk I saw last month and want at our event.",
"should_trigger": true
},
{
"query": "The candidate wants an answer on the fee by Friday and I am not the one who decides. What do I say?",
"should_trigger": true
},
{
"query": "How do I close out a thread with a speaker who has gone quiet, without burning the relationship?",
"should_trigger": true
},
{
"query": "Is it weird to ask them in person at the conference we are both at next month instead of emailing?",
"should_trigger": true
},
{
"query": "Give me a cadence for chasing an unanswered keynote ask.",
"should_trigger": true
},
{
"query": "Two weeks and nothing back on our first email. Any point in a third try?",
"should_trigger": true
},
{
"query": "I want to invite this maintainer but all I know is that they maintain a popular library. Is that enough to write?",
"should_trigger": true
},
{
"query": "What do I do if both people I asked for the same slot say yes?",
"should_trigger": true
},
{
"query": "Should I CC my co-organizer and both candidates on the same thread?",
"should_trigger": true
},
{
"query": "How long should the first email be?",
"should_trigger": true
},
{
"query": "We are a vendor conference with real budget. Does that change how I write the ask?",
"should_trigger": true
},
{
"query": "Rewrite this speaker invite so it does not read like it was generated.",
"should_trigger": true
},
{
"query": "A candidate asked what we pay and we have not confirmed the travel budget yet. What do I tell them?",
"should_trigger": true
},
{
"query": "Which is better for a first approach, email or a LinkedIn message?",
"should_trigger": true
},
{
"query": "Can I post in their project's Discord to ask them to speak?",
"should_trigger": true
},
{
"query": "Our keynote candidate turned us down last year. Worth asking again this edition?",
"should_trigger": true
},
{
"query": "How do I track whether our speaker invitations actually work?",
"should_trigger": true
},
{
"query": "What should I measure about our speaker asks between editions?",
"should_trigger": true
},
{
"query": "She said yes on a call and agreed to a shorter slot. Anything else I need to do?",
"should_trigger": true
},
{
"query": "I need someone on stage in March and I am starting from a ranked list of five names.",
"should_trigger": true
},
{
"query": "What do I absolutely have to say in the first message to a speaker?",
"should_trigger": true
},
{
"query": "We cannot pay a fee. What else can we offer to get a yes?",
"should_trigger": true
},
{
"query": "Is there an industry standard rate for conference keynotes I should be matching?",
"should_trigger": true
},
{
"query": "How do I ask a declining speaker for a referral without being pushy?",
"should_trigger": true
},
{
"query": "Write the ask for our opening slot - the candidate is a first-time speaker we really want.",
"should_trigger": true
},
{
"query": "Help me find speakers for our platform engineering track - where do I even look?",
"should_trigger": false
},
{
"query": "Build me a scoring rubric to rank candidate speakers by fit before we contact any of them.",
"should_trigger": false
},
{
"query": "Our speaker confirmed. What do I send them about A/V needs and travel booking?",
"should_trigger": false
},
{
"query": "Write the pre-event briefing document for our confirmed keynote.",
"should_trigger": false
},
{
"query": "Design the call for papers for our 2027 edition.",
"should_trigger": false
},
{
"query": "What fields should our CFP submission form have?",
"should_trigger": false
},
{
"query": "We got 240 CFP submissions. How do we review them?",
"should_trigger": false
},
{
"query": "Set up blind review for our program committee.",
"should_trigger": false
},
{
"query": "Write the cold email to a sponsor prospect for our Gold tier.",
"should_trigger": false
},
{
"query": "How do I follow up with a sponsor who has not replied to our prospectus?",
"should_trigger": false
},
{
"query": "Build our sponsorship rate card and tier ladder.",
"should_trigger": false
},
{
"query": "Draft the attendee announcement email sequence for our conference.",
"should_trigger": false
},
{
"query": "How many reminder emails should ticket holders get before the event?",
"should_trigger": false
},
{
"query": "Pitch our event to tech journalists for coverage.",
"should_trigger": false
},
{
"query": "Write the press release announcing our conference lineup.",
"should_trigger": false
},
{
"query": "Set up a newsletter swap with another developer conference.",
"should_trigger": false
},
{
"query": "I want to submit a talk proposal to a big infrastructure conference - help me write the abstract.",
"should_trigger": false
},
{
"query": "How do I get accepted as a speaker at more conferences?",
"should_trigger": false
},
{
"query": "Lay our 42 accepted talks into a two-track grid.",
"should_trigger": false
},
{
"query": "How long should sessions be and where do the breaks go?",
"should_trigger": false
},
{
"query": "Who do I invite to the private dinner alongside the conference?",
"should_trigger": false
},
{
"query": "A government minister is attending. What is the escort and protocol plan?",
"should_trigger": false
},
{
"query": "Write our code of conduct and the reporting channel behind it.",
"should_trigger": false
},
{
"query": "How do we handle a harassment report made about a speaker?",
"should_trigger": false
},
{
"query": "Design our expo floor layout so attendees walk past every booth.",
"should_trigger": false
},
{
"query": "How do we match sponsors and buyers for the 1:1 meeting program?",
"should_trigger": false
},
{
"query": "Recruit and roster our volunteers across the two event days.",
"should_trigger": false
},
{
"query": "Write the job description for the conference producer we are hiring.",
"should_trigger": false
},
{
"query": "How do I break into event production as a career?",
"should_trigger": false
},
{
"query": "Which weekend should we run on - three other events are already in March.",
"should_trigger": false
},
{
"query": "Build the budget and break-even model for a 400-person conference.",
"should_trigger": false
},
{
"query": "Should we charge for tickets or run the event free?",
"should_trigger": false
},
{
"query": "Find us a venue for 300 people with two breakout rooms.",
"should_trigger": false
},
{
"query": "Our catering quote is over budget - how do I compare other caterers?",
"should_trigger": false
},
{
"query": "Write our post-event survey and thank-you to attendees.",
"should_trigger": false
},
{
"query": "Run the internal retrospective on the edition we just finished.",
"should_trigger": false
},
{
"query": "How do we turn last year's talk recordings into blog posts and clips?",
"should_trigger": false
},
{
"query": "Plan our social posts for the speaker reveal.",
"should_trigger": false
},
{
"query": "Write the landing page copy for our conference.",
"should_trigger": false
},
{
"query": "We need mentors for our hackathon tracks. How many, and how do we recruit them?",
"should_trigger": false
},
{
"query": "Design the judging rubric for our hackathon.",
"should_trigger": false
},
{
"query": "Write a cold outreach sequence for our SaaS sales team targeting CTOs.",
"should_trigger": false
},
{
"query": "Help me write a LinkedIn connection request to a VP of Engineering.",
"should_trigger": false
},
{
"query": "Draft an outreach email to an influencer for a product collaboration.",
"should_trigger": false
},
{
"query": "How do I recruit a senior Go developer with a cold email?",
"should_trigger": false
},
{
"query": "Our MC needs a script for opening the day.",
"should_trigger": false
},
{
"query": "What do we do about no-shows - should we overbook registrations?",
"should_trigger": false
},
{
"query": "How do we decide between a hybrid and a fully in-person event?",
"should_trigger": false
}
]
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |