event-sponsor-prospectus

Assembles a technical event's sponsorship prospectus with tier tables, perks, and audience evidence.

1|Updated Sep 6, 2026
One-click install
npx skills add https://github.com/samber/dev-event-organizer-skills --skill event-sponsor-prospectus-samber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: event-sponsor-prospectus
Source: https://github.com/samber/dev-event-organizer-skills/tree/main/skills/event-sponsor-prospectus
Command: npx skills add https://github.com/samber/dev-event-organizer-skills --skill event-sponsor-prospectus-samber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Event organizers struggle to turn their sponsor value proposition and rate card into a credible, published sponsorship document that prospects can read and forward before any sales call, without printing guarantees, fake scarcity, or unverifiable claims. ## Core Features & Use Cases - Document anatomy and ordering: Lays out sections in a credibility-before-price order (cover, brand imagery, facts, value proposition, proof, tier table, add-ons, logistics, named contacts), capped around 10-12 pages. - Tier table and perks construction: Builds checkmark tier grids with the price row first, max-available rows only for real caps, named perks, and à-la-carte add-on cards for single-exclusive surfaces. - Audience evidence and distribution: Writes the demographics section only as deep as verified data allows, chooses between an in-page tier-table page, a text one-pager, or a full PDF kit, and sets a per-edition refresh cadence. - Use Case: A community-run conference with finished tier prices needs a sponsorship kit PDF; the skill strips undeliverable lead-data perks, refuses guarantee language, orders proof before price, and produces a dated, per-edition document. ## Quick Start Ask the assistant to build the sponsorship prospectus for your conference using your existing rate card and value proposition, specifying whether the event is community-run or vendor-run.

Frequently Asked Questions about event-sponsor-prospectus

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a sponsorship prospectus for a developer conference?

Provide your existing sponsor value proposition and priced tier ladder, then the skill lays out sections in credibility-before-price order: cover, brand imagery, event facts, value proposition, proof, tier table, add-ons, logistics, and named contacts. It never sets prices or invents value claims itself.

What sections go in a conference sponsorship kit and in what order?

Proof precedes price: open on the event's brand and facts, then value proposition, testimonials and proof, then the tier table with the price row first, followed by add-ons, logistics FAQ, and named organizer contacts. Cap the document around 10-12 pages.

Should a sponsorship prospectus be a web page or a PDF?

Both are real formats. An in-page tier-table web page ships in days with no design capacity and suits first editions or tight deadlines; a dated PDF kit linked from a web stub is the dominant pattern for established community conferences with photo assets and design hours.

Can a sponsorship deck guarantee a number of leads to sponsors?

No. Real prospectuses from DevOpsDays, PyCon US, DjangoCon US, and Cal Hacks omit guarantees of any type, and this skill rejects them explicitly. Community-run events also cannot print attendee-list or badge-scanning benefits; aggregate demographics are the honest substitute.

When should I not use this skill for sponsorship work?

Do not use it to set tier prices, run sponsor outreach, draft contracts, or track perk delivery; those belong to sibling skills for pricing, outreach, agreement, and fulfillment. This skill only packages existing prices and value claims into the published document.

How do I refresh last year's sponsorship kit for a new edition?

Produce a fresh dated document per edition rather than editing in place: update the year in title and filename, refresh testimonials and logos, re-verify every printed cap against real inventory, update audience data, sweep dead links, and archive the previous edition.