samber/dev-event-organizer-skills / skills/event-sponsor-agreement
event-sponsor-agreement
VerifiedTurn a sold event sponsorship into a term sheet a lawyer can review - never a signable contract or legal advice. Covers the clause checklist an organizer hands to counsel - a deliverables schedule mirroring the sold tier, payment and late-fee terms, sponsor-withdrawal refunds plus the narrower organizer-cancels remedy, a force-majeure remedy, category exclusivity bounded by published caps, liability and insurance, a code-of-conduct clause with an ejection right, an editorial-independence clause denying sponsors program control, mutual logo licensing, term and renewal. Use whenever the user mentions a sponsorship agreement or contract, sponsor payment or cancellation terms, exclusivity, or a force-majeure clause - even if they never say "agreement". Do NOT use to set prices - use samber/dev-event-organizer-skills@event-sponsor-pricing.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 29.7 KB |
| evals/evals.json | config | 42.8 KB |
| references/clause-library.md | markdown | 18.8 KB |
| references/exclusivity-and-renewal.md | markdown | 6.9 KB |
| references/term-sheet-template.md | markdown | 10.7 KB |
evals/evals.json
View on GitHub{
"skill_name": "event-sponsor-agreement",
"evals": [
{
"id": 1,
"prompt": "We run KernelDays Bordeaux, a volunteer-organised systems conference, 320 attendees last year. Hexabyte Cloud just said yes to our Gold tier at 7,500 EUR - that is the price on our rate card, and Gold there is logo on the website sponsor page, logo on the lanyard, a 3x2m table in the hallway, and 4 full passes. We are not incorporated; the money lands in our treasurer's personal bank account. Their procurement wants paper by Friday. Write the sponsorship contract.",
"expected_output": "A term sheet for counsel review - not a contract - opening with the not-legal-advice constraint, flagging the unincorporated entity as a structural exposure, carrying a deliverables exhibit built from the Gold rate card, and drafting sponsor withdrawal and organizer cancellation as two separate clauses.",
"files": [],
"expectations": [
"Presents the output as a term sheet for a lawyer to review, and states inside the document itself that it is not a contract and not legal advice",
"Repeats the not-a-contract and not-legal-advice statement at the handoff to counsel, not only once at the top",
"Flags the unincorporated organizer as a structural exposure the document cannot draft around, and names the personal liability the individuals carry",
"Routes the legal-entity question to samber/dev-event-organizer-skills@event-team-structure",
"Declines to produce a signable document, and presents any signature block only as a placeholder pending counsel review",
"Establishes the jurisdiction and governing law and identifies the counsel who will review, before drafting clause language",
"Produces a deliverables exhibit with one row per sold perk covering the website logo, the lanyard logo, the 3x2m table and the 4 passes",
"Gives each exhibit row a specification, a delivery surface, a hard deadline and a named responsible party",
"Carries the 7,500 EUR fee and the four Gold perks through unchanged, and adds no perk that was not on the rate card",
"Drafts sponsor withdrawal and organizer cancellation as two separate clauses rather than one mutual cancellation section",
"States that the organizer-cancellation remedy is narrower than the sponsor-withdrawal remedy",
"Names an explicit remedy in words for the force-majeure branch rather than leaving it implied",
"Includes a code-of-conduct clause binding the sponsor's own staff, carrying an ejection right and a no-refund consequence",
"States that the Friday deadline cannot displace counsel review, and that the term sheet must reach counsel before the sponsor is asked to sign"
]
},
{
"id": 2,
"prompt": "Quick one. ObservaCon is on 26 March, we are at 600 attendees. One of our Silver sponsors, Meridian Metrics, paid their 4,000 GBP in full and is now making noises about pulling out because their marketing budget got frozen. We have nothing written about refunds at all, which I now realise is a problem. What should our refund policy say? I would rather keep some flexibility so we can be generous with the sponsors we like and firm with the ones we do not.",
"expected_output": "A refusal of the requested discretionary refund posture, a recommended dated two-tier cutoff with the other two postures presented and ranked, plus a separate and narrower organizer-cancellation clause.",
"files": [],
"expectations": [
"Refuses a discretionary or undated refund clause and states that every published example names either a date or none",
"Grounds the refusal in NetOne v. Panache Destination Mgmt., where a vague clause was read against the party hoping it meant more than it said",
"Recommends the two-tier cutoff - a refund above a dated line, none below it - as the default posture",
"Presents the hard no-refund posture as a real and widely used option rather than dismissing it",
"Presents the graduated multi-tier ladder as the option the efficiency ordering starves, and names the conditions that would promote it",
"States that the graduated ladder and the two-tier cutoff tie on deal-closing value, because procurement checks whether a refund exists and by which date rather than how many steps the ladder has",
"Gives a dated example schedule anchored to a real published conference calendar, such as 75% at 120 days, 50% at 80 days and none after",
"Requires written notice measured against a named date",
"Drafts the organizer-cancellation remedy as a separate clause rather than mirroring the sponsor-withdrawal terms",
"Describes the organizer-cancellation remedy as pro-rata net of expenses already incurred, or zero after a cutoff",
"States that the refund-posture ranking is a default that shifts with the organizer's leverage and effort ceiling rather than a rule",
"Does not re-price the 4,000 GBP Silver tier or offer a discount as a substitute for the refund clause",
"Marks the output as a term sheet for counsel rather than a contract or legal advice"
]
},
{
"id": 3,
"prompt": "Writing the sponsorship terms for PlatformNight, our monthly platform-engineering meetup in Manchester. It is 150 people in a bar's function room. Sponsors pay 900 GBP up front for the evening - bar tab covered, logo on the meetup page, five minutes on stage. What do we put in for force majeure? I copied this from a template: 'Neither party shall be liable for any failure or delay in performance due to causes beyond its reasonable control, including acts of God, war, terrorism, strike, or government action. The parties shall discuss an equitable resolution in good faith.' Is that fine?",
"expected_output": "A rejection of the pasted clause on four named grounds, a separated trigger list and remedy, an expanded trigger list naming pandemic and epidemic, and a remedy stated in words for the cancelled, postponed and virtual branches.",
"files": [],
"expectations": [
"Rejects the pasted clause and identifies that it names no remedy",
"Identifies that 'discuss an equitable resolution in good faith' is the silence NetOne v. Panache read as no refund",
"Contrasts NetOne, where the refund was denied on silent text, with Sanders v. Edison Ballroom, where the refund was ordered on explicit text, as the same doctrine producing opposite outcomes",
"States the 45,219.28 USD deposit figure returned in Sanders, or otherwise cites that case as ordering the deposit back because the clause expressly said so",
"Identifies that the pasted clause's trigger list is generic and names neither pandemic nor epidemic",
"Identifies that the pasted clause is symmetric, and states that the organizer-side and sponsor-side remedies must be drafted separately",
"Treats the trigger list and the remedy as two separate drafting decisions",
"Produces an expanded trigger list that expressly names pandemic and epidemic alongside the physical events",
"Names a remedy in words for every branch: event cancelled, event postponed, and event converted to virtual",
"Recommends the pro-rata net of documented expenses remedy as the default at the community pole, given a meetup with no reserve to absorb a full refund",
"Presents the sponsor-elected credit-or-refund remedy with a dated election window as the higher-effort option, and names the conditions that would promote it",
"Presents 'no obligation to refund any part' as a real published position while naming its cost in negotiation and goodwill",
"Notes that a duration-triggered termination right, letting either party terminate once force majeure has prevented performance for a set number of days, composes with the chosen remedy rather than replacing it",
"States that the output is a term sheet for counsel review, not a contract and not legal advice"
]
},
{
"id": 4,
"prompt": "TraceCon sells Gold at 12,000 USD and our published prospectus says Gold is capped at 3 sponsors, Silver at 6, Bronze at 20. NimbusTrace wants category exclusivity in observability and they want it locked for three editions. They are at Gold. They have offered an extra 4,000 USD for it. Draft the exclusivity clause.",
"expected_output": "An exclusivity section that refuses to promise exclusivity at a tier capped at three, carries all three enforceability elements, defines the category by list plus exclusions plus carve-outs, replaces the three-edition grant with a right of first refusal, and routes the premium to the pricing skill.",
"files": [],
"expectations": [
"States that the contract's exclusivity language may never be looser than the cap the prospectus already published",
"Names the conflict between the word exclusive and a Gold tier that admits three sponsors, and refuses to promise exclusivity at that tier as published",
"Requires all three enforceability elements together: a specific category definition, a stated duration and channel scope, and an explicit breach remedy",
"States that a clause missing any one of the three should not be drafted at all",
"Defines the category as a named list plus named exclusions rather than the single noun observability",
"Names the definitional trap of a narrow product versus the broader category the same clause could be read to include, such as observability versus developer tooling",
"Writes in a carve-out for venue-operated concessions",
"Writes in a carve-out for pre-existing media or community partnerships signed before the exclusivity deal",
"Specifies the channel scope across which exclusivity applies, covering surfaces such as on-site, website, newsletter, stream and social",
"Specifies a defined refund percentage or equivalent remedy if the organizer sells a competitor anyway",
"Declines the flat three-edition grant and proposes a right of first refusal on renewal instead",
"States that exclusivity should not outlast the paid tier's own term by default",
"Refuses to set or validate the 4,000 USD premium and routes the pricing decision to samber/dev-event-organizer-skills@event-sponsor-pricing",
"Does not invent a tighter cap at drafting time to make the exclusivity claim work"
]
},
{
"id": 5,
"prompt": "60-person hackathon, Saturday only, in a coworking space that carries its own public liability policy. Two sponsors: one gives us 1,500 USD and a swag bag, the other sends two mentors and buys the pizza. Do we need to make them carry insurance? Our template has a big insurance section with 1M/2M limits and I do not know whether I should delete it.",
"expected_output": "A recommendation of no sponsor-carried insurance, stated explicitly in the term sheet as a decided position, with the 1M/2M figure placed at its real threshold and the promotion conditions for layered coverage named.",
"files": [],
"expectations": [
"Recommends no sponsor-carried insurance for this event and treats it as a decided position rather than an omission",
"Requires the term sheet to state explicitly that no sponsor cover is required, so a reviewer can see the choice was made rather than forgotten",
"Grounds the recommendation in the venue's or organizer's own master policy already covering the room at this scale",
"Rejects keeping the 1M/2M clause without a certificate deadline and a gate, and states that an uncollected requirement is worse than no clause because it creates a false belief the exposure was transferred",
"Places the 1,000,000 per occurrence / 2,000,000 aggregate commercial general liability figure at the threshold where sponsors staff a booth or bring physical demos, not at this scale",
"Names the conditions that would promote layered coverage: alcohol served, sponsor demos with physical risk, sponsor-supplied vehicles or heavy equipment, or a venue contract flowing the requirement down",
"Asks what physically happens at the event that an insurer would care about before settling the insurance rung",
"Checks whether the coworking space's own contract already flows an insurance requirement down to sponsors",
"Applies the same insurance decision to the in-kind sponsor rather than treating mentors and pizza as outside the clause",
"States that the insurance ranking is a default that shifts with the event's pole and the effort ceiling rather than a rule",
"Keeps the output as a term sheet for counsel review rather than finished clause language to sign"
]
},
{
"id": 6,
"prompt": "DriveStack Summit, 900 attendees, two-day expo hall at a convention centre. One sponsor, Voltway, wants to park an electric van inside the hall as their booth. Another is pouring cocktails at their stand on the Thursday evening. Our venue contract says exhibitors must name the convention centre as additional insured with 1M per occurrence. What insurance do we put in the sponsor agreement, and when do we need the paperwork?",
"expected_output": "A layered insurance requirement keyed to the vehicle and the alcohol, sitting on top of the 1M/2M CGL base, with the venue requirement flowed down, the certificate tied to contract execution and a booth-hold gate.",
"files": [],
"expectations": [
"Selects layered coverage rather than the baseline commercial general liability rung, keyed to the vehicle inside the hall and the alcohol served",
"Names the additional layers: auto liability, workers' compensation and employer's liability, and liquor or product liability",
"Keeps commercial general liability at 1,000,000 per occurrence / 2,000,000 aggregate as the base layer beneath the added lines",
"Flows the venue contract's requirement down to sponsors and names the convention centre as an additional insured alongside the organizer",
"Ties the certificate deadline to contract execution rather than to event-day arrival",
"Adds a gate holding the booth until the certificate arrives",
"States that layered coverage is the highest-effort and highest-compliance-cost rung, picked here only because the promotion condition fired",
"Names the verification risk that a missing or wrongly worded additional-insured endorsement is discovered only after an incident, when it can no longer be fixed",
"Notes that a sponsor objecting to year-round cover can buy a compliant single-event policy for well under a hundred dollars",
"Marks the insurance section with an explicit counsel flag where the wording is jurisdiction- or policy-dependent",
"Does not present the output as signable contract language"
]
},
{
"id": 7,
"prompt": "Sponsor signed for our conference: Praxis Data, Platinum, 25,000 USD. Their AP department says they only pay on invoices issued after the service is delivered, so they want to be invoiced the week after the event, net 45. Event is in May. Write the payment section. Also we have never charged interest on late payment - our treasurer just chases by email.",
"expected_output": "A refusal of post-event invoicing with the leverage argument, a staged deposit-plus-balance counter-proposal, and an express late-payment interest clause in the 12-18% range plus the non-payment devices.",
"files": [],
"expectations": [
"Refuses post-event invoicing and states it is deleted from the menu rather than ranked last",
"Explains that post-event invoicing hands away the organizer's only leverage because the perks are already delivered",
"States that the perk-hold and immediate de-branding remedies stop existing once the fee is invoiced after the event",
"Notes that the downstream payment gate in samber/dev-event-organizer-skills@event-sponsor-fulfillment becomes unenforceable under post-event invoicing",
"Offers a staged deposit plus balance schedule as the counter-proposal for a procurement department that cannot release the full amount upfront",
"Gives a real staged shape as a majority deposit rather than an even split, such as 80% on signature with 20% three months out, or 50% with the application and the balance by a fixed date",
"Names 100% at signing as the default rung and the one the efficiency ordering picks",
"States that the staged schedule wins on the deal-capture value axis and loses on effort, which is why efficiency never picks it",
"Drafts an express late-payment interest clause and states that interest is not recoverable without one",
"Sets the interest rate inside the verified 12-18% per annum range",
"States that the late-fee clause and the non-payment clause are always drafted rather than being menu options",
"Includes a clause making the payment obligation survive the sponsor not attending",
"Includes an immediate de-branding remedy letting the organizer remove all references to the sponsor from the event website and elsewhere",
"Does not re-price the 25,000 USD Platinum tier or offer a discount to unblock the payment terms"
]
},
{
"id": 8,
"prompt": "We are turning our one-off sponsor agreement into a template we will reuse every year for PortsConf. Two questions. First, cure period - I read somewhere that the Python Software Foundation uses a 15-day cure period for sponsors, and that sounded like a sensible standard to copy. Second, renewal: I do not want to redraft the whole thing every year, and ideally sponsors just roll over unless they tell us otherwise.",
"expected_output": "A correction of the 15-day PSF attribution, a 30-day cure default with the event-proximate variant, and a renewal branch built on exhibit replacement with the silence question and exclusivity travel settled explicitly.",
"files": [],
"expectations": [
"Refuses to attribute a 15-day cure period to the Python Software Foundation and states the claim is unverified",
"States that the only public PSF sponsorship contract contains no cure period at all, and that termination there is at the organizer's sole discretion",
"Notes that 15-day cure periods do exist in the general template market, so the error is the attribution rather than the number itself",
"Recommends 30 days as the default cure period and names it as the most common verified length",
"Offers the compressed event-proximate variant of around three days for breaches discovered close to the event date",
"States that a breach not curable before the event may be treated as non-remediable outright",
"Recommends the renewal mechanic of replacing the exhibit rather than rewriting the agreement",
"Requires the exhibit to be genuinely self-contained, warning that a perk or deadline written into the body will be silently carried into an edition where it no longer applies",
"Warns that automatic renewal on non-objection is the shape sponsors' procurement teams most often strike, and that affirmative approval of the new exhibit is slower but far easier to defend",
"Requires the renewal branch to settle explicitly how exclusivity travels: renewing with the exhibit, lapsing at term end, or converting into a right of first refusal",
"Notes that a reusable template promotes the higher-effort menu rungs, because the drafting cost is amortized across sponsors and editions",
"Includes termination grounds beyond cure: termination for convenience on notice, termination for material breach, and termination by mutual consent",
"Marks the enforceability of the cure and termination mechanics as jurisdiction-dependent and flags them for counsel",
"Presents the result as a term sheet rather than a signable reusable template"
]
},
{
"id": 9,
"prompt": "Sponsor countersigned last night: Cassini Robotics, Gold, at our robotics conference MotusConf. Our prospectus lists Gold as logo on website, logo on lanyards, booth, 4 passes, and a slot in the attendee newsletter. During the call we also agreed they would get a 20-minute workshop room on day 2 and their logo on the t-shirt, and they knocked the price from 9,000 EUR to 8,200 EUR. Build me the deliverables schedule - I will just copy the Gold column out of the prospectus.",
"expected_output": "A deliverables exhibit built from the accepted proposal rather than the prospectus column, carrying the two negotiated additions and the negotiated fee, with print-lock deadlines and a responsible party per row.",
"files": [],
"expectations": [
"Builds the exhibit from the accepted proposal for this sponsor rather than from the prospectus Gold column",
"States explicitly that the prospectus is the sales document and the accepted proposal is what the contract must carry",
"Includes the 20-minute day-2 workshop room and the t-shirt logo as their own exhibit rows",
"Carries the negotiated fee of 8,200 EUR rather than the 9,000 EUR list price",
"Gives every row a specification, a delivery surface, a hard deadline, a responsible party and a source",
"Sets the lanyard and t-shirt deadlines to the printer's lock date rather than the event date, and states that a logo missed at the print lock is unfixable afterwards",
"Names the sponsor as the responsible party on rows where the sponsor owes an asset, such as a vector logo file",
"States that most deliverable failures are the sponsor missing an asset deadline, and that a contract obliging only the organizer has no answer for it",
"Keeps the negotiated deltas inside the exhibit rather than in the body of the agreement, so the renewal mechanic can replace the exhibit cleanly",
"Specifies the booth row concretely with size, power, connectivity and setup window rather than as the bare word booth",
"Hands the completed exhibit to samber/dev-event-organizer-skills@event-sponsor-fulfillment as its input",
"Adds no perk that does not trace to the rate card or the accepted proposal",
"States that the output is a term sheet exhibit for counsel review rather than a contract"
]
},
{
"id": 10,
"prompt": "PyFrame Meetup, community-run, and our published rules say we never share attendee contact details with anyone. A sponsor is asking for the attendee list as part of their Silver package. Silver does not mention any data anywhere. They are fine with us writing it into the contract as a deliverable. Draft that clause.",
"expected_output": "A refusal to draft the data clause, grounded in the published no-list rule and the fact that Silver sold no data benefit, with the aggregate-demographics substitute offered and the section marked not applicable with a reason.",
"files": [],
"expectations": [
"Refuses to draft an attendee-list or attendee-data clause for this event",
"Grounds the refusal in the organizer's own published no-contact-list rule bounding what the contract may promise",
"States that the Silver tier sold no data benefit, and that a perk absent from the rate card and prospectus does not enter the contract",
"States that the sponsor agreeing to the clause does not make it draftable here",
"States that published sponsorship contracts carry no attendee-data or lead-list delivery clause by default, including at the foundation-run pole",
"Names the condition under which a data clause becomes draftable: a consented lead-retrieval benefit that was genuinely sold",
"Lists what such a clause would need if it ever applied: the lawful basis, the consent mechanism, the fields collected, the delivery timeline, each party's controller role, and the sponsor's downstream obligations",
"States that data handling is a counsel question rather than a template question, and flags it accordingly",
"Offers the aggregate audience demographics substitute - role, seniority and company-size mix with no names - delivered by samber/dev-event-organizer-skills@event-sponsor-fulfillment",
"Marks the data section in the term sheet as not applicable with a stated reason rather than silently omitting it",
"Does not invent a new consent mechanism at drafting time to make the clause work, since that would add a benefit the tier never sold"
]
},
{
"id": 11,
"prompt": "Our sponsor agreement draft has a section granting us the right to use the sponsor's logo in our promotion. A lawyer friend skimmed it and asked two things I cannot answer: does the sponsor's booth staff have to follow our code of conduct, and what happens to logo use after the event? We are a 500-person conference, SchemaFest, with a published code of conduct. Sponsors are Acme Registry at 8,000 USD and two others.",
"expected_output": "A code-of-conduct clause binding sponsor staff with an ejection right and no-refund consequence in the same clause, plus a redrafted reciprocal, promotion-only, auto-expiring logo licence.",
"files": [],
"expectations": [
"Treats the code-of-conduct clause binding the sponsor's own staff as a default rather than an option",
"Includes an organizer ejection right covering sponsors and their representatives who violate the code",
"States the no-refund consequence in the same clause as the ejection right rather than deferring it to the general cancellation section",
"Notes that this clause shape is confirmed across conferences and hackathons of very different sizes",
"Points the clause at the event's own published code of conduct, whose content belongs to samber/dev-event-organizer-skills@event-code-of-conduct",
"Redrafts the logo licence as reciprocal rather than one-directional",
"Makes each licence limited, non-exclusive and restricted to promotion of the sponsorship",
"Subjects each party's use to the other party's brand guidelines",
"Makes the licence expire automatically at the end of the agreement unless extended in writing, rather than continuing silently",
"Includes a ban on implying endorsement, or prior-approval rights running both ways",
"States that on termination each party ceases using the other party's intellectual property",
"Presents the result as a term sheet section for counsel rather than finished contract language to sign"
]
},
{
"id": 12,
"prompt": "The sponsor's legal team came back on our draft. They have struck our indemnity clause - it says the sponsor indemnifies us for everything arising from their participation and caps our own exposure at what they paid us - and replaced it with a mutual one. Our treasurer wants to just accept it so we do not lose the deal. Is their version right? What do we do? This is Gridline Systems, 15,000 USD, at our 700-person conference.",
"expected_output": "Both indemnity shapes presented without declaring a winner, a warning that striking the one-sided clause removes the only liability cap where no separate cap clause exists, and the whole question flagged for counsel.",
"files": [],
"expectations": [
"Declines to declare either indemnity shape correct, and states that which shape lands reflects bargaining power rather than an industry default",
"Presents both real shapes side by side: one-sided organizer-favouring, and mutual",
"Describes the one-sided shape concretely, with the sponsor indemnifying and defending the organizer against claims arising from the sponsor's participation, and the organizer's exposure capped at the amount actually paid by the sponsor",
"Warns that where the agreement carries no separate liability-cap clause, the one-sided indemnity is the only liability protection in the document, so striking it removes the cap as well",
"States that sponsors commonly request broad indemnity covering the organizer's own negligence, breach and IP infringement, so this pushback is expected rather than a red flag",
"Marks indemnity scope and the enforceability of any liability cap as jurisdiction-dependent and flags them for counsel rather than resolving them",
"Refuses to advise accepting or rejecting the redline as a legal matter, and routes the decision to the named counsel",
"Does not treat the risk of losing the deal as a reason to skip counsel review",
"Keeps the 15,000 USD fee and the sold tier unchanged while the indemnity is negotiated",
"States that the output is a term sheet and not legal advice",
"Notes that a well-advised sponsor may separately ask whether the organizer carries event-cancellation insurance, since a fee refund leaves the sponsor's own activation costs unrecovered",
"Names which parts of the section were drafted from published examples and which remain the organizer's or counsel's decision"
]
}
],
"trigger_queries": [
{ "query": "A sponsor said yes to our Gold tier. Draft the agreement terms.", "should_trigger": true },
{ "query": "We need a sponsorship contract for our conference - where do we start?", "should_trigger": true },
{ "query": "What should our cancellation and refund policy be if a sponsor pulls out two months before the conference?", "should_trigger": true },
{ "query": "Our top sponsor wants category exclusivity in cloud infrastructure. How do we write that?", "should_trigger": true },
{ "query": "Write the force-majeure clause for our meetup sponsorship - what happens if we have to cancel?", "should_trigger": true },
{ "query": "Do we need to require sponsors to carry insurance for a 60-person hackathon?", "should_trigger": true },
{ "query": "What cure period should we give a sponsor before we can terminate?", "should_trigger": true },
{ "query": "Can we charge interest if a sponsor pays late?", "should_trigger": true },
{ "query": "The sponsor's lawyer sent back a redlined indemnity clause. Now what?", "should_trigger": true },
{ "query": "How do we word the bit that lets us throw a sponsor's booth staff out if they harass someone?", "should_trigger": true },
{ "query": "What happens to the sponsorship money if we have to postpone the conference to next spring?", "should_trigger": true },
{ "query": "Our sponsor wants to be invoiced after the event. Is that ok?", "should_trigger": true },
{ "query": "Put together the paperwork for the sponsor who just signed.", "should_trigger": true },
{ "query": "How long should sponsors be allowed to use our logo after the event?", "should_trigger": true },
{ "query": "A sponsor asked for the attendee list in writing. How do I word that?", "should_trigger": true },
{ "query": "We promised a sponsor they would be the only database company. Three others are already Bronze. Help.", "should_trigger": true },
{ "query": "Write the terms for our first paid sponsor - we have never done this before.", "should_trigger": true },
{ "query": "What goes in the exhibit listing everything a sponsor gets?", "should_trigger": true },
{ "query": "Need a deliverables schedule for our Platinum sponsor with real deadlines.", "should_trigger": true },
{ "query": "How should we handle a sponsor who does not pay?", "should_trigger": true },
{ "query": "What is a sensible late payment penalty for sponsorships?", "should_trigger": true },
{ "query": "We are turning our one-off sponsor paperwork into a reusable template. What should change?", "should_trigger": true },
{ "query": "How do sponsors roll over to next year without redrafting everything?", "should_trigger": true },
{ "query": "Does the sponsor agreement need a governing law section?", "should_trigger": true },
{ "query": "Should we require a certificate of insurance from sponsors, and by when?", "should_trigger": true },
{ "query": "A sponsor is bringing a van into the expo hall. Does that change anything in their paperwork?", "should_trigger": true },
{ "query": "We are serving cocktails at a sponsor's stand. What cover do we need them to have?", "should_trigger": true },
{ "query": "How much notice does a sponsor need to give to get a refund?", "should_trigger": true },
{ "query": "What if we cancel the event - what do we owe the sponsors?", "should_trigger": true },
{ "query": "Is it ok to have one cancellation clause that covers both sides?", "should_trigger": true },
{ "query": "Our template says 'acts of God' - is that enough these days?", "should_trigger": true },
{ "query": "How do we define the category for an exclusivity deal so it does not blow up?", "should_trigger": true },
{ "query": "A sponsor wants exclusivity for three years. Should we agree?", "should_trigger": true },
{ "query": "What is the remedy if we accidentally sell to a competitor of an exclusive sponsor?", "should_trigger": true },
{ "query": "We are not a registered non-profit. Can we still sign sponsorship paperwork?", "should_trigger": true },
{ "query": "Who signs the sponsorship deal if we are just a group of volunteers?", "should_trigger": true },
{ "query": "Our sponsor negotiated two extra perks on the call. Where do those go?", "should_trigger": true },
{ "query": "A sponsor missed their logo deadline. Should our paperwork have covered that?", "should_trigger": true },
{ "query": "What sections does a sponsorship term sheet need?", "should_trigger": true },
{ "query": "Can you review the sponsorship terms I drafted?", "should_trigger": true },
{ "query": "Draft the payment schedule for a 25k sponsorship.", "should_trigger": true },
{ "query": "Should sponsors pay everything upfront or in instalments?", "should_trigger": true },
{ "query": "What do we send our lawyer before they draft the sponsor contract?", "should_trigger": true },
{ "query": "How do we protect ourselves if a sponsor backs out after we have printed the banners?", "should_trigger": true },
{ "query": "The sponsor's procurement wants net-60. What do we say?", "should_trigger": true },
{ "query": "Write the clause about sponsors following our code of conduct.", "should_trigger": true },
{ "query": "Can we take a sponsor's logo off the website if they do not pay?", "should_trigger": true },
{ "query": "Do we need a confidentiality clause in a sponsorship deal?", "should_trigger": true },
{ "query": "What is the right way to write the renewal option for a returning sponsor?", "should_trigger": true },
{ "query": "Our sponsor wants a right of first refusal for next year. How does that work?", "should_trigger": true },
{ "query": "The sponsor's counsel is asking what happens to their booth build costs if we cancel. What do I say?", "should_trigger": true },
{ "query": "How do we write the terms so a sponsor cannot imply we endorse their product?", "should_trigger": true },
{ "query": "We sold a booth to a sponsor and they never showed up. Do they still owe us?", "should_trigger": true },
{ "query": "Formalise the Silver deal we closed yesterday.", "should_trigger": true },
{ "query": "What do we put in writing now that the sponsor has said yes?", "should_trigger": true },
{ "query": "Terms for a sponsor who paid in full and now wants out.", "should_trigger": true },
{ "query": "How do I avoid promising something in the paperwork that we cannot actually deliver?", "should_trigger": true },
{ "query": "The sponsor's own paper arrived instead of ours. What should I be looking for?", "should_trigger": true },
{ "query": "What is the difference between what a sponsor gets if they cancel versus if we cancel?", "should_trigger": true },
{ "query": "Do we need a separate branch for converting the event to virtual?", "should_trigger": true },
{ "query": "Our meetup sponsor pays 900 an evening. Do we need anything written at all?", "should_trigger": true },
{ "query": "What notice period should we set to end a sponsorship for convenience?", "should_trigger": true },
{ "query": "A sponsor's brand team sent us logo usage guidelines. Does that belong in the agreement?", "should_trigger": true },
{ "query": "How do we make sure the printer's deadlines are actually in the sponsor paperwork?", "should_trigger": true },
{ "query": "We want to be able to drop a sponsor whose reputation turns toxic. Is that a thing?", "should_trigger": true },
{ "query": "A sponsor reserved stage time and never used it. Can we keep the money?", "should_trigger": true },
{ "query": "Write up what we agreed with the sponsor so our lawyer can turn it into a contract.", "should_trigger": true },
{ "query": "How much should we charge for our Gold sponsorship tier?", "should_trigger": false },
{ "query": "Build our sponsorship rate card for next year.", "should_trigger": false },
{ "query": "What premium should we add for category exclusivity on top of the Gold price?", "should_trigger": false },
{ "query": "Should we publish sponsor prices or quote-gate them?", "should_trigger": false },
{ "query": "What is a sane ratio between our top and bottom sponsor tiers?", "should_trigger": false },
{ "query": "How do we value an in-kind sponsorship in euros?", "should_trigger": false },
{ "query": "What discount policy should we set before the first sponsor call?", "should_trigger": false },
{ "query": "Write our sponsorship prospectus.", "should_trigger": false },
{ "query": "What goes in a sponsor kit PDF?", "should_trigger": false },
{ "query": "Design the tier comparison table for our sponsor page.", "should_trigger": false },
{ "query": "How do we present audience demographics to sponsors?", "should_trigger": false },
{ "query": "Write a cold email to a potential sponsor.", "should_trigger": false },
{ "query": "How do I handle a sponsor saying our audience is too small?", "should_trigger": false },
{ "query": "When in the year should we start pitching sponsors?", "should_trigger": false },
{ "query": "How many follow-ups before I give up on a sponsor prospect?", "should_trigger": false },
{ "query": "Build a target list of companies to approach for sponsorship.", "should_trigger": false },
{ "query": "Our sponsor signed months ago - how do I track what we still owe them?", "should_trigger": false },
{ "query": "What should the post-event sponsor report contain?", "should_trigger": false },
{ "query": "How do we run an opt-in raffle for sponsor lead capture?", "should_trigger": false },
{ "query": "Chase our sponsors for their logo files.", "should_trigger": false },
{ "query": "How much power and WiFi does each booth need on the day?", "should_trigger": false },
{ "query": "Why would a company sponsor our meetup?", "should_trigger": false },
{ "query": "What do sponsors actually get out of a developer conference?", "should_trigger": false },
{ "query": "Negotiate the attrition clause in our venue contract.", "should_trigger": false },
{ "query": "What is a reasonable food and beverage minimum for a 300-person venue?", "should_trigger": false },
{ "query": "The hotel's cancellation curve looks brutal - help me push back.", "should_trigger": false },
{ "query": "Find us a venue for a 400-person conference.", "should_trigger": false },
{ "query": "Review this caterer's contract before I sign it.", "should_trigger": false },
{ "query": "Ask our AV supplier for a certificate of insurance.", "should_trigger": false },
{ "query": "Compare three quotes for conference t-shirts.", "should_trigger": false },
{ "query": "Should we buy event cancellation insurance for the conference?", "should_trigger": false },
{ "query": "Set our go/no-go decision date against the venue's cancellation fees.", "should_trigger": false },
{ "query": "Build a risk register for our conference.", "should_trigger": false },
{ "query": "What is our plan if a keynote speaker drops out the day before?", "should_trigger": false },
{ "query": "Write the evacuation plan for the venue.", "should_trigger": false },
{ "query": "Write our conference code of conduct.", "should_trigger": false },
{ "query": "Set up an anonymous incident reporting channel.", "should_trigger": false },
{ "query": "How do we train the code of conduct response team?", "should_trigger": false },
{ "query": "What sanctions ladder should our code of conduct have?", "should_trigger": false },
{ "query": "Should we form a non-profit for our conference?", "should_trigger": false },
{ "query": "How do fiscal sponsors work for a volunteer-run event?", "should_trigger": false },
{ "query": "Split decision rights between the board and the organizing team.", "should_trigger": false },
{ "query": "Model the break-even for our conference.", "should_trigger": false },
{ "query": "Build the P&L for a 500-person event.", "should_trigger": false },
{ "query": "How big should our contingency reserve be?", "should_trigger": false },
{ "query": "Lay out the expo floor so attendees walk past every booth.", "should_trigger": false },
{ "query": "What does a Gold booth physically include - table size, power, signage?", "should_trigger": false },
{ "query": "When do sponsors load in and out?", "should_trigger": false },
{ "query": "Set up a newsletter mention swap with a community partner.", "should_trigger": false },
{ "query": "What should our community-partner tier offer?", "should_trigger": false },
{ "query": "Do we need speakers to sign a release for recording their talks?", "should_trigger": false },
{ "query": "Write the speaker invitation email for our keynote.", "should_trigger": false },
{ "query": "How do we handle speaker travel reimbursement?", "should_trigger": false },
{ "query": "Do our volunteers need to sign a waiver?", "should_trigger": false },
{ "query": "How do we handle tax on hackathon prize money?", "should_trigger": false },
{ "query": "What should the prize structure be for a 24-hour hackathon?", "should_trigger": false },
{ "query": "Set our early bird ticket prices.", "should_trigger": false },
{ "query": "Review this NDA before I sign it.", "should_trigger": false },
{ "query": "Generate an NDA for a contractor.", "should_trigger": false },
{ "query": "Draft an employment contract for our first hire.", "should_trigger": false },
{ "query": "Audit this smart contract for reentrancy vulnerabilities.", "should_trigger": false },
{ "query": "Review our SaaS master services agreement.", "should_trigger": false },
{ "query": "Run a legal risk assessment on our new product launch.", "should_trigger": false },
{ "query": "Draft a freelance design contract with payment milestones.", "should_trigger": false },
{ "query": "What should be in a mutual confidentiality agreement between two startups?", "should_trigger": false },
{ "query": "Draft a partnership agreement between two software companies.", "should_trigger": false },
{ "query": "Negotiate a brand sponsorship deal for my YouTube channel.", "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 |