AGENT SKILLS · EQUIPAGGIAMENTO / samber

samber · Agent Skills

228 Skill con documentazione sostanziale e fonti verificate. Apri una scheda per leggere le istruzioni originali e verificare pacchetto e installazione.

samber
Community

event-booth-experience

Design a technical event's expo floor once per edition, organizer-side - the layout and traffic pattern carrying attendees past every booth, the tier-to-physical-spec catalog turning "floor presence, Gold" into table size, power, height and signage rules, the master setup and teardown schedule, per-booth power and WiFi distribution, booth staffing and conduct rules, and a floor-wide traffic mechanic such as a passport card. Use whenever asked how to lay out an expo hall or sponsor area, what a s

Installazioni / 1h
7
GitHub Stars
4
Aggiornato
25 ott
samber
Community

event-community-building

Animate one recurring technical event's own audience in the gaps between editions - the cadence posture for the standing space, the conversion of attendees into returning participants and contributors, keeping a local cohort of the same event's fans warm, and handing the community asset over when organizers change. Use whenever asked how to keep an event's community alive between editions, what to post in the quiet months, whether a between-editions space should stay dormant or be programmed, ho

Installazioni / 1h
7
GitHub Stars
4
Aggiornato
25 ott
samber
Community

event-first-edition

Launch the first edition of a tech event (conference, hackathon, large meetup) from zero - a minimum viable edition 1, scope discipline against the full vision, the first cross-organization team, the decision-to-doors-open reverse timeline, and a pre-mortem of first-edition-specific risks with written go/no-go dates. Use whenever asked to start a new conference or hackathon, plan a first edition, scope a minimum viable event, form a founding organizer team, or set a launch timeline for an event

Installazioni / 1h
7
GitHub Stars
4
Aggiornato
25 ott
samber
Community

event-growth-strategy

Grow an established technical event edition over edition, or decide not to - the demand-headroom read, one discrete lever per edition (venue squeeze, track or day addition, venue step-up, price-led growth), the contract-risk gate on venue moves (deposits, attrition penalties, F&B minimums, long lead times), the pricing posture before scaling, and deliberate non-growth (caps, lotteries, shrinking back down) as a real strategy. Use whenever asked whether a conference or hackathon should grow, how

Installazioni / 1h
7
GitHub Stars
4
Aggiornato
25 ott
samber
Community

event-marketing-plan

Build the attendee-acquisition plan for a technical event - audience segments mapped to channels, the campaign-calendar spine (a ticketed event's percent-of-ticket-sales ladder or a free event's percent-of-attendance-goal curve), campaign moments pinned to pricing and program dates fixed elsewhere, budget allocated across the channel mix, funnel targets per phase, and each channel routed to the sibling that executes it. Use whenever asked to plan how to fill an event, run a ticket-sales or regis

Installazioni / 1h
7
GitHub Stars
4
Aggiornato
25 ott
samber
Community

event-run-of-show

Write and run the day-of run of show for a technical event once the schedule is published - the minute-by-minute playbook staff execute from, day-of role assignment (MC, speaker introducers, room leads, the organizer on duty), cue sheets at every transition, an organizer-only comm channel kept separate from attendee-facing ones, the escalation path and live incident response, shift rotation with verified handoffs, and closeout. Use whenever the user mentions a day-of rundown, a cue sheet, MC or

Installazioni / 1h
7
GitHub Stars
4
Aggiornato
25 ott
samber
Community

event-sponsor-fulfillment

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

Installazioni / 1h
7
GitHub Stars
4
Aggiornato
25 ott
samber
Community

event-vendor-sourcing

Source, vet and contract the suppliers a venue does not include - caterers, AV and production suppliers, security firms, insurance brokers, swag and print. Covers the venue-exclusivity check that precedes any evaluation, one identical brief per category, sourcing posture and quote-comparison depth, contract red flags and the certificate-of-insurance ask, ordering lead times, delivery buffers, and day-of coordination. Use whenever the user mentions finding a caterer, comparing supplier quotes, br

Installazioni / 1h
7
GitHub Stars
4
Aggiornato
25 ott
samber
Community

event-vip-social-program

