Skip to content

samber/dev-event-organizer-skills / skills/event-sponsor-fulfillment

event-sponsor-fulfillment

Verified

Deliver everything a signed event sponsor was promised, from countersignature to the post-event report - the tier-by-perk fulfillment matrix built from the signed agreement, payment-gated perk release, sponsor asset collection against deadlines, the day-of sponsor experience (setup, shipping, staffing, A/V), consented lead capture such as an opt-in raffle, and the post-event sponsor report that anchors the renewal ask. Use whenever the user mentions onboarding a signed sponsor, tracking sponsor deliverables, booth logistics, sponsor logo placement, or a post-event sponsor report or recap - even without saying "fulfillment". Do NOT use for the sale - use samber/dev-event-organizer-skills@event-sponsor-outreach; use samber/dev-event-organizer-skills@event-sponsor-renewal for the renewal ask.

evals/evals.json

View on GitHub
{
  "skill_name": "event-sponsor-fulfillment",
  "evals": [
    {
      "id": 1,
      "prompt": "Harborline DevSummit is on 14 November and we finally have four sponsors signed. Verilume Systems took Platinum at $14,000 and paid on 2 October. Klarstack took Gold at $6,000, invoice went out 9 October, nothing received. Nordpath Analytics also took Gold at $6,000 and wired half of it last week, said the rest comes when their PO clears. Bitmoor took Silver at $2,000, paid. I want to get moving tonight: put all four logos up on the website, send everyone a welcome pack. For the perk lists I'll just copy what's in our prospectus PDF since that's what they bought anyway. Can you set me up with a tracker and the welcome emails?",
      "expected_output": "A tier-by-perk fulfillment matrix built from the four signed agreements with per-cell states, a payment gate that releases Verilume and Bitmoor while holding Klarstack and Nordpath, communicated holds via a named liaison, and a refusal to derive the perk list from the prospectus.",
      "files": [],
      "expectations": [
        "Builds a tier-by-perk matrix with perks as rows and tiers or sponsors as columns, not a single flat list of perks",
        "Gives each matrix cell a state along a promised, scheduled, delivered, evidenced progression",
        "States the promise column quotes each signed agreement, and declines to build the perk list from the prospectus PDF",
        "Explains that the prospectus is the sales document while custom-negotiated deltas exist only in the signed contract",
        "Holds every Klarstack perk, including the website logo, until the invoice is paid in full",
        "Treats Nordpath Analytics's half payment as not-paid-in-full and holds their perks too",
        "Releases perks for Verilume Systems and Bitmoor, whose payments are confirmed",
        "Communicates each hold to the affected sponsor through their liaison, naming what is queued and why",
        "Rejects letting an unpaid sponsor discover the hold at the venue door or at setup time",
        "Names one liaison per sponsor",
        "Asks for the hard pre-event deadlines (printer dates, program lock, newsletter schedule) rather than sequencing work from the 14 November event date"
      ]
    },
    {
      "id": 2,
      "prompt": "Ten weeks until Brackenmoor Tech Days. Our lanyard printer wants final artwork in six days or we lose the slot, the swag bag print run closes in three weeks, the printed program locks five weeks out, and our newsletter goes out every Tuesday. Cindercloud bought the lanyard tier for $2,500 and their invoice is still open, no payment. Meanwhile Tesserly (Silver, paid) emailed asking if we can kick off with their social posts first since those are quick wins and we have plenty of time before the event. What order should I work through all this?",
      "expected_output": "A delivery order sequenced by earliest hard deadline with printed surfaces ahead of digital ones, the printer date named as the fulfillment clock, Cindercloud's artwork still held behind payment with the deadline communicated to them, and a dated asset table.",
      "files": [],
      "expectations": [
        "Sequences perk delivery by earliest hard deadline first, not by ease of execution or by the event date",
        "States the fulfillment clock starts at the printer's six-day date, not the ten-week event date",
        "Places printed surfaces (lanyard, swag bag, signage) ahead of digital ones (newsletter, social, slides)",
        "Declines to start with Tesserly's social posts on the grounds that they are quick",
        "States a logo missed on a printed run is unfixable afterwards and becomes a make-good negotiation instead of a perk",
        "Holds Cindercloud's lanyard artwork behind payment rather than sending it to the printer on an open invoice",
        "Tells Cindercloud the print deadline explicitly so they can decide in time, instead of silently letting the slot lapse",
        "Gives each asset a needed-by date tied to a named driver such as the printer date, program lock, or newsletter send",
        "Sorts the deadline table by date and treats its top row as the clock",
        "Shares the sponsor-facing part of the deadline table with each sponsor"
      ]
    },
    {
      "id": 3,
      "prompt": "We run Tidewater Ops Meetup, all volunteers, about 220 people show up, and our own published sponsor rules say we do not share attendee contact details. Ferrolane signed at our top tier, $9,000, biggest cheque we have ever had. Their partner manager emailed: they want the attendee email list post-event, and if that is a problem they suggest we just add a little 'opt in to Ferrolane's newsletter' checkbox on the raffle entry form they are running at their booth. They also offered to bring their own badge scanners so we do not have to do anything. I really do not want to lose them. What can I actually offer?",
      "expected_output": "A refusal of the attendee list, the newsletter checkbox and the badge scanners at a community-run event, with aggregate demographics offered as the default and a properly consented raffle as the higher-value option, including its consent statement, single-sponsor hand-off and deletion step.",
      "files": [],
      "expectations": [
        "Refuses the bulk attendee list outright rather than parking it as a last-resort or lower-priority option",
        "Refuses sponsor badge scanning at this community-run event",
        "States the refusal holds even for the largest sponsor, whose choice is the remaining options or no deal",
        "Identifies the newsletter opt-in checkbox on the raffle form as the banned bulk-capture move in disguise, not a middle ground",
        "Offers aggregate demographics (role mix, seniority mix, company-size mix, no names) as the default answer",
        "Offers a consented opt-in raffle as the higher-value option where that perk was sold",
        "States plainly at the point of entry what is collected and that it goes to Ferrolane specifically",
        "Hands the raffle entries to Ferrolane only",
        "Deletes the organizer's own copy of the entries after hand-off",
        "States the entries never merge into any organizer list and the raffle never substitutes for an attendee list",
        "Briefs the volunteers that the raffle and the aggregate demographics document are the only data hand-offs that exist",
        "Notes the raffle carries a compliance cost the aggregate document does not, and that a mishandled hand-off cannot be walked back"
      ]
    },
    {
      "id": 4,
      "prompt": "Ridgewire Conf wrapped Saturday, 310 attendees, four sponsors. Auxograph was our headline sponsor at $12,000 and on the exploratory call back in June they told us straight out that success for them was five qualified hiring conversations. Here is what we have for them: their booth raffle collected 34 entries, their two booth staff logged 12 conversations in their notebook, and their job post on our site got 61 views. We also completely forgot to put their logo on the rotating break slides, nobody noticed until I was going through my notes yesterday. Our marketing volunteer drafted something that opens with '500,000+ brand impressions across the weekend' and closes asking them to commit to the same tier for next year. She wants to polish it over the next few weeks. Thoughts before I send?",
      "expected_output": "A report sent inside 72 hours, scored against Auxograph's own five-hiring-conversations metric, carrying the real small numbers with interpretation labels, self-disclosing the missed break-slide logo with a make-good, dropping the invented impressions figure and the hard renewal ask, and closing with a renew/renegotiate/drop read handed to the outreach motion.",
      "files": [],
      "expectations": [
        "Sends the report within 72 hours of the event rather than polishing it over the following weeks",
        "Scores Auxograph's outcomes against their own stated metric of five qualified hiring conversations, not a generic one",
        "Reports the real figures (34 raffle entries, 12 booth conversations, 61 job-post views) rather than inflating or omitting them for being small",
        "Rejects the '500,000+ brand impressions' line as an invented, unmeasurable reach number",
        "States that an invented reach number damages the credibility of the real numbers printed beside it",
        "Labels what each number does and does not show, for example that raffle entries show booth draw rather than lead quality",
        "Names the missed break-slide logo in the report itself, before Auxograph discovers it",
        "Attaches a make-good to the slipped break-slide perk",
        "Includes a delivered-versus-promised table with per-perk evidence such as a photo, link or screenshot",
        "Includes aggregate audience data (attendance, role, seniority, company-size mix) and no attendee names",
        "Removes the hard renewal ask from the close, leaving next edition as dates and a light note",
        "Produces a renew, renegotiate or drop read on Auxograph and hands it with the report to the sponsor outreach motion",
        "Does not build a renewal follow-up cadence or sequence inside this work"
      ]
    },
    {
      "id": 5,
      "prompt": "Quillbase is sponsoring our hackathon (Friday evening through Sunday afternoon) at $7,500. Their package includes a 45-minute sponsored workshop slot plus $2,000 of API credits they are giving to the teams. Their marketing lead came back with: they would like the slot on Sunday because that is when their people are free-ish, their team is fully remote so instead of sending anyone they will give us a really thorough PDF walkthrough for participants, and the proposed title is 'Getting production-ready with Quillbase'. Honestly their brand is a perfect fit for our crowd and the topic sounds right, so I was going to just say yes to all of it. Anything I should push back on?",
      "expected_output": "A hard requirement for a named on-site representative for the credits perk (with an independent-user fallback), a content review of the sponsored slot rather than brand-fit approval, the workshop moved off the final day, and staffing guidance passed to the sponsor.",
      "files": [],
      "expectations": [
        "Makes a named on-site representative a hard condition of the API-credits perk rather than a nice-to-have",
        "Rejects the PDF walkthrough as a substitute for a live person when participants hit friction under time pressure",
        "States that a tool with nobody available to troubleshoot it gets abandoned the moment it stops working",
        "Offers an enthusiastic independent user of the tool as the on-site point of contact when no company representative can attend",
        "Reviews the actual content of the sponsored slot before confirming it, not just the sponsor's brand and topic",
        "Flags that a 'getting production-ready' session asking a time-boxed hackathon audience to invest hours works against the event's own format",
        "Refuses to confirm the sponsored session on brand or logo fit alone",
        "Moves the workshop off Sunday to the Friday or Saturday of the event",
        "Passes along guidance to send someone who can tell the company's story and participate with the community rather than a sales representative",
        "Collects the workshop title, abstract and speaker name as intake assets against a deadline"
      ]
    },
    {
      "id": 6,
      "prompt": "Steelharbor Dev Days has nine sponsors signed this year, up from four. There are two of us organizing and realistically we each have about four hours a week for this. Mix is: Marrowgate took Platinum and it is their first time sponsoring anything of ours, Pellucid Labs has sponsored all four editions and already told me they are in for next year too, and the other seven are small Silvers who have all done it before and know the drill. My plan was to book a 45-minute kickoff call with each of the nine so nothing falls through the cracks. Sound right?",
      "expected_output": "An onboarding menu ranked by value per unit of effort, checklist emails as the default for the repeat Silvers, kickoff calls promoted only for Marrowgate and Pellucid Labs with the condition named, and an intake form recommended at this roster size.",
      "files": [],
      "expectations": [
        "Ranks the onboarding options explicitly by value returned per unit of effort rather than by which is cheapest",
        "Names the checklist email as the default instrument for the bulk of the roster",
        "Declines the plan of booking a kickoff call with all nine sponsors",
        "Promotes a kickoff call for Marrowgate as a top-tier, first-time sponsor and names that as the promotion condition",
        "Promotes a kickoff call for Pellucid Labs as a compounding multi-edition relationship and names that as the promotion condition",
        "Recommends an intake form at nine sponsors, citing roughly three sponsors as the point where it repays its setup cost",
        "Generates each welcome email from that sponsor's own column of the fulfillment matrix",
        "Writes the welcome email against specific named program moments the sponsor's team can put in a calendar, not a flat benefits list",
        "Keeps the accompanying asset kit deliberately minimal (photos, a presentation template, one contact-request email) rather than a sprawling toolkit",
        "States the ranking is a default that the four-hours-a-week effort ceiling and the compounding relationship re-rank"
      ]
    },
    {
      "id": 7,
      "prompt": "Our published prospectus for Calderwood Summit says Gold is capped at three sponsors and lanyard branding is exclusive to the Lanyard tier. We have all three Golds signed. Now Ombrelle Data has come in wanting Gold too, at full price, and separately our Platinum sponsor Harkwood asked whether their logo could also go on the lanyard since they are paying nearly double everyone else. We are about $11,000 behind on sponsorship revenue for this edition. Realistically nobody reads the caps page of the prospectus. Can I make both of these work?",
      "expected_output": "A refusal of both the fourth Gold and the shared lanyard surface, grounded in the published caps the matrix must honor, with a non-breaching alternative offered instead of a quiet oversell.",
      "files": [],
      "expectations": [
        "Refuses to sell a fourth Gold against a published cap of three",
        "Refuses to add Harkwood's logo to the lanyard, which was sold as the Lanyard tier's exclusive surface",
        "States the fulfillment matrix must honor every published cap, covering exclusive surfaces, premium placements and pitch slots",
        "Describes an oversold exclusive surface as one promise two sponsors hold at the same time",
        "States that delivering an oversold exclusive to one sponsor breaks it for the other in public",
        "Rejects 'nobody reads the caps' as a reason to breach one",
        "Offers a route that does not breach the published inventory, such as a non-exclusive surface, an add-on, or first pick at the next edition",
        "Declines to treat the $11,000 revenue shortfall as grounds to override published inventory"
      ]
    },
    {
      "id": 8,
      "prompt": "Nine days out from Alderfen Conf and three different sponsors have emailed this week asking basically the same things: when can they get in to set up, how do they ship their boxes to the venue, and is there power at the tables. I was going to write one FAQ page on our website and just reply to all of them with the link so I stop answering the same email. We already did the whole expo floor layout a few weeks back, tier specs, setup schedule, all of that. Is the FAQ page enough?",
      "expected_output": "An answered logistics FAQ pushed to sponsors before they ask, direct organizer contact scheduled for the venue-specific items, a per-sponsor day-of brief a week out, and a doors-open booth walk photographing placements as matrix evidence.",
      "files": [],
      "expectations": [
        "Sends each sponsor an already-answered logistics FAQ rather than waiting for them to ask",
        "Covers the setup and teardown window, shipping to the venue, whom to send, electricity, WiFi and additional A/V equipment",
        "Rejects a self-service FAQ page as sufficient because shipping, power and A/V are venue-specific and route to direct organizer contact",
        "Puts a logistics call or thread with each sponsor's on-site lead on the fulfillment calendar",
        "Produces one day-of brief per sponsor about a week out, carrying booth location and size, staff badge count and pickup, scheduled slots, an on-site organizer phone contact and teardown rules",
        "Takes the booth specs and setup schedule from the existing floor layout work instead of re-deriving or restating them",
        "Walks the booths at doors-open with the matrix in hand, photographing premium placements, banners and signage as cell evidence"
      ]
    }
  ],
  "trigger_queries": [
    { "query": "We just countersigned four sponsorship agreements. What happens next?", "should_trigger": true },
    { "query": "How do I track what each sponsor was promised versus what we've actually delivered?", "should_trigger": true },
    { "query": "Our Gold sponsor hasn't paid yet but their logo is due at the printer Friday.", "should_trigger": true },
    { "query": "Write the post-event reports for our sponsors.", "should_trigger": true },
    { "query": "A sponsor is asking for the attendee email list. What can we actually give them?", "should_trigger": true },
    { "query": "I need a welcome email for each sponsor listing the assets they owe us and when.", "should_trigger": true },
    { "query": "What do I send sponsors about setup times, shipping and power before the event?", "should_trigger": true },
    { "query": "Our sponsor wants to run a raffle at their booth. How do we handle the entries?", "should_trigger": true },
    { "query": "Two sponsors both think they got the lanyard branding. Help.", "should_trigger": true },
    { "query": "How soon after the event do I need to send sponsors something?", "should_trigger": true },
    { "query": "The event's over. How do I make the case for them to come back next year?", "should_trigger": true },
    { "query": "One of our sponsors' logos never made it onto the break slides and the event is done.", "should_trigger": true },
    { "query": "I need a deadline table for sponsor logos, blurbs and job posts.", "should_trigger": true },
    { "query": "How do I onboard a sponsor once the contract is signed?", "should_trigger": true },
    { "query": "What should go in a sponsor recap after a conference?", "should_trigger": true },
    { "query": "Sponsor is sending three account executives to staff their booth. Is that fine?", "should_trigger": true },
    { "query": "We sold a sponsored workshop slot. What do I need from them and by when?", "should_trigger": true },
    { "query": "Who do I chase for the sponsor's vector logo and what's my cutoff?", "should_trigger": true },
    { "query": "Can I let sponsors scan badges at a community-run event?", "should_trigger": true },
    { "query": "Our biggest sponsor asked what ROI we can show them afterwards.", "should_trigger": true },
    { "query": "Help me build the checklist for delivering everything we sold to sponsors.", "should_trigger": true },
    { "query": "I have nine sponsors and two volunteers. How do I collect all their assets without drowning?", "should_trigger": true },
    { "query": "Sponsor paid half the invoice. Do we give them the booth?", "should_trigger": true },
    { "query": "How do I prove to a sponsor we actually put their banner up?", "should_trigger": true },
    { "query": "The sponsor asked to add a newsletter opt-in to their raffle form.", "should_trigger": true },
    { "query": "A company wants our attendee list in exchange for upgrading a tier.", "should_trigger": true },
    { "query": "What goes in the brief we send sponsors a week before doors open?", "should_trigger": true },
    { "query": "Should each sponsor get an individual report or one generic recap?", "should_trigger": true },
    { "query": "We promised a pitch slot and forgot to schedule it. Event is next week.", "should_trigger": true },
    { "query": "How do I decide whether to keep, renegotiate or let go of each sponsor next edition?", "should_trigger": true },
    { "query": "Sponsor is giving API credits to participants but doesn't want to send anyone on site.", "should_trigger": true },
    { "query": "Getting a lot of last-minute questions from sponsors about WiFi and A/V.", "should_trigger": true },
    { "query": "Our sponsorship perks are scattered across five email threads. I need a system.", "should_trigger": true },
    { "query": "Is it okay to just thank sponsors by email and leave it at that?", "should_trigger": true },
    { "query": "What photos do I need to take of sponsor stuff during the event?", "should_trigger": true },
    { "query": "We're a volunteer-run meetup and a sponsor wants lead retrieval scanners.", "should_trigger": true },
    { "query": "Build the target list of companies to approach for sponsorship.", "should_trigger": false },
    { "query": "When should I email prospective sponsors relative to their fiscal year?", "should_trigger": false },
    { "query": "Write a cold email to a company we want as a sponsor.", "should_trigger": false },
    { "query": "How many follow-ups before I drop a sponsor lead?", "should_trigger": false },
    { "query": "How should I run the exploratory call with a potential sponsor?", "should_trigger": false },
    { "query": "A prospect says our sponsorship is too expensive. How do I respond?", "should_trigger": false },
    { "query": "What should we charge for the top sponsorship tier?", "should_trigger": false },
    { "query": "How many sponsorship tiers should our rate card have?", "should_trigger": false },
    { "query": "How do we value an in-kind sponsorship against a cash one?", "should_trigger": false },
    { "query": "Write our discount and negotiation policy before we start selling.", "should_trigger": false },
    { "query": "What clauses belong in our sponsorship contract?", "should_trigger": false },
    { "query": "What refund does a sponsor get if they withdraw two weeks out?", "should_trigger": false },
    { "query": "Draft the category exclusivity terms for our headline tier.", "should_trigger": false },
    { "query": "Design the sponsorship prospectus we send to prospects.", "should_trigger": false },
    { "query": "Why would any company sponsor a 200-person meetup?", "should_trigger": false },
    { "query": "What can we honestly promise a sponsor whose goal is recruiting?", "should_trigger": false },
    { "query": "Lay out the expo floor so attendee traffic passes every booth.", "should_trigger": false },
    { "query": "What table size, power and signage does each booth tier get?", "should_trigger": false },
    { "query": "Write the floor-wide booth conduct rules for exhibitors.", "should_trigger": false },
    { "query": "Build the master setup and teardown schedule for the exhibition hall.", "should_trigger": false },
    { "query": "Design the attendee check-in desk and badge pickup flow.", "should_trigger": false },
    { "query": "Should our attendee badges carry QR codes at all?", "should_trigger": false },
    { "query": "Set up 1:1 meeting scheduling between attendees and vendors.", "should_trigger": false },
    { "query": "How many booked meetings can a package honestly commit to?", "should_trigger": false },
    { "query": "Run the organizing team's retrospective on last weekend's edition.", "should_trigger": false },
    { "query": "Build the budget spreadsheet for a 400-person conference.", "should_trigger": false },
    { "query": "Swap newsletter mentions with another city's meetup organizer.", "should_trigger": false },
    { "query": "Write the post-event attendee survey.", "should_trigger": false },
    { "query": "Plan the social media calendar for the three months before the event.", "should_trigger": false },
    { "query": "What do we owe our speakers and how do we look after them?", "should_trigger": false },
    { "query": "Find a catering vendor for 300 people with dietary options.", "should_trigger": false },
    { "query": "How do I onboard volunteers in the week before doors open?", "should_trigger": false },
    { "query": "Write the code of conduct for our conference.", "should_trigger": false },
    { "query": "Set up a GitHub Sponsors page with tiers for my open source library.", "should_trigger": false },
    { "query": "Build the order fulfillment workflow for our merch store.", "should_trigger": false },
    { "query": "Design ad packages for our developer podcast.", "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