samber/dev-event-organizer-skills / skills/event-market-fit
event-market-fit
VerifiedRead whether a technical event's concept, audience and price combination actually meets demand - before launch (community baseline, CFP oversubscription, saturation mapping), mid-sale (checkpoint ladder and pace index against expected sales), and after an edition (attendee return, sponsor renewal, sellout-speed trend) - composed into a go, hold, pivot or stop call. Use whenever asked to validate demand for a conference, hackathon or a meetup-to-conference jump, judge whether ticket sales are on pace, decide whether an event should recur or scale, or diagnose why an edition underperformed. Reads signals only. Do NOT use for launch scoping - use samber/dev-event-organizer-skills@event-first-edition - or growth levers - use samber/dev-event-organizer-skills@event-growth-strategy.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 20.3 KB |
| evals/evals.json | config | 24.4 KB |
| references/demand-signal-benchmarks.md | markdown | 9.8 KB |
| references/reading-failures.md | markdown | 7.6 KB |
evals/evals.json
View on GitHub{
"skill_name": "event-market-fit",
"evals": [
{
"id": 1,
"prompt": "We run 'Data Circus', a monthly data-engineering meetup in Leeds. Our best-attended session ever drew 45 people, usually more like 30. Our Slack has 380 members. I read that typical first-edition community conferences draw around 250 attendees, so we're planning a 250-seat paid conference next spring at £120 a ticket. I also read community-building advice that groups shift character at 5, 12, and 45 members, and we're way past 45, so the community is clearly ready. We posted an interest form on the meetup page and got 210 'I'd come!' responses. Ready to book the venue?",
"expected_output": "A staged demand read that resets the attendance expectation from the meetup baseline, corrects the misquoted community thresholds, rejects the free interest form as evidence, and prescribes pre-declared instruments instead of a go.",
"files": [],
"expectations": [
"Sets the first-edition attendance expectation by multiplying the best meetup draw (45) by 2-3, landing at roughly 90-135 seats, not 250.",
"Rejects the ~250 'typical first edition' figure as an average across cities with larger communities, unusable as this city's target.",
"Corrects the 5/12/45 community thresholds as a misquote and cites 7/13/50/90/150 as the verified ladder.",
"Treats any 'grow to N members before launching' rule as self-set rather than a validated launch gate for the 380-member Slack.",
"Refuses to count the 210 free interest-form responses as demand evidence, classifying them as curiosity rather than intent.",
"Cites the roughly 50% no-show rate on free RSVPs as the reason free interest counts are excluded from the evidence menu.",
"Recommends at least one intent-filtering instrument (deposit-backed waitlist or CFP probe) with its pass threshold declared before the instrument opens.",
"If a CFP probe is proposed, sets a 2-3:1 oversubscription target and labels it self-set, scaled down from flagship figures rather than an industry standard.",
"Runs or prescribes a saturation scan of competing events and CFP listings before any go call, and treats it as capable only of ruling out, never proving demand.",
"Frames the demand question as a job statement of the form 'When [circumstance], I want to [progress], so I can [outcome]'.",
"Withholds the go verdict: the call is to hold and instrument first, not to book the 250-seat venue.",
"Labels the numeric thresholds it uses with a confidence tag (sourced, synthesis, or self-set).",
"Routes launch scoping and venue commitment to the first-edition sibling skill rather than delivering launch planning itself."
]
},
{
"id": 2,
"prompt": "Second edition of 'Kernel & Crust', our systems-programming conference in Porto. We put 500 tickets on sale 5 days ago and have only sold 38. Last year at this exact point we'd sold 61. Of this year's 38, 12 are actually speaker and sponsor comp codes that got redeemed. My co-organizer wants to publicly slash prices 30% this week to get momentum back. Is the event dying?",
"expected_output": "A refusal to read demand from day-5 data, a comp-netted count, instrumentation against the event's own prior curve, and a block on the public discount, with pricing routed to its sibling.",
"files": [],
"expectations": [
"Declines to issue a demand verdict from day-5 data, stating that the launch window tests reach, not demand, and the real read starts around week two.",
"Nets out the 12 comp redemptions and works from 26 paid tickets, not 38.",
"Judges pace against the event's own edition-1 curve rather than a generic expected curve, since a prior edition exists.",
"Advises against the public 30% discount, warning that public cuts teach the audience to wait.",
"Names targeted codes or bundles as the acceptable price-side response if price later becomes the diagnosis.",
"Routes any pricing change to the ticket-pricing sibling skill rather than prescribing the pricing fix itself.",
"Schedules the shortfall differential before any conclusion: marketing-execution gap versus price misfit versus genuine demand gap.",
"Describes the price-misfit signature as healthy event-page traffic with low conversion in the first two weeks, and notes that evidence has not been shown yet.",
"Prescribes weekly sales-pace instrumentation (pace index or checkpoint reads) for the remainder of the sale.",
"Describes the expected sales curve as spike-driven or U-shaped (announcement spike, quiet middle, final surge), not linear.",
"Notes that a surge in the final two weeks is normal, not a red flag.",
"Issues no stop or pivot verdict on this data; 'the event is dying' is explicitly withheld."
]
},
{
"id": 3,
"prompt": "'FluxConf', our observability conference in Denver, just wrapped edition 3. It sold out in 9 days (edition 2 took 31 days), the attendee survey came back 4.6/5, and 44% of last year's attendees came back. But only 9 of our 16 edition-2 sponsors renewed. The team wants to jump from 600 to 1,200 seats next year since two of our three metrics are killing it. Green light?",
"expected_output": "A three-signal read kept separate per axis that lands on hold-and-fix despite two green signals, because the red axis is sponsor renewal, with the sellout speed checked for batching and the ROI-report lever named.",
"files": [],
"expectations": [
"Computes sponsor renewal as 9 of 16, roughly 56%, and flags it below the 70% per-edition aim.",
"Reads the three lagging signals separately and refuses to blend them into one composite score.",
"Notes 44% attendee return clears the 30% floor, and treats 30% as a failing-grade-avoided floor a tight developer community should beat, not a success target.",
"Reads the sellout-speed trend (31 days to 9 days) as green on its own axis.",
"Delivers hold-and-fix, not go or scale, despite two of three signals being green.",
"Justifies the veto by sponsor renewal's confidence: deliberate repeat-budget money, independent of ticket buzz.",
"Cites the documented pattern of an event dying on the sponsor axis while its attendee signals stayed green.",
"Asks whether 72-hour post-event ROI reports were sent to sponsors, naming that report as the single highest-leverage renewal action.",
"Checks whether the 9-day sellout involved batch ticket releases before reading it as organic demand.",
"Recommends holding the 600-to-1,200 venue jump for at least one edition while the sponsor axis is diagnosed and fixed.",
"Labels the two-of-three composite assembly as a synthesis, not an industry standard.",
"Labels the renewal (70%) and return (30%) thresholds as sourced figures.",
"Routes the sponsor value-proposition or fulfillment fix to a sibling skill instead of prescribing it here."
]
},
{
"id": 4,
"prompt": "I'm the devrel lead at Quantivo, a data-warehouse vendor. Our free 'Quantivo Summit' pulled 1,400 registrations against 800 seats in 3 weeks - we 'sold out' nearly 2x over. Marketing wants to use this to justify a paid $299 conference next year plus a 3-city roadshow. Our CEO also points to the sponsor slide: Quantivo is title sponsor and renewed, plus two partner booths. How strong is our demand case?",
"expected_output": "A company-run read that swaps in the substitute signals, discounts free-registration oversubscription and self-sponsorship, and demands a paid instrument before the $299 bet.",
"files": [],
"expectations": [
"Identifies the event as company-run and applies the company-run signal substitutions rather than the community-run signal set.",
"Discounts the '2x sold out' framing as demand evidence because nothing was purchased.",
"Applies the 40-60% no-show rate for free events to the 1,400 registrations, projecting roughly 560-840 actual show-ups.",
"Substitutes registration-to-show-up rate for sellout speed, flagged as a reasoned stand-in rather than a measured equivalent.",
"Dismisses Quantivo's own title-sponsorship renewal as a demand signal, since the sponsor is the event's owner.",
"Substitutes pipeline or adoption outcomes for sponsor renewal, flagged as a stand-in.",
"States that free registrations do not validate the $299 price point.",
"Recommends a paid instrument - paid probe events measuring paid conversion, or a deposit-backed waitlist - before committing to the paid conference.",
"Requires the paid instrument's pass threshold to be declared before it opens.",
"Contrasts paid-ticket show-up (90-97%) with free-event no-show rates as part of the read.",
"Issues no go for the paid conference or roadshow on the current evidence.",
"Routes the roadshow-versus-conference format decision to a sibling skill as out of scope."
]
},
{
"id": 5,
"prompt": "We want to launch 'RustForge', a paid Rust conference in Atlanta. I did my research: 'CrabCon', the big Rust conference in our region, shut down last year - the organizers posted about stepping away after a code-of-conduct blow-up and board resignations, and press coverage called it 'a declining conference'. And I found zero other Rust conferences within 500 miles on the calendars I checked. So the market is wide open and de-risked, right? We have no local Rust meetup, but Rust is huge on Reddit.",
"expected_output": "A read that excludes the governance-driven shutdown from demand evidence, refuses the empty-calendar inference, flags the missing baseline as its own red flag, and prescribes community-first plus paid probes.",
"files": [],
"expectations": [
"Excludes the CrabCon shutdown from the demand evidence because the organizers' own account cites governance and code-of-conduct conflict, not demand.",
"States the differential rule: a shutdown counts as demand evidence only when the organizer's own account cites sales, sponsors, or attendance.",
"Rejects 'zero competing conferences' as proof of demand: an empty calendar proves nothing by itself.",
"Names non-consumption (staying home, existing channels) as the biggest competitor for a first edition.",
"Flags the absence of any local Rust meetup or community as 'no baseline exists' - a distinct red flag from a small baseline, leaving nothing to multiply.",
"Recommends the community-first sequence: cultivate the community or meetup first, then run events for it.",
"Rejects Reddit popularity and social reach as demand evidence, excluded from the instrument menu as curiosity measures.",
"Promotes paid probe events (a paid deep-dive or mini-hackathon measuring paid conversion, not RSVPs) as the fitting instrument when no meetup baseline exists.",
"Proposes a CFP probe with a pre-declared oversubscription target, or notes that CFP undersubscription would be a stop signal meaning stay at meetup scale.",
"Delivers a hold or not-go verdict rather than endorsing 'wide open and de-risked'.",
"Frames the job statement and the four forces (push, pull, anxiety, habit) on the ticket decision before leaning on instruments.",
"Reads the difficulty of recruiting co-organizers from outside one's own employer as an implicit early market test."
]
},
{
"id": 6,
"prompt": "'ShipItCon', platform engineering, Dublin, first edition. Target is 400 tickets but we already handed 40 comp tickets to speakers and sponsors, so 360 to sell. One month out we've sold 98. Early bird closed at 55 sold. Honestly we never did the announcement push - our designer quit and we skipped the speaker-announcement emails and socials entirely. We also have a 900-person waitlist from a signup form we posted before tickets went live, so demand is clearly there. Should we just call it demand-proven, blame the price, and discount?",
"expected_output": "A comp-netted checkpoint read that lands the shortfall in the skipped-push signature, refuses both the price blame and the waitlist-as-proof claim, and routes the fix to marketing before re-reading.",
"files": [],
"expectations": [
"Computes checkpoint percentages net of comps, against 360 expected sales rather than 400.",
"Reads the early-bird close at roughly 15% (55 of 360) as on-ladder for that checkpoint.",
"Reads the one-month-out position at roughly 27% (98 of 360) against the 40-50% checkpoint.",
"Attributes the shortfall to the skipped visibility push, matching the 25-30% marketing-execution signature, rather than declaring a demand gap.",
"Withholds the demand verdict until the differential resolves: re-read the curve after the visibility push runs.",
"Routes the visibility-push work to the marketing-plan sibling skill.",
"Rejects 'blame the price': the price-misfit signature (healthy page traffic with low conversion in the first two weeks) has not been demonstrated.",
"Advises against a public discount because public cuts teach the audience to wait.",
"Rejects the 900-person pre-launch waitlist as demand proof: a free list opened before sale with no pre-declared conversion target is a mailing list.",
"Distinguishes a post-sellout waitlist (high-intent evidence) from this pre-launch one.",
"Proposes making the waitlist evidential going forward, via a refundable deposit or a conversion target declared before reading it, noting deposit-backed lists convert several times higher than free ones.",
"Prescribes weekly checkpoint or pace-index instrumentation for the remaining sale window.",
"Issues neither a pivot nor a stop verdict on this evidence."
]
},
{
"id": 7,
"prompt": "We're deciding whether 'DocsCamp', our Berlin meetup for docs and DevEx writers, should become an annual paid conference. Our first CFP got 31 proposals for 12 slots. A friend who reviews for an academic HCI conference says that's weak - good venues reject 74% of submissions, so 2.6:1 means limited interest. Separately, our quarterly hackathon gets 60 signups for 40 spots and about half of the participants come back each time - is that a strong fit signal we can bank?",
"expected_output": "A read that scores 2.6:1 as a strong first-CFP signal, throws out the academic comparison, downgrades the hackathon figures to self-set directional data, and demands a second signal class before any go.",
"files": [],
"expectations": [
"Reads 31 proposals for 12 slots (about 2.6:1) as inside the 2-3:1 strong-signal band for a first local CFP, contradicting the 'weak' claim.",
"Rejects the academic acceptance-rate comparison as invalid because peer-review selection follows a different logic than conference CFPs.",
"Notes the 2-3:1 target is scaled down from flagship figures (around 6.5:1) and is a self-set target, not an industry standard.",
"Treats CFP oversubscription as evidence of a speaker base and, by extension, an audience - a leading signal, not a go verdict by itself.",
"Requires at least a second independent signal class before the go call.",
"Classifies the hackathon oversubscription and return figures as self-set and directional, not bankable sourced evidence.",
"Asks the organizer to define the hackathon targets (participants, and how many return or keep contributing within three months) before reading those numbers.",
"Reads submitter diversity, such as the share of first-time speakers, as an additional vibrancy signal worth checking in the CFP data.",
"Labels the figures used with confidence tags (sourced, synthesis, or self-set).",
"Recommends complementary pre-launch reads - the meetup-draw-times-2-3 baseline or a saturation scan - before sizing the conference.",
"Requires any further instrument (such as a deposit-backed waitlist) to have its pass threshold declared before it opens."
]
}
],
"trigger_queries": [
{ "query": "Is there enough demand for a paid Kubernetes conference in our city?", "should_trigger": true },
{ "query": "Our meetup draws 60 people - can we turn it into a conference?", "should_trigger": true },
{ "query": "Ticket sales feel slow six weeks out, are we on pace?", "should_trigger": true },
{ "query": "We sold 150 of 500 tickets with a month to go, should we panic?", "should_trigger": true },
{ "query": "How do I know if my developer conference should happen again next year?", "should_trigger": true },
{ "query": "Half our sponsors didn't renew but attendees loved it - does the event have a future?", "should_trigger": true },
{ "query": "validate demand for a hackathon before we book the venue", "should_trigger": true },
{ "query": "Should we scale our conference from 300 to 800 seats next year?", "should_trigger": true },
{ "query": "Why did our second edition undersell compared to the first?", "should_trigger": true },
{ "query": "Is our conference concept dead or did we just market it badly?", "should_trigger": true },
{ "query": "Our CFP got 3x more talks than slots - what does that tell us?", "should_trigger": true },
{ "query": "Nobody's submitting to our CFP, should we cancel the conference?", "should_trigger": true },
{ "query": "We have a 2,000-person waitlist for our dev summit - is that real demand?", "should_trigger": true },
{ "query": "How do I test whether developers would actually pay for this event?", "should_trigger": true },
{ "query": "Is there room for another AI conference in London or is the space saturated?", "should_trigger": true },
{ "query": "Are early-bird sales of 40 tickets good or bad against a 400-ticket target?", "should_trigger": true },
{ "query": "My free meetup gets 200 RSVPs - does that mean a paid event would work?", "should_trigger": true },
{ "query": "we want to go from quarterly meetup to annual conference, how do we know we're ready", "should_trigger": true },
{ "query": "Tickets went on sale Monday and we've only sold 12, is it over?", "should_trigger": true },
{ "query": "How to tell if slow ticket sales mean bad marketing or no demand", "should_trigger": true },
{ "query": "Should this event recur, pivot, or die? Help me decide.", "should_trigger": true },
{ "query": "Attendance dropped 30% this year - is the format losing fit?", "should_trigger": true },
{ "query": "Our event sold out in 4 days - safe to double capacity next year?", "should_trigger": true },
{ "query": "What demand signals should I check before committing the venue deposit for a first edition?", "should_trigger": true },
{ "query": "Is 25% returning attendees good for a tech conference?", "should_trigger": true },
{ "query": "How many people should we expect at our first conference given our meetup size?", "should_trigger": true },
{ "query": "Do we have product-market fit for our developer event?", "should_trigger": true },
{ "query": "Sponsor renewals came in at 50% - what does that say about our event?", "should_trigger": true },
{ "query": "A competitor conference just shut down - does that mean the space is open for us?", "should_trigger": true },
{ "query": "check if our ticket sales curve is healthy", "should_trigger": true },
{ "query": "We're 3 editions in and it keeps getting harder to sell out - diagnose why.", "should_trigger": true },
{ "query": "Was our sold-out conference a fluke or is there a real audience here?", "should_trigger": true },
{ "query": "Free registrations doubled but show-ups halved - what's going on with demand?", "should_trigger": true },
{ "query": "should i run a paid workshop first to test the waters before a full conference", "should_trigger": true },
{ "query": "How would you measure whether a city can support a DevOps conference?", "should_trigger": true },
{ "query": "Our waitlist converted at 2% when tickets opened - what does that mean?", "should_trigger": true },
{ "query": "The interest form got 500 responses - is that enough to greenlight the event?", "should_trigger": true },
{ "query": "Judge whether our developer summit underperformed because of price or demand", "should_trigger": true },
{ "query": "We put 600 tickets on sale and only moved 90 in three weeks - bad sign?", "should_trigger": true },
{ "query": "Help me set ticket prices and early-bird tiers for our conference.", "should_trigger": false },
{ "query": "Write the marketing plan for our conference's announcement push.", "should_trigger": false },
{ "query": "Design our CFP form and the review rubric for submissions.", "should_trigger": false },
{ "query": "Which talks should we accept from our CFP submissions?", "should_trigger": false },
{ "query": "Plan the launch timeline for our first conference edition.", "should_trigger": false },
{ "query": "What growth levers should we pull to scale our conference next year?", "should_trigger": false },
{ "query": "Should our event be a single-track conference or an unconference?", "should_trigger": false },
{ "query": "Draft our sponsor prospectus with tier pricing.", "should_trigger": false },
{ "query": "How do I win back churned sponsors - write the outreach emails.", "should_trigger": false },
{ "query": "Build the post-event attendee feedback survey for us.", "should_trigger": false },
{ "query": "Run the post-mortem debrief for last week's conference.", "should_trigger": false },
{ "query": "Pick the best date for our conference so it doesn't clash with other events.", "should_trigger": false },
{ "query": "Find and negotiate a venue for a 500-person conference.", "should_trigger": false },
{ "query": "How should we position our conference against the big incumbent?", "should_trigger": false },
{ "query": "Build the budget spreadsheet for our first conference.", "should_trigger": false },
{ "query": "How do we reduce no-shows at our free meetup?", "should_trigger": false },
{ "query": "Do we have product-market fit for our SaaS? We ran the Sean Ellis 40% survey.", "should_trigger": false },
{ "query": "Size the total addressable market for our developer-tools startup.", "should_trigger": false },
{ "query": "How do I validate demand for a new product feature before building it?", "should_trigger": false },
{ "query": "Plan the judging criteria and scoring for our hackathon.", "should_trigger": false },
{ "query": "Design the challenge brief for our hackathon.", "should_trigger": false },
{ "query": "How much cash prize should our hackathon offer?", "should_trigger": false },
{ "query": "Grow the Discord community around our conference.", "should_trigger": false },
{ "query": "What goals should our company's user conference be funded to accomplish?", "should_trigger": false },
{ "query": "Choose between a multi-city roadshow and a single user conference for our launch.", "should_trigger": false },
{ "query": "Set up cross-promotion between our two conferences.", "should_trigger": false },
{ "query": "Improve the attendee experience at our conference.", "should_trigger": false },
{ "query": "Write a 72-hour sponsor ROI report template for us.", "should_trigger": false },
{ "query": "How do we increase our CFP submission count next year?", "should_trigger": false },
{ "query": "Schedule our conference planning milestones and checkpoint dates.", "should_trigger": false },
{ "query": "Which speakers should we invite to maximize ticket sales?", "should_trigger": false },
{ "query": "Our conference is oversubscribed - how do we run a fair waitlist and seat allocation?", "should_trigger": false },
{ "query": "Write landing page copy that converts visitors into ticket buyers.", "should_trigger": false },
{ "query": "Decide which of our five community events to sunset for budget reasons.", "should_trigger": false },
{ "query": "Forecast catering and AV costs for 800 attendees.", "should_trigger": false },
{ "query": "How do we price the sponsorship packages for our conference?", "should_trigger": false },
{ "query": "Plan the social media calendar for the six weeks before our conference.", "should_trigger": false },
{ "query": "A/B test our ticket page to improve its conversion rate.", "should_trigger": false },
{ "query": "How should I structure the volunteer team for the 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 | Unverified | 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 |