Run the private gathering alongside a public technical event, once a named-guest programme already exists - how the seat list is assembled when sponsors, speakers and the organizer all put names forward, how invitations and the door work without publishing a tier, and where the gathering sits against the public programme. Use whenever the user mentions a private dinner or reception at a conference, refusing a sponsor's seat request, an invite-only room without a VIP badge, or when to schedule on

Installazioni / 1h
7
GitHub Stars
4
Aggiornato
25 ott
samber
Community

hackathon-mentoring

Design the mentor programme for one hackathon edition - coverage depth sized against the challenge tracks rather than a headcount, recruitment through community and sponsor channels, expertise tagging matched to the brief's tracks and any sponsor API, the request mechanic a stuck team uses to reach a mentor, the mentor briefing including the help-versus-build boundary, and rotation by expertise across shifts. Use whenever the user mentions how many mentors a hackathon needs, recruiting or briefi

Installazioni / 1h
7
GitHub Stars
4
Aggiornato
25 ott
samber
Community

hybrid-event-design

Design a technical event serving an in-room and a remote audience at once, after the format decision has already chosen hybrid - which sessions the remote audience gets, how far a remote attendee's voice reaches the stage, the cue track the stream needs beside the room's, and the crew split between them. Use whenever the user mentions streaming talks to a remote audience, remote Q&A, staffing the remote side, or running a day for two audiences at once - even if they never say "hybrid". Do NOT us

Installazioni / 1h
7
GitHub Stars
4
Aggiornato
25 ott
samber
Community

virtual-event-production

Run the technical and audience-facing delivery of a fully-remote technical event once the format decision has already chosen virtual - the platform that replaces the venue, remote-speaker connectivity and local backup recordings, live chat and Q&A moderation staffing, and the failure drills an event with no physical room needs. Use whenever the user mentions a virtual event platform, an online or remote-only conference or meetup, preparing remote speakers, staffing chat and Q&A moderation, or wh

Installazioni / 1h
7
GitHub Stars
4
Aggiornato
25 ott
samber
Community

golang-database

Comprehensive guide for Go database access — parameterized queries, struct scanning, NULLable columns, transactions, isolation levels, SELECT FOR UPDATE, connection pool, batch processing, context propagation, and migration tooling. Use when writing, reviewing, or debugging Golang code that interacts with PostgreSQL, MariaDB, MySQL, or SQLite; for database testing; or for questions about database/sql, sqlx, or pgx. Does NOT generate database schemas or migration SQL.

Installazioni / 1h
6
GitHub Stars
3,9K
Aggiornato
8 nov
samber
Community

golang-refactoring

Golang refactoring — safe, at-scale restructuring of existing Go code: a coverage-adaptive safety net, behavior-preserving transforms (gopls Rename/Extract, gofmt -r, gopatch), the Fowler catalog mapped to Go, breaking import cycles, and small stacked PRs. Apply when a function or type has grown too large, a code smell blocks a feature, or the user asks to refactor Go code — also for renaming at scale, extracting functions or interfaces, moving code between packages, or planning a multi-step ref

Installazioni / 1h
6
GitHub Stars
3,9K
Aggiornato
8 nov
samber
Community

copywriting-hooks

Writes opening hooks and post titles for long-form articles in EN or FR — blog posts, Substack/Medium/dev.to, LinkedIn long-form, newsletters, essays. Trigger whenever the user asks for a hook, opening, lede, intro, first sentence/paragraph, opener, accroche, attaque, phrase d'accroche, or première phrase — including punching up a flat intro or draft opening — or for a post title, titre d'article, or headline. Do NOT trigger for social posts (LinkedIn feed, Twitter/X, TikTok, Bluesky), READMEs,

Installazioni / 1h
6
GitHub Stars
242
Aggiornato
1 ott
samber
Community

dev-event-career

Plans a tech-event-organizing career from the candidate side - producer/manager/coordinator roles, and the community-manager-shaped end of the field. States plainly that no universal title ladder exists, gives the one real named ladder and CMX's community-management ladder as the closest dev-event-adjacent counterpart. Covers the volunteer-to-paid entry path, interview prep (portfolio review, scenario questions, CMX's five-competency loop, the paid mini-audit work sample), named practitioner quo

Installazioni / 1h
6
GitHub Stars
4
Aggiornato
25 ott
samber
Community

