Skip to content

samber/dev-event-organizer-skills / skills/event-side-event-coordination

event-side-event-coordination

Verified

Approve and coordinate third-party-run satellite events around a technical event - the vetting gate, calendar deconfliction against the published grid, name and logo usage rules, and the disclaimer stating what the main event does not vouch for. Use whenever a user group, sponsor or attendee wants to run a party, meetup, dinner, workshop or afterparty during the event's dates, when someone is already using the event's name on their own page, or when fringe events collide with the main programme - even if they never say "side event". Approving nothing is often the right answer; routes trademark and liability exposure to counsel. Do NOT use for the organizer's own evening programme - use samber/dev-event-organizer-skills@event-official-social-program instead.

evals/evals.json

View on GitHub
{
  "skill_name": "event-side-event-coordination",
  "evals": [
    {
      "id": 1,
      "prompt": "We're running the first edition of Terrafold, a 300-person infrastructure conference in Lyon next April, so five months out. I'm the volunteer who ended up owning \"community stuff\" and I want to get ahead of side events. My plan is an application form, a published set of approval criteria, and a printed fringe guide we hand out at check-in. Nobody has actually asked to run anything yet, and honestly nobody outside our four organizers knows the event exists yet. Our schedule isn't published either, we haven't finished talk selection. We're not incorporated, the whole thing runs through one organizer's personal bank account. Can you draft the form and the criteria for me?",
      "expected_output": "A recommendation to adopt no posture at all - approve nothing, list nothing, say nothing - published rather than left silent, with the application form, criteria set and fringe guide declined for now, and the specific conditions named that would change the answer.",
      "files": [],
      "expectations": [
        "Recommends approving nothing, listing nothing and saying nothing as the posture, instead of delivering the requested form and criteria set",
        "Names the fact that nobody has asked yet as the reason that posture wins",
        "Declines to produce the application form or the criteria set as this situation's deliverable",
        "States the absence of a posture should itself be published rather than left silent",
        "Rules out the printed fringe guide and ties the reason to the organizer's own stated constraints",
        "Rules out any signed partnership agreement because no legal entity exists that could be a counterparty",
        "Declines to set protected windows because the schedule is not published yet",
        "Names the specific conditions that would change the recommendation, including a request actually arriving or a third party using the event's name in published materials",
        "States no monetary figure, no legal threshold and no named legal instrument anywhere in the answer",
        "Labels any threshold it does give as one the organizer sets rather than an industry benchmark",
        "Presents the recommendation for the organizer's validation before anything is published"
      ]
    },
    {
      "id": 2,
      "prompt": "Someone is selling 35 EUR tickets on a ticketing site to something called \"The Harborlight Warehouse Party\", with our Harborlight Systems Summit logo at the top of the listing and the words \"the official Summit afterparty\" in the description. We have had zero contact with these people. Our summit runs under the Northline Foundation, and the foundation owns the trademark, not our organizing team. The summit is in three weeks. What do we do right now, and what should we have had in place?",
      "expected_output": "A plan that removes the do-nothing option because the name is already in published third-party use, routes the marks question to the foundation and to counsel without stating any legal rule, supplies an exact non-affiliation sentence, and names the retrospective fix as a criteria set and naming rule written before any request arrives.",
      "files": [],
      "expectations": [
        "Removes doing nothing from the available options because the event's name is already in published third-party use",
        "States no monetary figure anywhere in the answer",
        "Names no legal instrument as the recommended action",
        "States no legal threshold and no jurisdiction-specific rule, and says the specific rule is jurisdiction-specific",
        "Routes the use of the name and marks to the Northline Foundation as the mark holder, and to counsel",
        "States that granting any licence to use the name is the foundation's to make rather than the organizing team's",
        "Names apparent endorsement as a separate exposure that listing or promoting the party would create",
        "Supplies an exact non-affiliation sentence rather than describing what one should contain",
        "That sentence names who runs the party and states that the summit does not",
        "That sentence sends complaints to the party organizer's own contact rather than to the summit",
        "Notes that disclaimer wording is contested rather than a reliable cure for reader confusion",
        "States the retrospective fix as a criteria set and a naming rule written before any request arrived"
      ]
    },
    {
      "id": 3,
      "prompt": "The Lagos Go User Group wants to run a meetup on the Tuesday evening before GopherNaija opens on the Wednesday. They have asked to call it \"GopherNaija Pre-Conference Night\", put our gopher mascot on the poster, and have it listed on our site. They are lovely people, they have spoken at our event twice, and probably 60 of our attendees would go. We have a titanium sponsor, Kestrel Cloud. Our code of conduct is published on our site. What do I tell them?",
      "expected_output": "An approval response that refuses the \"Pre-Conference\" wording and the mascot, names exactly which words are out and which are allowed, supplies one reusable non-affiliation sentence, imposes code-of-conduct adoption as a condition, and runs the sponsor exclusivity check first.",
      "files": [],
      "expectations": [
        "Refuses \"Pre-Conference\" in the title and states that it claims a relationship to the conference's own programme",
        "Lists the specific words that are out, such as \"official\" and \"part of\", rather than describing a spirit to follow",
        "Confirms that stating the dates, the city, or that the meetup runs during the conference is factual and allowed",
        "Recommends mandatory non-affiliation wording rather than letting the meetup make a bare factual reference to the conference",
        "Explains that a bare factual reference leaves a reader concluding a connection that is wrong, with nothing on the page to correct them",
        "Refuses use of the gopher mascot unless a licence is deliberately granted",
        "Supplies one exact sentence the user group must carry, written once and reusable in every approval",
        "That sentence names who is responsible for the meetup and states who is not",
        "That sentence states what the conference did not do",
        "Makes adoption of a code of conduct and a named contact a condition of approval, rather than assuming the conference's existing policy already reaches the meetup",
        "Checks the meetup against Kestrel Cloud's exclusivity before approving",
        "Records the decision and the criterion behind it whether the answer is yes or no"
      ]
    },
    {
      "id": 4,
      "prompt": "Our published grid for Northgate Data Week has keynotes on Wednesday 09:00-10:00 and Friday 16:30-17:30, plus an awards dinner Thursday 19:00. Six fringe events have turned up on various community pages during our week. Two of them are Wednesday morning workshops that overlap the opening keynote, and one is a vendor dinner at Thursday 19:30. I am the only person on the team with any bandwidth for this and I am on stage most of the week. How do we fix the clashes?",
      "expected_output": "A recommendation to publish protected windows naming the organizer's own hours, with the shared calendar and the curated fringe guide both ruled out for lack of a maintainer, and no change whatsoever to the published session grid.",
      "files": [],
      "expectations": [
        "Never proposes moving, shortening or rescheduling any session on the published grid",
        "States that the published grid was laid against constraints this decision does not outrank",
        "Recommends publishing protected windows as the deconfliction depth",
        "Names the specific protected hours from the organizer's own figures: Wednesday 09:00-10:00, Friday 16:30-17:30 and the Thursday 19:00 dinner",
        "Rules out a shared public calendar because nobody is available to keep it current through the week",
        "Rules out an actively deconflicted fringe guide for the same maintenance reason",
        "States that a stale calendar is worse than no calendar because it sends people to an event that moved or was cancelled",
        "Explains that a window statement prevents a collision while a calendar only records one",
        "Does not promise that the six fringe organizers will move, and notes the window statement addresses organizers rather than attendees",
        "Publishes the posture rather than leaving it unstated",
        "Labels the choice of protected hours as one the organizer sets rather than a benchmark",
        "Names collisions against the protected windows as something to record after the edition"
      ]
    },
    {
      "id": 5,
      "prompt": "Meridian Dev Summit, 1,200 people, Barcelona. Nine unofficial parties are happening during our three days and attendees keep messaging us asking which ones are worth going to. I want to put them all on a /parties page on our site: just a table with name, time, venue and link, no filtering, whoever submits gets listed. One of them is \"Vaultrun After Hours\", and Vaultrun is a direct competitor of our title sponsor Bastion Security, who paid for our top tier. Our comms lead can keep a page updated during the week. Draft me the page and the submission form.",
      "expected_output": "A page and posture that flags the Vaultrun listing against Bastion Security's paid exclusivity before anything is published, carries an explicit non-endorsement line and support framing rather than programme framing, and names who decides or states plainly that no gate is being run.",
      "files": [],
      "expectations": [
        "Flags the Vaultrun After Hours listing against Bastion Security's paid exclusivity before anything is listed",
        "States that the exclusivity clauses live in the signed sponsor agreement and must be checked before approving, not just before publishing",
        "States that an unfiltered published list is read as vetted programming unless the page itself says otherwise",
        "Supplies framing that asks attendees to support these independently-run events, rather than presenting them as programme",
        "States that a list published without that framing is worse than publishing no list at all",
        "Notes that an open list with no gate is a worse trade than a vetted application despite costing less, because it hands the organizer an endorsement never examined",
        "Requires an explicit non-endorsement line on the page itself",
        "Names who decides, or states explicitly that no gate is being run",
        "Requires the criteria to exist in writing before the first submission arrives if any gate is run",
        "Names apparent endorsement as an exposure the page creates and routes it to counsel",
        "States no monetary figure and names no legal instrument",
        "Presents the page and the posture for validation before publication, noting that publication is the point of no return"
      ]
    },
    {
      "id": 6,
      "prompt": "Cobalt Registry bought our \"Signature Side Event\" package at Ferrolink Conf for 18,000 EUR. It was on the rate card and they signed in January. They want to run a 150-person evening event on our Thursday, call it \"Cobalt Night @ Ferrolink\", use our wordmark and our brand colour on their invite, and have it appear in our event app. We are an incorporated non-profit and we own the marks ourselves. Our closing keynote is Friday 16:00. They are asking me to just send them the logo files. What do I send back?",
      "expected_output": "A response applying the same criteria and approval decision as any unpaid satellite, plus a deliberately scoped name licence - named grantee, named marks, one purpose, a stated end date, materials reviewed before printing - and a withdrawal right kept separate from breach.",
      "files": [],
      "expectations": [
        "Applies the same criteria set and approval decision to the paid slot as to any unpaid satellite",
        "Recommends a licensed co-branding grant for this case rather than the default non-affiliation wording",
        "Gives the reason: the organizer wants this event read as connected, which is what breaks the usual case against granting a licence",
        "Names Cobalt Registry as the grantee of the licence",
        "Names the specific marks covered rather than gesturing at \"branding\" or \"our assets\"",
        "Binds the grant to one stated purpose",
        "Gives the grant a stated end date, or states that it expires automatically rather than continuing silently into future editions",
        "Requires materials be shown to the organizer before they are printed",
        "Keeps a withdrawal right separate from any breach of the criteria, on reputational grounds",
        "States what withdrawal means in practice, including that materials already printed are the sponsor's problem",
        "Imposes adoption of a code of conduct and a named contact as a condition",
        "Deconflicts the Thursday evening slot against the published grid's own protected hours"
      ]
    },
    {
      "id": 7,
      "prompt": "Pinefield Systems Day is a 250-person community conference we run in Utrecht. Five or six user groups and a couple of companies usually run something during our two days. The trouble is Joris. He is the only organizer with time to handle this, and he also runs the local JS meetup with half the people who would be applying. He drinks with them every second Thursday. Last year he approved everything, including one thing that turned out to be a recruiting pitch. Our comms volunteer Anouk is on site all week and happy to keep a page updated. What process should we set up?",
      "expected_output": "A recommendation for an open self-registration listing rather than a vetting gate, keyed explicitly to Joris being unable to refuse without it being personal, with a maintained shared calendar justified by Anouk plus the number of satellites, and the naming and liability work still done.",
      "files": [],
      "expectations": [
        "Recommends an open self-registration listing over a vetted application process, and ties that choice to Joris being unable to refuse a request without it being personal",
        "States that a gate that never says no is a worse arrangement than an open list carrying a non-endorsement line",
        "Does not propose a review committee, a scoring rubric or extra reviewers as the fix for Joris",
        "Requires a non-endorsement line on the listing",
        "Uses support framing rather than presenting the listed events as programme",
        "Recommends a shared public calendar only because both a named maintainer (Anouk) and enough satellites exist, not because either alone is satisfied",
        "Still sets a naming rung and supplies the exact sentence satellite organizers must carry",
        "Still names the liability exposure categories and routes each one",
        "States that the liability position is deliberately not ranked against effort or value",
        "Publishes the posture rather than leaving it unstated",
        "Records the posture and its reason so the next edition starts from a decided rule rather than an argument"
      ]
    },
    {
      "id": 8,
      "prompt": "Quick one. We listed \"The Foundry Sessions\" on our fringe page at Ashgrove Tech Week. It is not our event, a local co-working space runs it, and it is an open bar. If someone falls down their stairs drunk on the Thursday night, are we on the hook? Do we need them to sign something, and how much public liability cover should we be asking them to carry? We are in Ireland if that matters.",
      "expected_output": "A refusal to answer the liability question, replaced by the named exposure categories with each one routed - to counsel, to the mark holder, to whoever holds privacy obligations - with no figure, no instrument name and no jurisdiction-specific rule stated.",
      "files": [],
      "expectations": [
        "Declines to state whether the organizer is liable",
        "States no monetary figure for insurance cover or for anything else",
        "Names no legal instrument as the answer",
        "States no Irish or other jurisdiction-specific rule, threshold or statute",
        "States explicitly that the specific rule is jurisdiction-specific",
        "Names the exposure categories at stake instead of answering the question asked",
        "Routes what happens to a person at a third party's venue to counsel",
        "Routes alcohol served by somebody else to counsel",
        "Names apparent endorsement created by listing the event as a distinct exposure",
        "Names personal data collected by the satellite organizer and routes it to whoever holds the organization's privacy obligations",
        "States that the liability position is deliberately not ranked",
        "Offers to carry a chosen category as a scored risk-register row, separately from any disclaimer wording"
      ]
    },
    {
      "id": 9,
      "prompt": "Got an email from Tilda, who runs Rustfest Baltic. She wants us to put each other in our newsletters and share a discount code, 15% each way. She also mentions that while she is in town for our event (Kaunas, October 8-10) she would like to run a half-day Rust workshop on the 9th at a co-working space ten minutes from our venue, free entry, and asks whether we would list it and whether she can say \"in partnership with Baltcon\". How should I handle this?",
      "expected_output": "An answer that splits the reciprocal promotion swap from the workshop request, handles the swap as a peer exchange with no hosting or approval involved, and puts only the 9 October workshop through the satellite approval decision including its naming rung.",
      "files": [],
      "expectations": [
        "Separates the reciprocal newsletter-and-discount swap from the workshop request and handles them differently",
        "States that the promotion swap involves no hosting and no approval by either side, and routes it away from the satellite approval machinery",
        "Treats the 9 October workshop as a satellite requiring its own approval decision",
        "Refuses \"in partnership with Baltcon\", or requires a deliberate decision on it rather than granting it as a by-product of the promotion swap",
        "Sets a naming rung for the workshop and supplies the exact sentence it must carry",
        "Checks the workshop's timing against the published grid's protected hours",
        "Imposes code-of-conduct adoption and a named on-the-day contact on the workshop only",
        "Asks Tilda to separate exactly what she is requesting: a listing, a mention, permission to use the name, floor space, or nothing",
        "States no monetary figure and names no legal instrument",
        "Records the decision and the criterion behind it",
        "Presents the answer for validation before anything is published or sent"
      ]
    },
    {
      "id": 10,
      "prompt": "Two things. First, here is our side-event application form for Halcyon Summit, 14 fields: org name, org logo upload, org website, contact email, VAT number, event name, event description (min 200 words), format, headcount, ticketed yes/no, venue, start and end time, \"why your event is a good fit\" (min 150 words), social handles. Second, here is the refusal I drafted for a company whose Wednesday product demo runs straight through our opening keynote: \"Hi Marek, we love what you're building and would really like to support it, but we're a bit worried about the timing and how it might look to some of our sponsors, so maybe let's see how the schedule shapes up and circle back closer to the date?\" Tighten both up.",
      "expected_output": "A trimmed form carrying only fields a criterion consumes plus the missing ones (named human reachable during the event, intended name and every place the marks appear, the separated ask, accessibility and alcohol), and a rewritten refusal that names the criterion, states the decision, offers the one remaining option and stops.",
      "files": [],
      "expectations": [
        "Cuts fields no criterion consumes and names which ones go, such as the VAT number, the logo upload, the social handles or the long free-text essays",
        "States that each added field costs submissions, and that what is lost is how many satellites the organizer learns about at all",
        "Keeps a named human plus a way to reach them during the event, and rejects a brand or shared alias in that field",
        "Adds what the applicant intends to call the event and every place the event's name or logo would appear",
        "Adds what the applicant is actually asking for, separated into listing, mention, permission to use the name, floor space, or nothing",
        "Adds one-line accessibility and alcohol answers",
        "Rewrites the refusal to name the criterion that decided it, the clash with the protected opening keynote",
        "Rewrites it to state the decision plainly, with no deferral and no \"circle back\"",
        "Offers the one thing still available, moving clear of the protected window to be eligible for listing, and then stops",
        "Removes the softening, the sponsor-optics explanation and the open-endedness from the refusal",
        "States that the criteria are published while individual decisions and refusals are not",
        "Keeps the refusal in the internal decision record alongside approvals"
      ]
    }
  ],
  "trigger_queries": [
    {
      "query": "A local user group wants to run a meetup the night before our conference and call it a pre-conference event. Can they?",
      "should_trigger": true
    },
    {
      "query": "Someone is selling tickets to a party using our logo. What do we do, and what should we have done?",
      "should_trigger": true
    },
    {
      "query": "We have six fringe events during our week and half of them clash with our keynotes.",
      "should_trigger": true
    },
    {
      "query": "Our platinum sponsor bought a side event. What terms does it run under?",
      "should_trigger": true
    },
    {
      "query": "Should we publish a list of the unofficial parties happening during our conference?",
      "should_trigger": true
    },
    {
      "query": "how do we handle satellite events around our conference",
      "should_trigger": true
    },
    {
      "query": "someone built a whole website called DevConf Afterparty and we had nothing to do with it",
      "should_trigger": true
    },
    {
      "query": "what do we say to people who want to throw their own thing during our event",
      "should_trigger": true
    },
    {
      "query": "do we need to approve the dinners companies are hosting during our week",
      "should_trigger": true
    },
    {
      "query": "we want a fringe programme but nobody has asked to run anything yet",
      "should_trigger": true
    },
    {
      "query": "a vendor is running a breakfast briefing in the hotel next door on our second morning",
      "should_trigger": true
    },
    {
      "query": "can a company use our name on their own meetup page",
      "should_trigger": true
    },
    {
      "query": "what should our unofficial-event policy say",
      "should_trigger": true
    },
    {
      "query": "write the disclaimer for events we didn't organise",
      "should_trigger": true
    },
    {
      "query": "three companies are running parties on our keynote night and we're losing the room",
      "should_trigger": true
    },
    {
      "query": "is it ok to let attendees organise their own dinners under our banner",
      "should_trigger": true
    },
    {
      "query": "someone printed flyers with our logo for a party in a bar and we never said yes",
      "should_trigger": true
    },
    {
      "query": "we're being asked to list a recruiting event during our conference, do we?",
      "should_trigger": true
    },
    {
      "query": "how do other conferences deal with people running stuff around them",
      "should_trigger": true
    },
    {
      "query": "our sponsor's competitor is throwing a party the same night and wants it on our site",
      "should_trigger": true
    },
    {
      "query": "draft criteria for approving third-party events during our dates",
      "should_trigger": true
    },
    {
      "query": "what's an outboarding policy",
      "should_trigger": true
    },
    {
      "query": "do we owe anything if something goes wrong at a party we listed",
      "should_trigger": true
    },
    {
      "query": "we said yes to a side event last year and now we can't get out of it",
      "should_trigger": true
    },
    {
      "query": "should we run an application form for community-run events during the conference",
      "should_trigger": true
    },
    {
      "query": "a user group wants to co-brand their meetup with us",
      "should_trigger": true
    },
    {
      "query": "who decides whether an afterparty gets on our schedule page",
      "should_trigger": true
    },
    {
      "query": "our code of conduct, does it cover the parties we didn't organise?",
      "should_trigger": true
    },
    {
      "query": "we need rules for people using our event name",
      "should_trigger": true
    },
    {
      "query": "there's a hackathon running in parallel to our conference using our hashtag and our name",
      "should_trigger": true
    },
    {
      "query": "someone asked permission to use our logo on their event page and I don't know what to say",
      "should_trigger": true
    },
    {
      "query": "how do we stop companies hijacking our conference week",
      "should_trigger": true
    },
    {
      "query": "an attendee set up a page called Unofficial ScaleFest Drinks, do we care",
      "should_trigger": true
    },
    {
      "query": "we want to publish a fringe guide handed out at check-in",
      "should_trigger": true
    },
    {
      "query": "what goes in an approval email for a community event during our conference",
      "should_trigger": true
    },
    {
      "query": "how do we refuse someone's party without it turning into a fight",
      "should_trigger": true
    },
    {
      "query": "a partner wants to run a workshop the day before ours in the same city",
      "should_trigger": true
    },
    {
      "query": "we let anyone list their event last year and it looked like we programmed it",
      "should_trigger": true
    },
    {
      "query": "our foundation owns the trademark, can we let a meetup use it",
      "should_trigger": true
    },
    {
      "query": "is there a way to tell organizers which hours not to run against",
      "should_trigger": true
    },
    {
      "query": "should we protect our closing keynote from competing evening events",
      "should_trigger": true
    },
    {
      "query": "we're getting five or six requests a week to be listed on our events page during the conference",
      "should_trigger": true
    },
    {
      "query": "a sponsor wants exclusivity over evening events during our dates",
      "should_trigger": true
    },
    {
      "query": "what do we ask people who want to run something during our event",
      "should_trigger": true
    },
    {
      "query": "we need to decide what we permit other people to run around our conference",
      "should_trigger": true
    },
    {
      "query": "write an unofficial event policy for our website",
      "should_trigger": true
    },
    {
      "query": "how do we keep a list of parties current through the conference week",
      "should_trigger": true
    },
    {
      "query": "someone ran a paid training course during our event and called it a workshop track",
      "should_trigger": true
    },
    {
      "query": "our team has no legal entity, can we sign anything with a partner event",
      "should_trigger": true
    },
    {
      "query": "last edition three things ran that we never heard about until afterwards",
      "should_trigger": true
    },
    {
      "query": "a journalist asked us about a party we had nothing to do with",
      "should_trigger": true
    },
    {
      "query": "an invite-only dinner is being advertised as open to all attendees during our conference",
      "should_trigger": true
    },
    {
      "query": "how much control should we have over what happens around our event",
      "should_trigger": true
    },
    {
      "query": "how many official social occasions should our conference run",
      "should_trigger": false
    },
    {
      "query": "should we do a welcome reception or a closing party",
      "should_trigger": false
    },
    {
      "query": "plan the evening programme for our two-day conference",
      "should_trigger": false
    },
    {
      "query": "what's our alcohol posture for the conference bar",
      "should_trigger": false
    },
    {
      "query": "decide the catering service style for our 400-person event",
      "should_trigger": false
    },
    {
      "query": "design our official attendee party",
      "should_trigger": false
    },
    {
      "query": "do we need an official mixer on night one",
      "should_trigger": false
    },
    {
      "query": "set up a ticket-discount code swap with another conference",
      "should_trigger": false
    },
    {
      "query": "another conference wants to cross-promote with us, how do we score the deal",
      "should_trigger": false
    },
    {
      "query": "newsletter mention swap between two independent meetups",
      "should_trigger": false
    },
    {
      "query": "score partner events for a reciprocal promotion exchange",
      "should_trigger": false
    },
    {
      "query": "lay our accepted talks into a published session grid",
      "should_trigger": false
    },
    {
      "query": "where should lunch go in a two-track schedule",
      "should_trigger": false
    },
    {
      "query": "how long should our sessions be",
      "should_trigger": false
    },
    {
      "query": "avoid clashes between our own tracks",
      "should_trigger": false
    },
    {
      "query": "write our code of conduct",
      "should_trigger": false
    },
    {
      "query": "who should be on the code of conduct response team",
      "should_trigger": false
    },
    {
      "query": "how do we handle a harassment report during the event",
      "should_trigger": false
    },
    {
      "query": "deliver everything our gold sponsor was promised",
      "should_trigger": false
    },
    {
      "query": "turn our sponsorship sale into a term sheet for our lawyer",
      "should_trigger": false
    },
    {
      "query": "build the sponsorship rate card for our conference",
      "should_trigger": false
    },
    {
      "query": "cold email a sponsor prospect for our event",
      "should_trigger": false
    },
    {
      "query": "what do sponsors actually get out of sponsoring us",
      "should_trigger": false
    },
    {
      "query": "find a second venue for our breakout rooms",
      "should_trigger": false
    },
    {
      "query": "negotiate the venue contract for our conference",
      "should_trigger": false
    },
    {
      "query": "build the risk register for our event",
      "should_trigger": false
    },
    {
      "query": "what insurance stack does our conference need",
      "should_trigger": false
    },
    {
      "query": "run a private dinner for our named guests alongside the conference",
      "should_trigger": false
    },
    {
      "query": "how do we assemble the seat list for the VIP dinner",
      "should_trigger": false
    },
    {
      "query": "barter deal with a podcast to promote our event",
      "should_trigger": false
    },
    {
      "query": "community partner visibility swap, no cash changes hands",
      "should_trigger": false
    },
    {
      "query": "design the 1:1 business meeting programme for our trade show",
      "should_trigger": false
    },
    {
      "query": "lay out the expo floor so traffic passes every booth",
      "should_trigger": false
    },
    {
      "query": "take our attendees into a host company's offices for the day",
      "should_trigger": false
    },
    {
      "query": "design the hands-on workshop day for our conference",
      "should_trigger": false
    },
    {
      "query": "write the minute-by-minute run of show for day one",
      "should_trigger": false
    },
    {
      "query": "build the attendee acquisition plan for our conference",
      "should_trigger": false
    },
    {
      "query": "what should we post on social during the CFP window",
      "should_trigger": false
    },
    {
      "query": "set up press accreditation for bloggers at our event",
      "should_trigger": false
    },
    {
      "query": "write the challenge brief for our hackathon",
      "should_trigger": false
    },
    {
      "query": "how should we split the hackathon prize pool across places",
      "should_trigger": false
    },
    {
      "query": "write the pre-event reminder email sequence for attendees",
      "should_trigger": false
    },
    {
      "query": "keep our community chat alive between editions",
      "should_trigger": false
    },
    {
      "query": "should we add a meetup series alongside our conference",
      "should_trigger": false
    },
    {
      "query": "should we run a multi-city roadshow or a single-city user conference",
      "should_trigger": false
    },
    {
      "query": "what is our company event budget funded to accomplish",
      "should_trigger": false
    },
    {
      "query": "plan a company offsite for our engineering team",
      "should_trigger": false
    },
    {
      "query": "find the best side events to attend at a conference I'm flying to next month",
      "should_trigger": false
    },
    {
      "query": "review this affiliate partnership agreement before I sign it",
      "should_trigger": false
    },
    {
      "query": "write a trademark usage policy for our open source project's logo",
      "should_trigger": false
    },
    {
      "query": "how do we open a satellite office in another country",
      "should_trigger": false
    },
    {
      "query": "coordinate breakout sessions inside our company all-hands",
      "should_trigger": false
    },
    {
      "query": "what's the best event management software for tracking RSVPs",
      "should_trigger": false
    }
  ]
}
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall