samber · Agent Skills
228 Skills with substantive, source-verified documentation. Open a card to read the original instructions and review package and installation details.
event-market-fit
Read whether a technical event's concept, audience and price combination actually meets demand - before launch (community baseline, CFP oversubscription, saturation mapping), mid-sale (checkpoint ladder and pace index against expected sales), and after an edition (attendee return, sponsor renewal, sellout-speed trend) - composed into a go, hold, pivot or stop call. Use whenever asked to validate demand for a conference, hackathon or a meetup-to-conference jump, judge whether ticket sales are on
- 1h installs
- 1
- GitHub stars
- 5
- Updated
- Nov 8
event-portfolio-strategy
Shape one organizing team's set of event properties - flagship conference, meetup series, hackathon, podcast or always-on online space - into a portfolio where each one feeds the others. Covers what each property is for, the funnel path between them, cadence collisions against one team and audience, how much brand, audience list, team and sponsors are shared, the allocation posture, add/kill criteria written before they are needed, and the dated change-the-recipe, merge or retire call when atten
- 1h installs
- 1
- GitHub stars
- 5
- Updated
- Nov 8
event-speaker-coaching
Designs and runs the coaching program an event organizer offers accepted speakers: the coaching offer, mentor pairing, the review and dry-run calendar, a feedback protocol that improves a talk without crushing the speaker, cutting to time, nerves, Q&A and slide accessibility. Use whenever an organizer mentions coaching or mentoring their speakers, first-time or underrepresented speakers after acceptance, speaker dry runs, feedback on a speaker''s talk or slides, or a speaker who runs long, even
- 1h installs
- 1
- GitHub stars
- 5
- Updated
- Nov 8
event-speaker-cold-outreach
Write and sequence the cold invitation to a speaker a shortlist already picked - the message, not the search. Covers what a first invitation must disclose up front (event basics, honest budget and travel terms, the answer deadline, how you found them), personalization built from the shortlist's own "why", ranked first-touch channels, follow-up cadences that add a new angle instead of bumping, and the fee conversation where speakers have no rate card. Use whenever the user mentions writing a spea
- 1h installs
- 1
- GitHub stars
- 5
- Updated
- Nov 8
event-speaker-experience
Run the speaker-side experience from the moment a speaker confirms through to the thank-you after their talk - collecting bio, headshot, A/V needs and travel details against a deadline ladder, a single named point of contact, the pre-event briefing and slide deadline, tech check and green room, documented recording consent and its per-format opt-out asymmetry, and post-event follow-up. Use whenever the user mentions what to send an accepted speaker, a green room, speaker travel or hotel, a tech
- 1h installs
- 1
- GitHub stars
- 5
- Updated
- Nov 8
event-sponsor-agreement
Turn 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
- 1h installs
- 1
- GitHub stars
- 5
- Updated
- Nov 8
event-sponsor-pricing
Build the sponsorship rate card for a technical event - the revenue target taken from the budget, an inventory of sellable surfaces, cost-recovery, market-comp and value-based price setting, a 2-4 tier ladder with anchoring and a sane top-to-floor ratio, add-on and exclusivity premiums, in-kind valuation, and the discount and negotiation policy written before the first sponsor call, and annual sponsorship decoupled from events for a recurring series. Use whenever the user mentions sponsorship ti
- 1h installs
- 1
- GitHub stars
- 5
- Updated
- Nov 8
event-sustainability-plan
Plans, measures and reports the environmental footprint of a technical event the user organizes, and writes its public sustainability page without greenwashing, from a screening estimate of attendee travel (usually the dominant line) and ranked reduction levers to offset-free claim wording. Use whenever an organizer mentions a conference or meetup carbon footprint, a green or low-carbon event, conference waste, an event sustainability page or report, an event's carbon-neutral or offset claims, o
- 1h installs
- 1
- GitHub stars
- 5
- Updated
- Nov 8
event-ticket-pricing
Set attendee ticket prices for a technical event - free, nominal or priced against the funding model, comps subtracted from capacity, a ladder split by who pays (employer-funded, self-funded, student), gating on a date or a ticket count, the need-gated scholarship rung, group and invoicing mechanics, and the refund and transfer policy written before tickets go on sale. Use whenever the user mentions ticket prices, early-bird tiers, free versus paid entry, student, diversity or group rates, invoi
- 1h installs
- 1
- GitHub stars
- 5
- Updated
- Nov 8
event-vip-management
Receive named guests who are neither speaking nor sponsoring but whose presence creates escort, protocol, security or discretion obligations the general attendee flow cannot absorb - public officials, dignitaries, major funders, executives with no booth duty. Covers the qualification test (obligation, never status), the identification roster, escort depth, and a visibility posture that meets the obligation without building a status tier attendees can read. Use whenever the user mentions receivin
- 1h installs
- 1
- GitHub stars
- 5
- Updated
- Nov 8
event-volunteers
Recruit and organize the volunteer workforce that staffs one edition of a technical event - roster sizing built bottom-up from the posts the schedule needs standing, role definitions with real fit criteria, shift plans with arrival buffers, sign-up and confirmation, the briefing including the code-of-conduct escalation script, a named replacement protocol holding coverage, and recognition for the people who showed up. Use whenever the user mentions how many volunteers an event needs, recruiting
- 1h installs
- 1
- GitHub stars
- 5
- Updated
- Nov 8
changelog-writing
Turns raw commits, pull requests and tickets into release notes developers actually read - a scannable record of what shipped, what it means in practice, and what breaks. Use whenever the user mentions a changelog, CHANGELOG.md, release notes, a GitHub release body for a tag, a hosted "what's new" page, app-store release notes, Keep a Changelog, or Common Changelog, or asks what to write for a release they just cut - even when the commit history is messy and follows no commit convention. Not for
- 1h installs
- 1
- GitHub stars
- 11
- Updated
- Nov 8