event-comms-channels

Design the attendee-facing communication channel architecture for one edition of a technical event - which channels exist, who is on each, which class of message routes to which channel, how several writers stay consistent executing a register set elsewhere, and how every channel is wound down once the event ends. Use whenever asked whether an event needs a chat space, an app or a status page, where a room change or schedule slip should be announced, how to stop attendees missing announcements,

Installazioni / 1h
6
GitHub Stars
4
Aggiornato
25 ott
samber
Community

event-date-selection

Pick the date a technical event runs on - the decision every other plan hangs off. Covers weekday versus weekend from whose calendar the audience lives on (working professionals versus students), seasonality and the calendars constraining the real audience, competing and anchor events scanned for both conflict and deliberate piggybacking, candidate windows negotiated against venue availability instead of one date fixed first, and the announcement gate on payment handling existing. Use whenever a

Installazioni / 1h
6
GitHub Stars
4
Aggiornato
25 ott
samber
Community

event-official-social-program

Decide how many official social occasions a technical event runs and how they sit against each other one occasion, two on separate slots, or a themed multi-activity track - plus the inclusion floor a whole slate must clear rather than each activity separately. Use whenever asked whether to run more than one social activity, whether two social activities can run in the same hours, how to publish a social track, or which activity a caregiver or a non-drinker can be in. Do NOT use for a single occa

Installazioni / 1h
6
GitHub Stars
4
Aggiornato
25 ott
samber
Community

event-schedule-design

Lay a technical event's already-selected talks into a published session grid - session-length standardization, room and capacity matching, the four clash types with multi-speaker intersection, break and lunch placement, buffer sizing, keynote and plenary placement as re-sync points, synchronized versus staggered track starts, energy-curve pacing, and speaker travel windows against slot assignment. Use whenever the user mentions building a conference schedule or agenda, a multi-track layout, sess

Installazioni / 1h
6
GitHub Stars
4
Aggiornato
25 ott
samber
Community

event-sponsor-prospectus

Assemble a technical event's sponsorship prospectus - the published document packaging an existing sponsor value proposition and rate card into a credibility-before-price section anatomy, a checkmark tier table with real disclosed caps, named per-tier perks and add-on packages, an audience-demographics evidence section, and a distribution format (web page or PDF kit) refreshed every edition. Use whenever the user mentions a sponsor deck, a sponsorship kit, a sponsor packages document, a prospect

Installazioni / 1h
6
GitHub Stars
4
Aggiornato
25 ott
samber
Community

event-sponsor-value-proposition

Discover what each sponsor of a technical conference actually needs, then articulate what it genuinely gets and why each sponsor segment buys - brand exposure, product feedback, recruiting, community goodwill, and (vendor-run events only) pipeline - one segment at a time through a six-part jobs-to-be-done template, bounded by what the event type can honestly promise and backed by proof points a diligent sponsor will check. Use whenever the user mentions why a company should sponsor an event, spo

Installazioni / 1h
6
GitHub Stars
4
Aggiornato
25 ott
samber
Community

event-venue-sourcing

Find and negotiate the venue for a technical event. Covers the written space program built from an attendance estimate and chosen format (main room, breakouts, hallway track, sponsor tables, power and WiFi density, load-in), a sourcing ladder treating free campus, civic and company-hosted space as a real first rung, site visits at the depth the risk warrants, several venues carried against several dates, and the contract traps - attrition, food-and-beverage minimum, cancellation curve, insurance

Installazioni / 1h
6
GitHub Stars
4
Aggiornato
25 ott
samber
Community

golang-samber-lo

Functional programming helpers for Golang using samber/lo — 500+ type-safe generic functions for slices, maps, channels, strings, math, tuples, and concurrency (Map, Filter, Reduce, GroupBy, Chunk, Flatten, Find, Uniq, etc.). Core immutable package (lo), concurrent variants (lo/parallel aka lop), in-place mutations (lo/mutable aka lom), lazy iterators (lo/it aka loi for Go 1.23+), and experimental SIMD (lo/exp/simd). Apply when using or adopting samber/lo, when the codebase imports github.com/sa

Installazioni / 1h
5
GitHub Stars
3,9K
Aggiornato
8 nov