samber/dev-event-organizer-skills / skills/event-date-selection
event-date-selection
VerifiedPick the date a technical event runs on - the decision every other plan hangs off. Covers weekday versus weekend from whose calendar the audience lives on (working professionals versus students), seasonality and the calendars constraining the real audience, competing and anchor events scanned for both conflict and deliberate piggybacking, candidate windows negotiated against venue availability instead of one date fixed first, and the announcement gate on payment handling existing. Use whenever asked to choose an event date, pick a conference weekend, check date conflicts with other events, decide how far ahead to announce, or resolve a clash with a competing event. Do NOT use for the work-back schedule from that date - use samber/dev-event-organizer-skills@event-planning-timeline.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 23.8 KB |
| evals/evals.json | config | 24.7 KB |
| references/audience-calendars.md | markdown | 6.8 KB |
| references/competing-events-and-announcement.md | markdown | 9.1 KB |
evals/evals.json
View on GitHub{
"skill_name": "event-date-selection",
"evals": [
{
"id": 1,
"prompt": "I'm organizing ShipFast Conf, a two-day platform engineering conference in Rotterdam for working SREs and platform engineers, about 400 attendees, roughly a third each travelling from the Netherlands, Germany, and Poland. Second edition - last year ran in May and sold out slowly. I'm thinking we run it on a Saturday-Sunday this time so attendees don't have to take days off work, and I want to lock in the second weekend of May and get it announced on our site next week so people can book travel early. Can you sanity-check the plan and finalize the date?",
"expected_output": "A date recommendation that moves the event to a weekday slot with the rule's source named, promotes the multi-geography calendar check for the three-country audience without inventing holiday dates, treats May as a hypothesis, produces three to five candidate windows for the venue conversation, and blocks the announcement until money handling is confirmed.",
"files": [],
"expectations": [
"Recommends a weekday slot and rejects the proposed Saturday-Sunday for this working-professional audience",
"Justifies the weekday choice by whose time attendance spends: work topics belong to work life, and a weekend slot competes with family time rather than with the office",
"Attributes the weekday rule for professional audiences to the DevOpsDays organizing guide",
"Does not offer a Friday-based or Friday-plus-Saturday compromise slot",
"Promotes the multi-geography observance pass because attendees travel from three countries",
"Does not assert any specific Dutch, German, or Polish holiday date from memory as verified; requires each country's official calendar for the specific year, or the user's own input",
"Reports every calendar category as either checked with a source or explicitly outstanding, with none silently assumed clear",
"Treats the May window as a hypothesis to test against the event's own prior edition, not as a seasonal fact",
"Produces three to five candidate windows to carry into the venue conversation instead of fixing the single second-weekend-of-May date",
"Treats date and venue as one joint decision, letting venue availability rank the surviving windows",
"Refuses to schedule the announcement until a working way to handle money (ticketing, payment processing, or an entity that can receive it) is confirmed",
"Extends the competing-event scan to adjacent topics and different organizers rather than only same-brand platform-engineering events",
"Includes employer quarter-end and the school holidays of attendees' children among the professional audience's calendar checks"
]
},
{
"id": 2,
"prompt": "We run HackHarbour, a student hackathon at a university in Toronto, usually about 250 students. Two problems with this year's plan: the weekend we wanted in October is right after a huge developer conference downtown that half the local tech scene attends, so we figure we need to move at least a month away from it. And the backup weekend falls during the university's fall reading week, which obviously kills it since students will be gone. A third option would be running it Wednesday-Thursday so we're not fighting anyone for a weekend. Which of the three do we pick?",
"expected_output": "A day-type verdict that keeps the hackathon on a weekend per the student-audience rule, weighs the downtown conference as a dodge-or-piggyback decision instead of fleeing it, investigates the reading week instead of auto-rejecting it, and carries multiple surviving windows with rejected ones recorded.",
"files": [],
"expectations": [
"Rejects the Wednesday-Thursday option because a student audience attends on personal time and weekdays collide with class, exams, and part-time work",
"Cites the MLH hackathon organizer guide as the source of the weekend rule for student events",
"States the recommended weekend shape: start no earlier than Friday evening and end by Sunday",
"Does not endorse reflexively moving a month away from the downtown conference; treats proximity to it as a two-sided decision",
"Applies the dodge-or-piggyback criteria explicitly (who the other event draws, whether the audience travels or commutes, overlap in sponsors, speakers, or venues) and makes a per-event call",
"Describes piggybacking - scheduling immediately before or after a nearby major event so one trip covers both - as a documented deliberate tactic, not a consolation",
"Does not apply a blanket avoid-all-breaks rule to the fall reading week: notes a short university break can raise turnout for a single weekend event even though breaks generally reduce participation",
"Recommends checking the specific reading week (prior editions, asking students) rather than rejecting the category outright",
"Checks the university's own institutional calendar - exams, breaks, major campus events - as the floor of the constraint check",
"Widens the competing-event scan beyond hackathon listings to adjacent topics, different organizers, and call-for-papers listings",
"Includes asking two or three students what else they plan to attend that season as part of the scan",
"Records every rejected window together with the constraint it failed",
"Carries more than one surviving candidate window forward rather than crowning a single date immediately"
]
},
{
"id": 3,
"prompt": "First edition of DataForge Summit, a 300-person data-engineering conference in Austin. We've settled internally on the third week of September, and our venue said yes verbally last Friday - contract should be signed in three or four weeks. Here's the urgency: we heard a well-funded competitor is planning a data conference in Austin that same month, and we want to publish our date Monday to claim the slot before they do. We haven't picked a ticketing platform yet and our LLC paperwork is still being filed, but that's a couple of weeks out too. Draft the announcement plan - blog post Monday, socials through the week?",
"expected_output": "A refusal to announce on Monday because the money-handling gate is unpassed, with the date held internally, the gate's clearing conditions spelled out, and the trigger choice (money-ready for the contested slot, program-teased for a first edition) deferred until the gate clears.",
"files": [],
"expectations": [
"Refuses to endorse publishing the date on Monday because no working way to handle money exists yet",
"Treats money handling as a hard prerequisite gate on announcing, not one factor to weigh against the competitor threat",
"Cites the documented consequence of skipping the gate: teams have rescheduled or cancelled events",
"Advises keeping the date decided internally and publishing nothing until the gate clears",
"States that an unannounced date is still a variable while a published one is a promise",
"Does not present the announcement-trigger options as currently selectable; brings that menu back only after money handling exists",
"Specifies what clears the gate: a ticketing arrangement, a payment processor, or an entity able to receive money, whichever the event's model needs",
"Requires a named person accountable for the money",
"Distinguishes the verbal venue agreement from a signed contract, so the venue-locked trigger's precondition is not yet met",
"Acknowledges the contested slot maps to the money-ready trigger (publishing before the venue signs) once, and only once, the money gate clears",
"Raises the program-teased option for this first edition: waiting for an anchor speaker or an openable CFP so the announcement carries more than a bare date from an unknown event",
"Does not invent an attendance or registration figure to justify the announcement timing"
]
},
{
"id": 4,
"prompt": "Our open-source project Meshwork runs its annual contributor summit alongside a large cloud-native conference - the foundation gives satellite events exactly one co-location slot, and ours is confirmed: the two days right before the main conference in Amsterdam. That can't move. My co-organizer wants us to now do the full due-diligence pass we did last year: map every holiday across our contributors' 12 countries, build a spreadsheet of every conference that quarter, and score alternative weeks. She figures three or four days of work. Before we burn the time - what date research does this situation actually need?",
"expected_output": "A verdict that the externally forced window deletes the competing-event scan and multi-geography pass as decision inputs, keeps the audience-calendar floor, redirects the hours into mitigation, routes known conflicts to risk planning, and replaces the candidate-window gate with a written record of the constraint.",
"files": [],
"expectations": [
"Identifies the window as externally forced and states that no scan result could change the date",
"Advises deleting, not merely deprioritizing, the competing-event scan and the multi-geography observance pass as date-selection inputs",
"Gives the rationale: a check whose result cannot change the decision has no decision attached",
"Rejects the three-to-four-day research plan, including scoring alternative weeks, rather than trimming it",
"Redirects the available hours toward mitigating the conflicts the forced window already carries",
"Routes known conflicts and observance collisions into risk planning as hazards, not back into the date decision",
"Does not require generating three candidate windows; the gate becomes writing down the constraint, what fixes it, and who could move it",
"Retains the audience-calendar floor - knowing which contributor calendars the fixed window collides with - for mitigation purposes",
"Confirms the announcement remains gated on money handling regardless of the forced window",
"Asks or confirms who could actually move the constraint before accepting it as immovable"
]
},
{
"id": 5,
"prompt": "We're planning CompilerCamp, a two-day systems programming conference in Manchester. We deliberately want both audiences: professional compiler engineers from the big employers in town, and CS students from the two universities. Our committee landed on Friday plus Saturday as the obvious compromise - Friday is a workday so the professionals can come on company time, Saturday works for the students. One committee member wants data: roughly what percentage of attendance do we lose if we get the day choice wrong? Help us settle both the dates and that estimate.",
"expected_output": "A rejection of the Friday-plus-Saturday compromise with the worst-half-of-each-rule reasoning, the pick-a-pole and programme-split routes laid out with boundary days marked weakest, the pole named in the deliverable, and a refusal to attach a percentage to the day-type mistake.",
"files": [],
"expectations": [
"Rejects the Friday-plus-Saturday compromise rather than endorsing it",
"Explains the specific failure: the compromise takes the worst half of each rule - an employer day students cannot take off and a personal day professionals will not give",
"Presents picking one audience pole and accepting lower attendance from the other as the primary route",
"Presents the programme-split alternative - a weekday main programme plus a weekend-adjacent satellite day - with its stated cost of a second day of logistics and a second volunteer roster",
"Labels boundary days (Friday and Monday) the weakest option: the day both audiences are most easily pulled away from, endorsed by neither guide",
"Requires the deliverable to name which pole was picked and why",
"Frames the pole choice as a positioning decision to make explicitly, not a scheduling detail",
"Grounds the two opposing day-type defaults in their sources: the DevOpsDays guide for the weekday rule and the MLH guide for the weekend rule",
"Declines to give a percentage attendance penalty for a wrong day type, stating the guides say which day but not how much a mistake costs",
"Does not fabricate any substitute attendance statistic for the committee member",
"Establishes whose time the attendee spends as the first and deciding question before any other constraint"
]
},
{
"id": 6,
"prompt": "Fourth edition of RustAtlantic, our annual Rust conference in Halifax - the date has been public for two months, about 900 tickets usually, maybe 180 sold so far. We're behind: our keynote speaker pulled out last week, the CFP opened three weeks late, and the workshop track has no leads yet. The team wants to push the whole event back six weeks to buy breathing room - we'd email ticket holders, and most would probably be fine with it. Good idea, or how would you play it?",
"expected_output": "A recommendation to hold the announced date and cut scope instead, with the promise framing, the extra retraction cost a recurring event pays, and the work-back schedule identified as the variable that moves.",
"files": [],
"expectations": [
"Advises against moving the announced date",
"States the published date is a promise, and moving it burns speaker, sponsor, and attendee trust",
"Notes the retraction cost is higher for a recurring annual event than for a one-off",
"Recommends cutting scope instead - shrinking or dropping the unready parts such as the workshop track - to rescue the plan",
"Does not accept the keynote loss or late CFP as sufficient grounds to reschedule",
"Treats the internal work-back schedule as what adjusts, not the public date",
"Does not propose a retract-and-reannounce or tentative-new-date maneuver",
"Does not treat the low ticket count or expected ticket-holder tolerance as making the move cheap"
]
},
{
"id": 7,
"prompt": "We've done our homework for GreenStack Days, a sustainability-in-tech conference in Copenhagen: three date windows in March-April all cleared our conflict checks, and we ranked them - window A is clearly best for us, and C is honestly a stretch we'd rather not use. Tomorrow I meet our top venue choice. My plan: present the ranked list, push hard for window A, and keep C as a bargaining chip. Also, heads up - the venue emailed that they might counter with a week in late February they're trying to fill. How do I run this negotiation?",
"expected_output": "Negotiation guidance that presents the windows as equivalents rather than a ranked list, removes or genuinely accepts the bluff window, asks after the venue's quiet periods, and routes the February counter-offer back through the constraint checks before acceptance.",
"files": [],
"expectations": [
"Advises presenting the windows as equivalent options rather than a ranked list",
"Gives the reason: a ranked list invites the venue to offer only the top window and decline the rest",
"Flags window C: a window the team would refuse is not an option but a bluff that collapses if the venue picks it - drop it or genuinely accept it",
"Recommends asking the venue about its own quiet periods, where rate flexibility lives",
"Treats the late-February counter-offer as a new candidate window rather than accepting or rejecting it on availability alone",
"Requires the counter-offer to go back through the constraint checks (calendars, competing events) before acceptance",
"States that an availability or rate win landing on an unchecked observance is not a win",
"Names the several-windows-into-the-venue-conversation practice as \"Get Options\" or attributes it to the DevOpsDays guide",
"Suggests restoring the option count so three to five genuinely acceptable windows enter the conversation"
]
}
],
"trigger_queries": [
{ "query": "Help me pick a date for our Kubernetes conference next year.", "should_trigger": true },
{ "query": "Should our developer conference run on a weekday or a weekend?", "should_trigger": true },
{ "query": "Our student hackathon clashes with another one in the same city - move it or keep the date?", "should_trigger": true },
{ "query": "When should we announce the date for our tech conference?", "should_trigger": true },
{ "query": "Is scheduling our conference the same week as a giant industry conference suicide, or can we use it?", "should_trigger": true },
{ "query": "What's the best month to run a developer conference in northern Europe?", "should_trigger": true },
{ "query": "We can't decide between two weekends in June for the hackathon - how do we choose?", "should_trigger": true },
{ "query": "The venue gave us three possible weeks - which one do we take and when do we go public?", "should_trigger": true },
{ "query": "How far in advance should a conference date be announced?", "should_trigger": true },
{ "query": "Check whether mid-October works for our security summit or if something big collides with it.", "should_trigger": true },
{ "query": "Our conference date keeps landing on school holidays somewhere - how do I pick a week that works across Europe?", "should_trigger": true },
{ "query": "Pick a weekend for a 48-hour student hackathon in the fall semester.", "should_trigger": true },
{ "query": "There's a huge gaming expo in our city the week we wanted - should we move our indie dev conference?", "should_trigger": true },
{ "query": "Everything else about the event is planned, we just don't have a date yet. Where do we start?", "should_trigger": true },
{ "query": "Would running our event right after a major conference in the same city help or hurt attendance?", "should_trigger": true },
{ "query": "We want to announce our conference date but ticketing isn't set up yet - go anyway?", "should_trigger": true },
{ "query": "How do I check if another tech event conflicts with the week we picked?", "should_trigger": true },
{ "query": "Weekday vs Saturday for a 200-person API meetup for professionals - settle this argument.", "should_trigger": true },
{ "query": "What do organizers usually check before locking a conference date?", "should_trigger": true },
{ "query": "Ramadan might overlap the window we like for our Berlin developer festival - how should we handle it?", "should_trigger": true },
{ "query": "Our CFO says don't announce until the venue contract is signed, marketing wants to announce now - who's right?", "should_trigger": true },
{ "query": "Find us a date for the third edition of our data engineering summit.", "should_trigger": true },
{ "query": "Two conferences in our niche already picked June - where does that leave us?", "should_trigger": true },
{ "query": "Does it matter which day of the week a community tech event lands on?", "should_trigger": true },
{ "query": "We're thinking last weekend of September for the hackathon - poke holes in that.", "should_trigger": true },
{ "query": "How do conference organizers avoid double-booking against other events?", "should_trigger": true },
{ "query": "The university's exam period moved and now our event date looks risky - rethink it with me.", "should_trigger": true },
{ "query": "When do we tell the public the date - after the venue signs, or sooner to beat a competitor?", "should_trigger": true },
{ "query": "Sanity-check March 12-13 for our platform engineering conference.", "should_trigger": true },
{ "query": "Our audience is half students, half professionals - what day do we run the conference?", "should_trigger": true },
{ "query": "Is August really a dead month for tech events or is that a myth we should test?", "should_trigger": true },
{ "query": "A rival meetup group announced an event two days before ours - what now?", "should_trigger": true },
{ "query": "Help me shortlist candidate weeks for a two-day fintech developer conference.", "should_trigger": true },
{ "query": "What holidays should I check before fixing the date of an international conference?", "should_trigger": true },
{ "query": "Our sponsor wants the event inside their fiscal Q2 - how does that constrain the date?", "should_trigger": true },
{ "query": "Should we anchor our community day to the big annual conference or keep our distance?", "should_trigger": true },
{ "query": "We've outgrown our usual slot - walk me through re-picking the annual conference date.", "should_trigger": true },
{ "query": "Our conference date is locked for June 10 - build the work-back plan of everything due before it.", "should_trigger": false },
{ "query": "The date's set; what should the 12-week countdown of milestones look like?", "should_trigger": false },
{ "query": "Help me find and shortlist venues for a 500-person developer conference.", "should_trigger": false },
{ "query": "Is there even room for another DevOps conference in our region, or is the market saturated?", "should_trigger": false },
{ "query": "There are already four AI meetups in town - does a fifth have an audience?", "should_trigger": false },
{ "query": "When should our CFP open and close, and how long should the review window be?", "should_trigger": false },
{ "query": "Design the CFP form and review process for our conference.", "should_trigger": false },
{ "query": "Build the two-day session schedule - how many tracks and how long should talks be?", "should_trigger": false },
{ "query": "Draft the minute-by-minute run of show for the keynote morning.", "should_trigger": false },
{ "query": "Should our company run a roadshow or a single user conference this year?", "should_trigger": false },
{ "query": "What should we charge for tickets to our two-day conference?", "should_trigger": false },
{ "query": "Put together the budget for a 300-person conference.", "should_trigger": false },
{ "query": "Which audience should our conference be built for - students or senior engineers?", "should_trigger": false },
{ "query": "What launch gates should a first-edition conference clear before we commit to running it?", "should_trigger": false },
{ "query": "How do we promote our conference and when should the marketing pushes go out?", "should_trigger": false },
{ "query": "Write the announcement blog post for our conference.", "should_trigger": false },
{ "query": "How do we cut our hackathon's no-show rate?", "should_trigger": false },
{ "query": "Plan the after-party and evening social program for our summit.", "should_trigger": false },
{ "query": "Coordinate the community-run side events happening around our conference week.", "should_trigger": false },
{ "query": "What risks should be on the risk register for our outdoor tech festival?", "should_trigger": false },
{ "query": "Help me pick which talks to accept from 200 CFP submissions.", "should_trigger": false },
{ "query": "How should we structure sponsorship tiers and pricing?", "should_trigger": false },
{ "query": "Our two annual events cannibalize each other's audience - how should we promote them together?", "should_trigger": false },
{ "query": "Set up a recurring calendar event for our weekly team standup.", "should_trigger": false },
{ "query": "Find a meeting slot next week that works for eight people across three time zones.", "should_trigger": false },
{ "query": "Reschedule my Thursday meetings and update the invites.", "should_trigger": false },
{ "query": "Sync our conference schedule into attendees' Google Calendars.", "should_trigger": false },
{ "query": "What's the best day of the week to send our product newsletter?", "should_trigger": false },
{ "query": "Pick a launch date for our SaaS product's v2 release.", "should_trigger": false },
{ "query": "When should we schedule the maintenance window for the database migration?", "should_trigger": false },
{ "query": "Design the event store and event sourcing schema for our order service.", "should_trigger": false },
{ "query": "Subscribe our webhook to calendar change events in the workspace API.", "should_trigger": false },
{ "query": "Plan my week - block time for deep work around my existing meetings.", "should_trigger": false },
{ "query": "How far in advance should wedding invitations go out?", "should_trigger": false },
{ "query": "Build the production schedule for our factory's Q3 output.", "should_trigger": false },
{ "query": "Which conference should our team attend this year given our travel budget?", "should_trigger": false },
{ "query": "How do I add speaker session times to the event mobile app agenda?", "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 |