AGENT SKILLS · ミッション装備
実際に使われている Agent Skills
公開リポジトリの検証済み Skills を比較し、機能、内容、導入状況、出典を確認してから追加できます。
- 掲載範囲
- 検証済み
- Skills
- 23,248
- リポジトリ
- 3589
- 最終同期
- 2026/11/04
codexthemescodex-theme-switcher
Apply, switch, and restore Codex desktop themes from the local ~/.codexthemes library with one command, and report which theme is currently active. Use when a user asks to apply or activate a theme they created or installed, switch between installed themes, restore the native Codex look, or check or debug which theme is currently applied.
- 1時間の導入数
- 3
- GitHub Stars
- 7
- 更新日
- 7月21日
melvynxanti-vibecode
Bans the 43 tells of a vibecoded website (purple gradient on black, indigo Tailwind buttons, bento grid, liquid glass, sparkles icon, fake counters, "Most popular" pricing, the "Create Next App" tab, no legal pages...) while Claude builds or reviews a site, so it looks made by a human. Use when building, redesigning or reviewing a website, landing page or web app UI, or when the user types /anti-vibecode, "vibecodé", "ça fait IA", "looks AI generated".
- 1時間の導入数
- 3
- GitHub Stars
- 10
- 更新日
- 10月27日
samberevent-hospitality
Decide the food, drink and social provision every population at a technical event shares - the catering service style and the dietary counts it has to carry, what a scheduled break contains, the event's alcohol posture, and whether an evening or social programme exists and in what form. Use whenever asked what format to feed a conference in, how catering should cover dietary restrictions across a whole event, what to put in a coffee break, whether to serve alcohol or run the event dry, or what t
- 1時間の導入数
- 3
- GitHub Stars
- 4
- 更新日
- 11月1日
samberevent-learning-expedition-design
Decide whether to take a technical audience into an organization the organizer does not control, and on what terms - when a host's own premises, operation and staff are the programme rather than a room rented and filled by the organizer. Sets the host-dependency posture (host speaker hosted in-house, one host site host-led or to a negotiated agenda, a multi-host circuit) and the access posture, meaning what the host lets attendees see and repeat afterwards. Use whenever asked to design a learnin
- 1時間の導入数
- 3
- GitHub Stars
- 4
- 更新日
- 11月1日
samberevent-no-show-management
Reduce and absorb no-shows at a technical event - an overbooking ratio against the room's real capacity and a stated ceiling, the waitlist and what triggers a promotion off it, the day-of walk-in lane, and the expected-show-up number handed to catering instead of the registration count. Use whenever asked how many registrations to accept for a free event, whether to overbook, how to run an event waitlist, why half the RSVPs did not turn up, or how many people to order food for. Do NOT use for re
- 1時間の導入数
- 3
- GitHub Stars
- 4
- 更新日
- 11月1日
samberevent-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
- 1時間の導入数
- 3
- GitHub Stars
- 4
- 更新日
- 11月1日
samberevent-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
- 1時間の導入数
- 3
- GitHub Stars
- 4
- 更新日
- 11月1日
samberworkshop-program-design
Design how a hands-on technical workshop at a developer event or conference runs, once the format decision has committed hours to it - facilitator coverage, participant prerequisites and setup, capacity ceilings, session length, materials, and what breaks when a room of laptops cannot reach the network. Use whenever the user mentions planning sessions inside a workshop day, how many helpers a conference lab needs, a workshop's prerequisites, capping workshop seats, bring-your-own-laptop versus a
- 1時間の導入数
- 3
- GitHub Stars
- 4
- 更新日
- 11月1日
samberbusiness-event-formats
Choose which company-run event shape to run - invite-only dinner, executive summit, single-city user conference, multi-city roadshow, or a floor-primary trade-show event - plus how its program is sourced and what shape its floor takes. Also owns the business-oriented activity layer any conference can run beside its program for sponsors (hiring corner, hands-on product feedback session, opt-in demo space, matchmaking). Use whenever a company weighs a user conference against a roadshow or a summit
- 1時間の導入数
- 3
- GitHub Stars
- 4
- 更新日
- 11月1日
samberevent-budget
Build the budget and P&L for a technical event - every cost line split into fixed and per-head, the revenue mix against the funding model, a Good/Better/Best scope-tier ladder so break-even has three answers instead of one, a contingency sized as a stacked floor, pad and downgrade ladder whose cuts also price lost sponsor reach, a cross-edition reserve policy, annual funding decoupled from single events, and outflows scheduled against the dates sponsor and ticket money actually lands. Use whenev
- 1時間の導入数
- 3
- GitHub Stars
- 4
- 更新日
- 11月1日
samberevent-code-of-conduct
Write a technical event's code of conduct and build the enforcement pipeline behind it - what the policy has to say, who and which spaces it binds (attendees, speakers, volunteers, sponsor and booth staff, satellite events), the reporting channels including an anonymous path, response-team composition and rehearsal, the on-site incident runbook and its response clock, the sanctions ladder, which rungs carry an appeal, and the transparency report. Use whenever asked to write or review an event or
- 1時間の導入数
- 3
- GitHub Stars
- 4
- 更新日
- 11月1日
samberevent-content-repurposing
Turn one edition's already-captured material into derivative published artifacts after the event - which formats get made, on what cadence, under which licence, and what speakers are asked to amplify. Covers publishing latency (dump, batched, drip, evergreen), the rights gate on third-party slide material and attendee photos, and the inventory handed up to the next edition's campaign. Use whenever asked what to do with talk recordings after a conference, how to turn an event into clips, write-up
- 1時間の導入数
- 3
- GitHub Stars
- 4
- 更新日
- 11月1日
samberevent-cultural-identity
Design and audit the lived culture of a technical event - the register (hacker, corporate, design, business) and its consistent expression across venue, catering, swag, dress code, stage production, MC and hosting tone, opening and closing ceremonies, and the values a code of conduct puts in the room. Use whenever asked to define an event's vibe or cultural identity, design a signature tradition or ritual, script an opening or closing, brief an MC or organizer-hosts, choose a swag posture, or au
- 1時間の導入数
- 3
- GitHub Stars
- 4
- 更新日
- 11月1日
samberevent-debrief
Run the organizing team's own internal retrospective on one finished edition of a technical event - the blameless frame, the reconstructed timeline, what went well split from what went poorly, what fired reconciled against the risk register, budget plan and run of show, team-health findings, and dated lessons-learned entries each carrying an owner and a due date. Use whenever asked to run a post-event debrief, a post-mortem or a retrospective after a conference, meetup or hackathon, review an ed
- 1時間の導入数
- 3
- GitHub Stars
- 4
- 更新日
- 11月1日
samberevent-feedback
Design and run participant-feedback collection for one edition of a technical event - what gets asked, who answers it, through which channel, when it goes out, and what goes back to respondents. Covers format-adapted question sets (meetup pulse, conference satisfaction and return intent, hackathon team dynamics, mentors, judging fairness, project continuation), attendee, speaker and sponsor segmentation, in-room versus emailed collection against real response-rate data, survey length, anonymity
- 1時間の導入数
- 3
- GitHub Stars
- 4
- 更新日
- 11月1日
samberevent-format-selection
Choose a technical event's structure before anything is scheduled - the event shape (recurring meetup, hackathon, unconference day, single-day or multi-day conference), one program or several (single versus multi-track), workshop-day ratios, the session-format mix (curated talks, workshops, open space, ignite, fireside chats, panels), delivery mode (in-person, virtual, hybrid), and hackathon demo/judging structure. Use whenever asked to pick an event format or concept, decide single-track versus
- 1時間の導入数
- 3
- GitHub Stars
- 4
- 更新日
- 11月1日
samberevent-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
- 1時間の導入数
- 3
- GitHub Stars
- 4
- 更新日
- 11月1日
samberevent-planning-timeline
Build the months-long work-back plan for a tech event, any edition - the doors-open anchor date, parallel tracks (venue, program/CFP, sponsors, marketing, ticketing) each worked back from that date, cross-track dependency gates, a buffer policy through latest-safe commitment dates, and replanning checkpoints that cut scope instead of moving the date. Use whenever asked to build an event planning timeline, conference retroplanning, a work-back or reverse schedule, event milestone sequencing, or t
- 1時間の導入数
- 3
- GitHub Stars
- 4
- 更新日
- 11月1日
samberevent-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
- 1時間の導入数
- 3
- GitHub Stars
- 4
- 更新日
- 11月1日
samberevent-positioning
Define a technical event's positioning - what it stands for, against which alternatives, for which audience identity. Covers the governance axis (community-run, foundation, media-run, vendor-owned), competitive-alternative mapping, best-fit attendee and sponsor segments (and when a conference may serve several targets), the business-oriented layer sponsors buy, market-category strategy (head-to-head, subcategory, new category and its education tax), the positioning statement, contrast-not-attack
- 1時間の導入数
- 3
- GitHub Stars
- 4
- 更新日
- 11月1日
samberevent-production
Engineer the technical AV production of a technical event once the format and session grid are fixed - capture tiers from a single smartphone to multi-camera vision mixing, signal-path architecture separating room display from recorded output and crew monitor, redundancy against named recorded-audio failure modes, AV crew roles, the written technical spec handed to venue sourcing, the Media budget line, rehearsal, and the publication pipeline. Use whenever the user mentions conference AV, record
- 1時間の導入数
- 3
- GitHub Stars
- 4
- 更新日
- 11月1日
samberevent-risk-management
Build and maintain the standing risk register for a technical event - risks named by category, scored on a likelihood x impact matrix adapted to a dated one-shot deliverable, split into prevention, contingency or insurance, the insurance stack including the communicable-disease buy-back, internal go/no-go decision dates set against the venue's escalating cancellation-fee curve, and the on-site emergency plan. Use whenever the user mentions event insurance, cancelling or postponing an event, a go
- 1時間の導入数
- 3
- GitHub Stars
- 4
- 更新日
- 11月1日
samberevent-side-event-coordination
Approve and coordinate third-party-run satellite events around a technical event - the vetting gate, calendar deconfliction against the published grid, name and logo usage rules, and the disclaimer stating what the main event does not vouch for. Use whenever a user group, sponsor or attendee wants to run a party, meetup, dinner, workshop or afterparty during the event's dates, when someone is already using the event's name on their own page, or when fringe events collide with the main programme
- 1時間の導入数
- 3
- GitHub Stars
- 4
- 更新日
- 11月1日
samberevent-social-media
Run a technical event's own social presence inside the weight, phase and dates the marketing plan already fixed - platform selection, the campaign versus community hashtag, posts mapped onto campaign phases (announcement, CFP, speaker reveal, final push, live), speaker and sponsor amplification asks, and day-of coverage. Use whenever the user mentions event social media, a conference or hackathon content calendar, speaker-announcement posts, which platforms an event should post on, an event hash
- 1時間の導入数
- 3
- GitHub Stars
- 4
- 更新日
- 11月1日