samber/dev-event-organizer-skills / skills/event-marketing-plan
event-marketing-plan
VerifiedBuild the attendee-acquisition plan for a technical event - audience segments mapped to channels, the campaign-calendar spine (a ticketed event's percent-of-ticket-sales ladder or a free event's percent-of-attendance-goal curve), campaign moments pinned to pricing and program dates fixed elsewhere, budget allocated across the channel mix, funnel targets per phase, and each channel routed to the sibling that executes it. Use whenever asked to plan how to fill an event, run a ticket-sales or registration campaign, choose promotion channels, split promotion budget, or set registration targets by date. Do NOT use for the email copy itself - use samber/dev-event-organizer-skills@event-attendee-email-sequences - or ticket prices - use samber/dev-event-organizer-skills@event-ticket-pricing.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 27.4 KB |
| evals/evals.json | config | 31.1 KB |
| references/calendar-spines-and-phase-targets.md | markdown | 10.6 KB |
| references/channel-menu-and-budget-allocation.md | markdown | 9.8 KB |
evals/evals.json
View on GitHub{
"skill_name": "event-marketing-plan",
"evals": [
{
"id": 1,
"prompt": "We're organizing StreamStack Conf, a paid two-day data-engineering conference in Rotterdam this October - it's currently March. We expect 450 attendees total. Our sponsor packages include 30 tickets across sponsors, we have 12 speakers, 8 organizers, 15 volunteers, and we set aside 10 scholarship passes; all of those get in free. Tickets go on sale May 5, early-bird pricing ends June 15, speakers are announced July 10, and the full agenda is published August 20. Build the marketing calendar with registration targets for each date so we know if we're on track.",
"expected_output": "A ticketed-spine campaign calendar with checkpoint targets computed against 375 net-of-comps expected sales, pinned to the named marketing moments and worked backward from doors.",
"files": [],
"expectations": [
"Targets are computed against 375 expected sales (450 minus 75 comps), never against the gross 450.",
"The 75 comps subtracted cover the sponsor, speaker, organizer, volunteer and scholarship tickets named in the prompt.",
"The plan uses the ticketed spine (percent of expected ticket sales at named marketing moments), not a percent-of-attendance-goal curve.",
"The early-bird close (June 15) checkpoint is set at roughly 15% of net expected sales, approximately 55-60 tickets.",
"The speaker announcement adds roughly another 10%, putting the cumulative target near 90-95 tickets (~25%).",
"The one-month-out checkpoint is 40-50% of the 375 net target, roughly 150-190 tickets.",
"A final-two-weeks surge is described as the normal shape of the curve, not a red flag.",
"Checkpoints sit on the named marketing moments (announcement, early-bird close, speaker announcement, agenda release), not at evenly-spaced calendar intervals or on a straight line.",
"The calendar is worked backward from doors, with marketing off and running by roughly T-7 months.",
"The first sales week is checked for the presence of any real spike, with its absence named as the earliest warning that no audience exists.",
"The June 15 early-bird date is treated as a fixed input the calendar reacts to; the plan never moves or proposes moving it.",
"No free-event mechanic is applied: no 30-50% drop-off multiplier and no 200% over-registration target appears.",
"Each checkpoint carries a pre-decided response to a miss, chosen before launch."
]
},
{
"id": 2,
"prompt": "Our student hackathon BitBloom runs on campus in 11 weeks and it's free to attend. We want 600 hackers in the building. Registration opens next Monday. How many signups do we need at each point between now and the event, and when should we close registration? We're an MLH member event if that matters.",
"expected_output": "A free-event registration curve at fixed calendar offsets, targeting 100% of the 600 goal two weeks out and 200% one week out, with registration closing one week before the event.",
"files": [],
"expectations": [
"The target line is expressed as percent of the attendance goal at fixed calendar offsets (2 weeks, 1 week), not as percent of ticket sales at marketing moments.",
"The signup target deliberately exceeds 100% of the goal, framed as absorbing no-shows rather than as a stretch target.",
"The signup-to-attendance drop-off is stated as the 30-50% range, not as a single figure.",
"100% of the attendance goal (about 600 signups) is targeted two weeks before the event.",
"200% of the goal (about 1,200 signups) is targeted one week before the event.",
"Registration close is set at one week before the event, tied to the partner-event requirement (pre-event email preparation and a bad-actor check).",
"The one-week registration close is flagged as hackathon-specific rather than generalized into a conference rule.",
"The risk being managed is named as no-shows, not under-selling.",
"No ticketed-conference checkpoint (15% at early-bird close, 40-50% one month out) is applied to this free event.",
"Checkpoints are converted into absolute signup counts attached to dates, not left as ratios.",
"Intermediate milestones before the two-week mark (around the two-month and one-month points) are included, not just the final two checkpoints."
]
},
{
"id": 3,
"prompt": "PulseConf, our paid observability conference, is four weeks out. We budgeted for 380 paid tickets and we've sold 104. The team WhatsApp is in meltdown - half of us want to cancel the third track and drop prices 40%, the other half says the market just doesn't want this event. What's your read?",
"expected_output": "A diagnosis placing 27% in the execution-shortfall band, checking communication causes and reach signals before any demand conclusion, price cut, or ad spend.",
"files": [],
"expectations": [
"The position is computed as roughly 27% of expected sales and compared against the one-month checkpoint.",
"40-50% of expected sales at one month out is named as the on-track band.",
"27% is placed in the 25-30% band characteristic of a team that skipped or delayed its visibility push - an execution shortfall, not a demand verdict.",
"The response refuses to conclude weak demand from the checkpoint number alone, noting that execution and demand shortfalls have opposite fixes.",
"It checks whether the 380 figure is net of comps (sponsor, speaker, organizer, volunteer tickets) before trusting the percentage.",
"It checks whether program or speaker announcements ran later than planned.",
"It checks whether the theme is narrow enough to exclude part of the intended audience.",
"It checks whether the messaging ever actually said who is welcome, named as a funnel problem rather than a vague promote-more diagnosis.",
"Reach signals (registration-page traffic, email opens, partner referrals) are used to discriminate execution shortfall from demand shortfall.",
"Healthy reach with low conversion is routed to the price or the registration page, not answered with more reach.",
"Healthy reach and healthy conversion is named as a genuine demand read belonging to the demand-fit diagnosis and the event's own scope-downgrade decision, not to a bigger campaign.",
"The 40% price cut and track cancellation are not endorsed as a first response before the diagnosis.",
"Paid ads are not recommended as a reflex response to the miss.",
"The final-two-weeks surge is noted as still ahead and a normal part of the curve."
]
},
{
"id": 4,
"prompt": "We run FerroConf, a volunteer community Rust conference - five organizers, all nights-and-weekends. After sponsorship we have 3,000 EUR left we could put toward promotion. My cofounder found a marketing budget template that says 30-40% paid ads, 20-30% content, 10-20% events/sponsorships, 10-15% tools, 5-10% testing. Should we just apply that?",
"expected_output": "A rejection of the full-spread template for this community event, with the percentages labeled as borrowed SaaS conventions, and a barter-only plus fixed-test-budget allocation gated behind checkpoints.",
"files": [],
"expectations": [
"The percentage split is explicitly labeled as a B2B/B2C SaaS marketing convention, not an event-industry standard or benchmark.",
"The full-spread posture is recommended against for this volunteer community-run event.",
"The full spread is identified as fitting a company-run event with a standing marketing budget line and someone whose actual job is reporting on it.",
"Barter-only plus a fixed test budget is recommended as the default posture.",
"No cash is allocated to partner swaps, because that channel trades in reciprocal visibility rather than money.",
"The fixed test is one capped amount, on one paid channel, answering one question decided in advance.",
"The test carries a tracked link decided before launch.",
"The bulk of the money is held behind a decision point (released against a checkpoint), not committed in week one.",
"A concentrated bet is gated on a checkpoint miss combined with an existing tracked referral signal; a miss alone is named as a reason to diagnose, not to spend.",
"Owned channels (mailing list, comms hub, social) are costed in organizer hours, not cash.",
"The plan states it assumes the community-run pole before allocating anything.",
"The full spread and concentrated bet are noted to trigger finance or treasurer sign-off, while a capped test budget clears under one organizer's own discretion."
]
},
{
"id": 5,
"prompt": "First edition of ShipItDay, a free one-day developer event in a single university city, aimed at students and junior devs at the three local schools. We have zero mailing list, a social account with 40 followers, and six volunteers. Which promotion channels should we actually put our hours into?",
"expected_output": "A channel ranking re-ranked for this organizer, promoting local and campus engagement to the top, with campus-specific tactics, a comms hub, list building as a compounding asset, and no lead role for paid ads or social.",
"files": [],
"expectations": [
"Local and campus engagement is promoted to the top of the channel ranking despite being the highest-effort channel.",
"The promotion is justified by the conditions present: a first edition with no list to mail, and a geographically concentrated (single-city, campus) audience.",
"The nonexistent mailing list is not ranked as the primary immediate channel; list building is started as a compounding asset alongside the campaign.",
"The event's own social presence is kept low-weight, on the grounds that community events struggle to reach people since audiences dispersed from Twitter.",
"Named campus tactics appear: in-class pitches, tabling, or flyering.",
"Outreach extends beyond the home campus, applying the rule of inviting at least 3 schools within 6 hours, without overlooking community colleges.",
"Paid ads, if included at all, are a capped test rather than the lead channel, and any cheap-and-effective claim for them is scoped to campus audiences.",
"A comms hub (one page centralizing every channel, shareable by QR code) is included as a one-time build that converts reach rather than creating it.",
"School contacts and local business or professional networks are tracked as two separate referrer pools, not one undifferentiated local list.",
"Each channel is tied to the named segment it is bought for.",
"The ranking is presented as a default re-ranked for this organizer's context, not as a fixed law.",
"A second-order campus tactic appears: inviting student groups to run a workshop or volunteer so their own members self-market the event, or professors sharing with classes."
]
},
{
"id": 6,
"prompt": "For APIcon our early-bird price ends Friday May 30 - the pricing team set that months ago - but our speaker announcement slipped to June 12 and the campaign would clearly land better if early-bird ran through June 20. Please update the marketing calendar with the extended early-bird, and while you're in there, draft the early-bird reminder email and two weeks of LinkedIn posts to go with it.",
"expected_output": "A refusal to move the pricing-owned early-bird date or to write the sibling channels' content, with the campaign planned around May 30 and the email and social work routed out with weight, phase and dates.",
"files": [],
"expectations": [
"The response refuses to extend or move the May 30 early-bird date inside the marketing plan.",
"It explains the cutoff is owned by the pricing decision: moving it changes the price ladder and revenue, and the pricing checkpoint no longer measures what it did.",
"If the date genuinely must move, the decision is routed back to the pricing owner rather than absorbed into the marketing plan.",
"The campaign is planned around May 30 as a fixed date, with the reminder push timed before it.",
"The response declines to draft the reminder email copy itself.",
"Email execution is routed to the sibling that writes attendee email sequences, handing over weight, phase and send dates.",
"The response declines to build the two weeks of LinkedIn posts or a social content calendar.",
"Social execution is routed to the sibling that owns the event's social presence, with its weight, phase and dates handed over.",
"The early-bird close is identified as a sales-spike moment carrying the roughly-15% checkpoint on the ladder.",
"The slipped speaker announcement is flagged as a communication cause to check when reading the next checkpoint, since late announcements are an execution risk."
]
},
{
"id": 7,
"prompt": "We announced TerraForge Summit twelve days ago: 58 registrations in the first four days, then eight in the last week. Marketing is 'clearly broken' according to our sponsor, who wants us to put 1,500 EUR into LinkedIn ads today. Two partner newsletters and a university club are posting about us next week. We also realized we don't know where the 66 came from - we're adding a 'how did you hear about us' dropdown to the registration form this week so we'll know going forward. Thoughts?",
"expected_output": "A read of the launch spike as reach rather than demand, a refusal of the reflex ad spend, and an attribution fix built on per-channel tracked links with the self-reported dropdown demoted to a cross-check.",
"files": [],
"expectations": [
"The launch spike is read as measuring reach, not demand.",
"The post-announcement quiet is named the normal shape of the curve, not a failure signal.",
"Week two is identified as when the campaign pattern becomes readable.",
"The 1,500 EUR LinkedIn ad spend is not endorsed as the response to a soft first fortnight.",
"Paid ads are gated on an owned channel first showing a tracked referral signal worth amplifying, never as the first move against a soft start.",
"Per-channel tracked links or registration codes are named as something decided before launch that cannot be added retroactively, which is why the existing 66 registrations are unattributable.",
"The 'how did you hear about us' field is flagged as undercounting owned channels and double-counting whatever the registrant saw last.",
"Self-reported source is allowed only as a cross-check against tracked links, never as primary attribution.",
"Distinct tracked links or codes per channel are recommended now, before the partner pushes land.",
"The partner newsletters and the university club each get their own code rather than one shared partner-channel code, so each community's conversion stays legible.",
"Progress is measured against the chosen spine's checkpoint line, not against day-over-day counts.",
"What each tracked signal would trigger is written down before the pushes launch; a miss alone triggers diagnosis, not spend."
]
},
{
"id": 8,
"prompt": "TinkerNight is a 150-seat community electronics evening; we charge 12 EUR mostly so people actually show up, and the room genuinely cannot hold more than 150. We have no promotion money at all - literally zero. Registration opens in six weeks. Should we track sales percentages like a conference or over-book like a free meetup, and what's our fallback if numbers look bad halfway - a small ad buy?",
"expected_output": "One spine chosen by the feared failure and run as the only target line, the other demoted to a sanity check, the spending postures deleted outright, and the ad-buy fallback refused.",
"files": [],
"expectations": [
"The two spines are not blended or averaged into a hybrid target.",
"The spine is picked by the failure that would actually hurt this event - empty seats versus unsold seats - reasoning from the nominal fee and the hard capacity cap.",
"Exactly one spine is run as the plan's only target line.",
"The other spine's checkpoint is used only as a secondary sanity check that never enters a target or a go/no-go decision.",
"The two denominators are named as different things: an attendance goal versus expected sales net of comps.",
"With zero cash, the three spending postures are deleted from the menu rather than parked at the bottom.",
"Barter-only is presented as the entire posture menu for this event.",
"The ad-buy fallback is refused: a rung nobody can fund does not reappear as a plan B the first time a checkpoint misses.",
"A halfway miss is answered with diagnosis (reach versus conversion signals) and re-weighting of owned and barter channels, not with spending.",
"The free-event figures (200% over-registration, 30-50% drop-off) are not carried as-is onto this nominal-fee event; its no-show rate is treated as its own, smaller, self-set figure.",
"Checkpoint miss responses are decided before launch, not improvised at the halfway point."
]
},
{
"id": 9,
"prompt": "Second edition of ConduitConf coming up. Last year we sold 210 tickets and kept the full week-by-week sales curve in a spreadsheet. Our registration form had a checkbox for 'interested but can't make it this year' - 143 people ticked it - and we also have a 3,800-address list assembled from last year's attendees, a partner meetup's export they shared with us, and business cards collected at our booth. Announcement is in three weeks and we want to email everything we have on day one. Also, our new headline sponsor gets a 60-ticket allocation this year - how should we read the first weeks of sales?",
"expected_output": "A consent-gated mailing plan that re-contacts the not-available segment, targets set against the event's own prior curve via the pace index, sponsor comps excluded from the target, and the edition's plan recorded for the next one.",
"files": [],
"expectations": [
"Mailing the assembled 3,800-address list is flagged as a consent exposure: addresses without a documented opt-in (the partner export, the booth business cards) can force a deletion the event cannot undo.",
"Emailing everything on day one is not endorsed; sends are restricted to addresses with documented opt-in.",
"The 143 'can't make it this year' respondents are re-contacted at this edition's announcement with an are-you-free-now ask.",
"That segment is named as one other channels never reach.",
"Last year's own week-by-week curve is overlaid as the primary target line, with the published checkpoint ladder as the fallback, because an event's own prior curve beats any published ladder.",
"The pace index is defined as tickets-to-date divided by curve-expected, times 100.",
"Above 100 is read as running hot and below 100 as a gap with a size and a deadline attached.",
"The sponsor's 60-ticket allocation is excluded from the sales target, since comp tickets never had to be sold.",
"An early above-the-line reading is checked for a comp-inflated or batch-release artifact before any budget moves on it.",
"Email frequency is kept limited and the content informative, to maintain list engagement.",
"The plan records for the next edition: the spine chosen, the net-of-comps target, channel weights with their segments, the fixed dates, the budget posture, and planned-versus-actual at each checkpoint."
]
}
],
"trigger_queries": [
{ "query": "Build the marketing plan for our 400-person DevOps conference in October - channels, calendar, targets.", "should_trigger": true },
{ "query": "Our free hackathon needs 500 attendees and registration opens in three months. How many signups do we need by when?", "should_trigger": true },
{ "query": "We're a month out and at 28% of expected ticket sales - did we under-market or is demand just not there?", "should_trigger": true },
{ "query": "We have 2,000 EUR for promotion and a volunteer team of four. Where should the money go?", "should_trigger": true },
{ "query": "How do I fill a 300-seat tech conference?", "should_trigger": true },
{ "query": "Which channels should we use to promote the first conference edition of our developer meetup?", "should_trigger": true },
{ "query": "Help me plan the ticket sales campaign for our community Kubernetes conference.", "should_trigger": true },
{ "query": "Set registration targets by date for our AI summit.", "should_trigger": true },
{ "query": "What percentage of tickets should be sold by the time early-bird closes?", "should_trigger": true },
{ "query": "When should conference marketing start relative to the event date?", "should_trigger": true },
{ "query": "How do I split our event promotion budget between ads, partners and content?", "should_trigger": true },
{ "query": "Our conference announcement went out, sales spiked, then died - is the campaign failing?", "should_trigger": true },
{ "query": "Draft an attendee acquisition plan for a two-day data engineering conference.", "should_trigger": true },
{ "query": "How many hackathon signups do we need to actually get 600 people in the room?", "should_trigger": true },
{ "query": "Plan the campaign calendar around our CFP close, speaker announcement and early-bird dates.", "should_trigger": true },
{ "query": "Should our student hackathon overbook registrations, and by how much?", "should_trigger": true },
{ "query": "We're behind on ticket sales six weeks out - should we buy ads?", "should_trigger": true },
{ "query": "Map our audience segments to promotion channels for the conference.", "should_trigger": true },
{ "query": "Registration opens Monday - what does the promotion timeline look like through doors?", "should_trigger": true },
{ "query": "Is 120 tickets sold out of 380 expected a problem four weeks before the event?", "should_trigger": true },
{ "query": "How do we know which promotion channel is actually bringing event registrations?", "should_trigger": true },
{ "query": "Our event has no marketing budget at all - how do we still fill the room?", "should_trigger": true },
{ "query": "What weekly registration numbers should a free community event expect leading up to the day?", "should_trigger": true },
{ "query": "Prioritize promotion channels for a conference whose audience all lives in one city.", "should_trigger": true },
{ "query": "Tickets went on sale two weeks ago and it's quiet. When should we panic?", "should_trigger": true },
{ "query": "We expect 450 attendees but 75 get free tickets - what number do we market against?", "should_trigger": true },
{ "query": "Give me phase-by-phase funnel targets for our conference registration campaign.", "should_trigger": true },
{ "query": "How should a volunteer-run conference spend a 3,000 EUR promotion budget?", "should_trigger": true },
{ "query": "What's a realistic signup curve for a free workshop day with a 250-attendee goal?", "should_trigger": true },
{ "query": "Our sponsor wants us to run LinkedIn ads for the event - should ads come first?", "should_trigger": true },
{ "query": "We need a plan to sell out a 500-seat conference by September.", "should_trigger": true },
{ "query": "How much should we lean on our mailing list versus partner newsletters versus social to fill the event?", "should_trigger": true },
{ "query": "Second edition of our conference: how do we use last year's sales curve to plan this year's targets?", "should_trigger": true },
{ "query": "How far ahead of a paid tech conference should promotion be running?", "should_trigger": true },
{ "query": "Nobody's registering for our meetup's anniversary conference - walk me through what to check.", "should_trigger": true },
{ "query": "Design the promotion push around our speaker announcement and agenda release.", "should_trigger": true },
{ "query": "Free event with a hard 150-seat cap: how many registrations should we aim for?", "should_trigger": true },
{ "query": "What should our week-by-week ticket targets be from announcement to doors?", "should_trigger": true },
{ "query": "Build a registration campaign for a hybrid conference targeting 350 in-person attendees.", "should_trigger": true },
{ "query": "Our early-bird ends in three weeks - how do we structure the campaign push around it?", "should_trigger": true },
{ "query": "Is it normal that most conference tickets sell in the last two weeks?", "should_trigger": true },
{ "query": "We can either do flyering at local campuses or buy Instagram ads - which fills the hackathon?", "should_trigger": true },
{ "query": "How do we get 1,000 developers to register for our free online conference?", "should_trigger": true },
{ "query": "Which checkpoints tell us whether the campaign is on track or the event should be descoped?", "should_trigger": true },
{ "query": "Allocate promotion effort across channels for a five-person organizing team with 10 hours a week.", "should_trigger": true },
{ "query": "Should we count sponsor comp tickets toward our ticket sales target?", "should_trigger": true },
{ "query": "Plan how we get from 0 to 800 registrations for the developer festival.", "should_trigger": true },
{ "query": "The first week of ticket sales had no spike at all - what does that mean for our conference?", "should_trigger": true },
{ "query": "How do we decide between spending on ads versus relying on partner swaps to promote the event?", "should_trigger": true },
{ "query": "Write the early-bird reminder email for our conference.", "should_trigger": false },
{ "query": "Draft the attendee announcement email sequence from ticket launch to doors.", "should_trigger": false },
{ "query": "What should we price our conference tickets at, and when should early-bird end?", "should_trigger": false },
{ "query": "Design the ticket ladder - student, indie and corporate rates.", "should_trigger": false },
{ "query": "Build the landing page for our conference - hero, sections, CTA.", "should_trigger": false },
{ "query": "Our registration page gets traffic but doesn't convert - redesign the page.", "should_trigger": false },
{ "query": "Set up a ticket-discount swap deal with the Python conference across town.", "should_trigger": false },
{ "query": "Which newsletters and podcasts should we approach for a barter media partnership, and on what deal terms?", "should_trigger": false },
{ "query": "Write our conference's positioning statement and define the audience we stand for.", "should_trigger": false },
{ "query": "Is there even demand for a Rust conference in our region?", "should_trigger": false },
{ "query": "Should our event be a conference, an unconference or a hackathon?", "should_trigger": false },
{ "query": "Plan the social media content calendar for the conference - post cadence and hashtags.", "should_trigger": false },
{ "query": "Which Slack and Discord setup should the event use to talk to attendees?", "should_trigger": false },
{ "query": "Sort out press accreditation and pitch tech journalists to cover our conference.", "should_trigger": false },
{ "query": "Build the sponsor outreach plan - which companies to contact and when.", "should_trigger": false },
{ "query": "Put together the sponsorship prospectus for our 400-person event.", "should_trigger": false },
{ "query": "Price our sponsorship tiers for next year's conference.", "should_trigger": false },
{ "query": "Build the P&L and break-even model for the conference.", "should_trigger": false },
{ "query": "Work out the full month-by-month planning timeline for the event - venue, CFP, sponsors, everything.", "should_trigger": false },
{ "query": "How much should we overbook the room given expected no-shows on the day?", "should_trigger": false },
{ "query": "Design the waitlist and the day-of walk-in policy.", "should_trigger": false },
{ "query": "Should our established conference add a second track or move to a bigger venue next year?", "should_trigger": false },
{ "query": "How do we keep our attendee community alive between editions?", "should_trigger": false },
{ "query": "Turn this year's talk recordings into a publishing plan.", "should_trigger": false },
{ "query": "Write the CFP announcement and design the submission form.", "should_trigger": false },
{ "query": "Pick the date our conference should run on next year.", "should_trigger": false },
{ "query": "Give me the launch checklist for the very first edition of our meetup-turned-conference.", "should_trigger": false },
{ "query": "Run the organizing team's retro on last month's conference.", "should_trigger": false },
{ "query": "Design the attendee feedback survey for this edition.", "should_trigger": false },
{ "query": "Create a marketing plan for our B2B SaaS product launch.", "should_trigger": false },
{ "query": "Build a demand-gen campaign to drive signups for our developer tool's free tier.", "should_trigger": false },
{ "query": "Plan the email nurture sequence for webinar leads after they attend.", "should_trigger": false },
{ "query": "How should I allocate my startup's annual marketing budget across channels?", "should_trigger": false },
{ "query": "Set OKRs and targets for our product's Q4 user-acquisition funnel.", "should_trigger": false },
{ "query": "Write LinkedIn ad copy promoting our conference sponsorship packages to potential sponsors.", "should_trigger": false },
{ "query": "Which cities should our multi-city developer roadshow hit?", "should_trigger": false },
{ "query": "Decide what our company-run developer conference is funded to accomplish.", "should_trigger": false },
{ "query": "Recruit the volunteers who will staff the event.", "should_trigger": false },
{ "query": "Find speakers for our conference outside the CFP.", "should_trigger": false },
{ "query": "Design the hackathon judging rubric and scoring process.", "should_trigger": false },
{ "query": "How do we grow our meetup group's membership on the platform between events?", "should_trigger": false },
{ "query": "Plan the minute-by-minute day-of run of show.", "should_trigger": false },
{ "query": "What swag should we order and which vendor should print it?", "should_trigger": false },
{ "query": "Negotiate the venue contract for our 500-person conference.", "should_trigger": false },
{ "query": "Improve conversion on our SaaS pricing page.", "should_trigger": false },
{ "query": "Build an SEO content plan to rank for kubernetes tutorials.", "should_trigger": false },
{ "query": "Set up UTM tracking for our product newsletter campaign.", "should_trigger": false },
{ "query": "Write the fulfillment checklist so every signed sponsor gets what they bought.", "should_trigger": false },
{ "query": "Our conference sold out - decide whether and how to scale attendance 3x next edition.", "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 |