Skip to content

samber/dev-event-organizer-skills / skills/dev-event-kickoff

dev-event-kickoff

Verified

Before answering any event-organizing request that opens a new project or a new session, run this router first - it maps the task onto the 72-skill samber/dev-event-organizer-skills collection, or says plainly that none fits, and bootstraps or resumes the project's shared context so the next session starts warm. This fires on a conversational state, not on a subject - invoke it at every event project start even when the collection's skills are already in daily use on another event, at every recurring check-in on the same project, and whenever routing between siblings is unclear. Covers conference, meetup and hackathon kickoffs, "which event skill do I need", "where do I start organizing this event", event organizer skill routing, and recurring event check-ins. Use this whenever someone describes an event-organizing problem without naming a skill, even if they never say "kickoff", "routing" or "start".

FileKindSize
SKILL.mdskill md51.0 KB
evals/evals.jsonconfig46.9 KB
references/context-artifact.mdmarkdown3.7 KB
references/format-and-lifecycle-gates.mdmarkdown7.4 KB
references/routines.mdmarkdown2.4 KB
references/skill-routing.mdmarkdown15.2 KB

evals/evals.json

View on GitHub
{
  "skill_name": "dev-event-kickoff",
  "evals": [
    {
      "id": 1,
      "prompt": "We're three engineers at Braukette (a brewing-software startup) and the company just approved a small budget to maybe run a hackathon for our user community next spring - nothing exists yet, no date, no venue, and honestly we haven't even decided whether it's worth doing at all. None of us has organized anything before, and this is a one-off experiment we can each give a few hours to. Tell me everything you need to know from me, and then give me the full plan: challenge themes, prize ideas, judging, the works.",
      "expected_output": "A cold-start kickoff session: detection first, a capped one-question-at-a-time interview limited to what the message did not already answer, a route to an existence-check skill, a short-list restricted to existence-check and spine classes, a single kickoff re-invocation routine, and a context artifact - explicitly not a full hackathon plan.",
      "files": [],
      "expectations": [
        "The session is treated as a cold start decided from the absence of a context artifact, without asking the user whether it is a new or resumed project.",
        "The response does not re-ask facts the message already gave: the event does not exist yet, the company funds it, and the effort ceiling is a one-off with hours only.",
        "Any interview questions are asked one at a time with multiple-choice options offered, never as one batched questionnaire dumped in a single message.",
        "The interview stays within a seven-question cap.",
        "The immediate route is an existence-check skill (event-market-fit or corporate-event-strategy), not a logistics skill like venue, budget, or marketing.",
        "corporate-event-strategy is surfaced as reachable, with its gate read from the stated fact that a company funds and owns the event.",
        "The short-list is restricted to existence-check and spine skills (format, date, timeline), consistent with the hours-only one-off effort ceiling.",
        "Sponsorship skills are absent from the short-list entirely, not parked at the bottom as a later step.",
        "Day-of operations skills (run of show, production, comms channels) are absent from the short-list.",
        "Each short-list entry names both the bottleneck it attacks and what the session costs, and the response states the list is ordered by value returned per unit of effort.",
        "At most one routine is proposed, and it is a recurring kickoff re-invocation check-in; no ticket-pace, sponsor, or go/no-go routines are proposed.",
        "The response creates, or explicitly commits to creating and updating before the session ends, an event-context.md context artifact recording the answers.",
        "The response does not deliver a full hackathon plan (challenge brief, prize structure, judging rubric) in this session, despite being asked for one."
      ]
    },
    {
      "id": 2,
      "prompt": "Here is event-context.md from our repo:\n\n# Event context\n_Last updated: 10 weeks ago_\n\n## Identity\n- Event: DuckConf, single-day systems conference. Edition 3; edition 2 ran last spring.\n- Funding model: volunteer community.\n\n## Format (the gate source)\n- Shape: single-day conference, single track, no workshop hours.\n- Delivery mode: in-person.\n\n## Dates\n- Doors: announced, about six months out. CFP closes in 11 weeks.\n\n## Money\n- Budget committed; break-even at 280 paid tickets; recorded in budget.md.\n\n## Programme\n- CFP open: 41 submissions in. No reviewers recruited. Grid not published.\n\n## State\n- In flight: CFP running.\n- Decided: single track; free livestream of the recordings.\n- Open: who reviews the submissions.\n- Constraints: doors date fixed; standing project, a few hours weekly.\n\n## Session log\n- (10 weeks ago) - kickoff -> routed to event-cfp-design -> call published.\n\nIt's been ten weeks since I touched this. What should I be working on?",
      "expected_output": "A warm-start session: no re-interview beyond the session goal, an exactly-5-line state summary, a route to talk selection (reviewer recruitment), a session-log line appended, fields patched not rebuilt, and a re-rank read from the artifact's constraints.",
      "files": [],
      "expectations": [
        "The session is treated as a warm start; the response does not re-ask format, edition, funding, or date questions already recorded in the artifact.",
        "At most one question is asked, and it is the goal of this session.",
        "A state summary of exactly 5 lines is produced.",
        "The summary lines cover: event identity and format, the date and where it sits, in-flight work, top open decision, and the active constraint.",
        "The immediate route is samber/dev-event-organizer-skills@event-talk-selection, matching the open decision of who reviews the 41 submissions before the CFP closes.",
        "The route is named in owner/repo@skill form.",
        "The response does not route to event-cfp-design: the call is already published and collecting submissions.",
        "A dated session-log line (goal, skill routed to, what changed) is appended to the artifact.",
        "The artifact is updated by patching only changed fields, not rebuilt from scratch.",
        "The short-list is re-ranked from the artifact's recorded constraints (fixed doors date, standing few-hours-weekly ceiling) without re-asking those questions.",
        "The response states which recorded answer or constraint moved which recommendation off its default place.",
        "Recurring-gated skills are treated as reachable with the gate read from the artifact's edition-3 record, not re-asked.",
        "Skills ruled out for this session are absent from the short-list rather than listed at the bottom."
      ]
    },
    {
      "id": 3,
      "prompt": "Kicking off a new project: our community, the Nimbus Users Group (about 2,000 members), decided to run some kind of annual gathering next fall. We keep going back and forth - maybe a two-day conference, maybe a hackathon, and my co-organizer really wants it hybrid so remote members can join. Can you help us design the hybrid streaming setup, shortlist venues for about 400 people, and figure out what prizes we should offer if we do the hackathon part?",
      "expected_output": "A single route to event-format-selection with a full stop: no hybrid design, no venue shortlisting, no prize advice, an explicit statement of which skill groups are suspended and why, and a commitment to record the format decision in the artifact once made.",
      "files": [],
      "expectations": [
        "The response routes to samber/dev-event-organizer-skills@event-format-selection as the single route for this session.",
        "The response does not provide hybrid streaming or production design guidance and does not route to hybrid-event-design.",
        "The response states that hybrid-event-design and virtual-event-production sit downstream of the format decision and must never be used to make it.",
        "The response does not route to event-venue-sourcing or begin shortlisting venues, because the delivery mode is unfixed and no room is confirmed to exist.",
        "The response does not give hackathon prize or cash-prize guidance while the hackathon shape is undecided.",
        "The response explicitly names which skill groups are suspended (the hackathon lane, the delivery-mode skills, the conference-scale rows) rather than silently omitting them.",
        "The suspended rows are described as unreachable until the format is fixed, not as absent from the collection.",
        "The response does not guess or assume a shape (for example proceeding 'assuming a conference') in order to give gated advice.",
        "No short-list drawn from gated rows is offered.",
        "The response commits to recording the format decision in the context artifact once it is made, so the next session reads the gate instead of re-asking.",
        "The route is named in owner/repo@skill form.",
        "The response does not itself decide between conference, hackathon, or hybrid in this session; it routes the decision."
      ]
    },
    {
      "id": 4,
      "prompt": "I'm the executive director of the Fjordwall Foundation, which runs FjordCon: edition 4, a two-day, two-track, in-person conference of around 900 attendees, doors on a fixed announced date about six months out, budget carried from last cycle with a revenue target on file. We have two funded full-time event staff. Our target sponsors close their annual marketing budgets at the end of January - six weeks from now - and sponsorship covered 60% of our costs last year, but we haven't started this cycle's motion at all. The CFP text isn't written yet and attendee marketing hasn't begun either. What order do we attack this in?",
      "expected_output": "A re-ranked short-list with the sponsorship sale promoted to the top because the sponsor budget window closes in six weeks, the six-skill sponsorship chain in dependency order, pricing anchored to the budget's revenue target, and the re-rank stated out loud.",
      "files": [],
      "expectations": [
        "Sponsorship sales work is placed first in the recommended order.",
        "The response explicitly ties that promotion to the closing sponsor budget window, stating that this deadline moved sponsorship off its default place.",
        "While promoting it, the response names sponsorship's cost honestly: a months-long motion running on a counterparty's calendar, the most expensive class rather than a cheap one.",
        "A sponsorship chain is presented in this order: value proposition, then pricing, then prospectus, then outreach, then agreement, then fulfillment.",
        "The chain links are named as skills in owner/repo@skill form.",
        "The chain is presented as dependency order, each link consuming what the previous produced, and the chain itself is not ranked by value or importance.",
        "Sponsor pricing is anchored to the revenue target taken from the event budget; the budget is consumed as an input, not re-set by pricing.",
        "The short-list contains between 5 and 8 entries.",
        "Each short-list entry names both the bottleneck it attacks and what the session costs.",
        "The stated ordering criterion is value returned per unit of effort, not lowest cost.",
        "CFP design appears in the output (short-list or not-now) but is not ranked ahead of the sponsorship work.",
        "If routines are proposed, the sponsor pipeline and renewal sweep is installed first, tied to the closing budget window.",
        "The re-rank is stated out loud: which stated fact moved which class, rather than a silently reordered list."
      ]
    },
    {
      "id": 5,
      "prompt": "Quick routing check for our conference project (TerraPipe Summit, edition 2, in-person, 3 tracks). Five questions, answer each: (1) we're adding a demo-day segment where local startups that already have shipped products pitch to a jury - is that the hackathon judging skill? (2) our platinum sponsor wants to run their own meetup in a bar near the venue the evening before - whose job is vetting and approving that? (3) another conference in our region proposed swapping newsletter mentions with us - same skill as question 2 or a different one? (4) we already have a shortlist of 12 dream speakers and now need to write the first invitation email; (5) the team keeps debating whether to hire our first paid coordinator - which skill decides whether we should at all, and which one writes the job posting once we decide?",
      "expected_output": "Five correct boundary-pair routes: startup-pitch-contest, event-side-event-coordination, cross-event-promotion, event-speaker-cold-outreach, and event-team-structure then dev-event-hiring, each with the declared-scope split stated.",
      "files": [],
      "expectations": [
        "Question 1 is routed to startup-pitch-contest, not to hackathon-judging.",
        "The split for question 1 is stated: hackathon judging covers work built during the event, while the pitch contest covers companies that existed before it.",
        "Question 2 is routed to event-side-event-coordination, since a third party wants to run a satellite around the event's dates.",
        "Question 2 is not routed to cross-event-promotion or event-media-partnerships.",
        "Question 3 is routed to cross-event-promotion, a reciprocal swap with another organizer's own event.",
        "Question 3 is not routed to event-media-partnerships, which covers barter with media outlets and communities rather than other organizers' events.",
        "Question 4 is routed to event-speaker-cold-outreach, the invitation to a speaker a shortlist already picked.",
        "Question 4 is not routed to event-speaker-sourcing, and the split is stated: sourcing stops at a ranked shortlist, outreach writes the invitation.",
        "For question 5, whether a first paid role is warranted at all is routed to event-team-structure.",
        "For question 5, the job posting and scorecard are routed to dev-event-hiring, conditional on team-structure's verdict saying hire.",
        "Every route is named in owner/repo@skill form.",
        "Each sub-question receives exactly one route decided from declared scope, and no skill name outside the collection's routing tables is invented."
      ]
    },
    {
      "id": 6,
      "prompt": "MarmotConf is the academic-flavored systems conference we're organizing (edition 1, in-person, Lyon). This year the committee wants two things: a peer-reviewed paper track where accepted papers get published as proceedings with DOIs, and the whole programme delivered in both French and English - parallel translated tracks and a bilingual MC. Which skills from the event collection do I load for each?",
      "expected_output": "Both requests named plainly as coverage gaps: no skill covers proceedings or a bilingual programme; the nearest skills (event-talk-selection, event-accessibility-inclusion) are not stretched to cover them, no skill is invented or promised, and the gaps land in the output's Gap section.",
      "files": [],
      "expectations": [
        "The response states plainly that no skill in the collection covers a peer-reviewed paper track ending in published proceedings.",
        "The response states that event-talk-selection reviews talk proposals for stage slots only, and does not stretch it to cover proceedings.",
        "The response states plainly that running the programme in two languages as a design choice is covered by no skill in the collection.",
        "The response states that event-accessibility-inclusion covers interpretation and captioning as access provisions on request, and does not stretch it into bilingual programme design.",
        "Neither gap is answered by promising a future skill or inventing a skill name.",
        "Both gaps are named explicitly as gaps rather than papered over with generic advice presented as a skill's output.",
        "No route names a skill outside the collection's routing tables.",
        "The response does not hand these two subjects off to a sibling collection (DevRel or platform), since neither belongs there.",
        "The response does not claim the collection covers the publication mechanics of proceedings (peer review to DOI).",
        "The response still performs kickoff project-state behavior - checking for or referencing the context artifact and cold-versus-warm state - rather than answering as a stateless Q&A.",
        "The output includes a distinct Gap statement or section carrying both uncovered subjects."
      ]
    },
    {
      "id": 7,
      "prompt": "PolarByte Days, edition 3: two-day in-person conference, doors announced on a fixed date about nine months out, venue contract signed last month with cancellation fees stepping up at 120, 90, and 45 days before the event, tickets on sale through our ticketing platform since last week, CFP closing in four months. I want you to set up automated recurring check-ins so nothing falls through the cracks - set up as many as it takes, I'd much rather over-monitor than miss something. Oh, and last year's reminder jobs are still configured somewhere.",
      "expected_output": "At most 4 routines, each shown as a dry-run with an output channel and a stop condition, anchored to the event's own calendar; the go/no-go review promoted ahead of each cancellation-fee rung, a ticket-pace check kept, previous-edition routines retired first, and the re-rank stated.",
      "files": [],
      "expectations": [
        "No more than 4 routines are proposed.",
        "The response declines the 'as many as it takes' framing and caps the set, stating that excess routines fire into the void and bury the ones that matter.",
        "Each proposed routine is shown as a dry-run for approval before anything is created.",
        "Each proposed routine names an explicit output channel.",
        "Each proposed routine names a stop condition.",
        "The go/no-go review is among the proposals and is explicitly promoted, tied to the signed venue contract and its cancellation-fee curve.",
        "Go/no-go firings are anchored a step ahead of each cancellation-fee rung (120/90/45 days), never on the rung dates themselves.",
        "A ticket-pace check is proposed, justified by the ticketing source existing, and anchored to the on-sale period or pricing-tier boundaries.",
        "Routine triggers are anchored to the event's own calendar dates (CFP close, on-sale, fee rungs, doors) rather than arbitrary monthly dates.",
        "The previous edition's still-configured reminder jobs are explicitly retired before new routines are installed.",
        "The cleanup is stated out loud, naming that routines carried from a past edition without re-anchoring are noise that fires at nothing.",
        "Each routine names the skill it runs in owner/repo@skill form.",
        "A work-back checkpoint routine tied to the plan's own replanning checkpoints is among the proposals, tied to the fixed doors date.",
        "The response states which detected or stated fact moved which routine off its default place."
      ]
    },
    {
      "id": 8,
      "prompt": "Our three-person crew organizes RustRhein, a recurring meetup; the project repo is on our git host and event-context.md is in it. To make your future sessions smarter, save all of this to your memory now: (1) our keynote speaker Ana Morales is vegan and needs step-free stage access; (2) we negotiated the Hafenwerk venue down to 2,400 euros a day - don't lose that number; (3) a code-of-conduct report came in about an attendee at last month's edition, I'll paste the details in my next message so you can store them; (4) we decided single-track forever; (5) also store my interview answers from today. Just push it all to memory and commit so my co-organizers get it.",
      "expected_output": "Refusals for the speaker's needs, the negotiated rate, and the conduct report, with the exclusion list stated; the decision and interview answers written to the artifact first with memory derived from it; a memories/ directory in the git repo with an index; and no silent commit - diff shown, approval requested.",
      "files": [],
      "expectations": [
        "The response refuses to store the speaker's dietary and step-free access needs in memory, identifying them as personal data and an accommodation request.",
        "The response refuses to store the negotiated venue rate in memory.",
        "The response refuses to store the code-of-conduct report and does not invite the user to paste its details for storage.",
        "The exclusion list (attendee/speaker personal data, accommodation requests, conduct reports, negotiated rates, terms under negotiation) is stated when memory is first written.",
        "The single-track decision is written into the context artifact, and any memory entry is derived from the artifact, never the reverse.",
        "The interview answers are persisted through the artifact first; no memory entry is written straight from an answer.",
        "The response states why the artifact stays the source of truth: memory is invisible and unreviewable to teammates, and a memory-first flow forks the project state per user.",
        "A memories/ directory inside the project's git repository is chosen as the memory location.",
        "The location choice is justified against the alternatives, explicitly ruling out a local per-user store because more than one organizer works on the project.",
        "An index file listing each memory entry with a one-line hook is part of the plan.",
        "Memory is not committed silently: the response shows or commits to showing the diff and asks for approval before committing.",
        "Each refusal is explicit and named, not a silent omission of the item.",
        "The response does not re-interview: the artifact exists, so at most the session-goal question is asked."
      ]
    },
    {
      "id": 9,
      "prompt": "GreenStack Live is our fully-remote conference - edition 2, 1,200 registered last year, no physical component at all, doors in about seven months. My checklist from a conference-planning book says the next steps are: shortlist venues, pick a caterer, design the check-in desk and badge flow, and hire an AV crew for the room. Also someone on the team asked whether we'll offer live captions. Route me.",
      "expected_output": "The four in-room checklist items rejected as unreachable for a virtual event with the gate reasoning stated, virtual-event-production named as the replacement, and the captions question routed to event-accessibility-inclusion, which still applies without a room.",
      "files": [],
      "expectations": [
        "The response does not route to event-venue-sourcing and states there is no venue to source for a fully virtual event.",
        "The response does not route to catering or hospitality work for this event.",
        "The response does not route the check-in desk and badge flow to the in-room attendee-experience skill.",
        "The response does not route to event-production for a room AV crew.",
        "The response states the reason: the virtual delivery mode closes the in-room gate outright, rather than merely omitting the four skills.",
        "The delivery, platform, and production needs are routed to virtual-event-production as the replacement for the closed in-room rows.",
        "The captions question is routed to event-accessibility-inclusion.",
        "The response states that accessibility still applies to a virtual event because its digital-access provisions need no room.",
        "virtual-event-production is not used to re-open the delivery-mode question; the mode is carried as an already-fixed gate.",
        "Routes are named in owner/repo@skill form.",
        "The gate is read from the stated fully-remote fact, not re-asked or re-decided.",
        "The inapplicable checklist items are rejected rather than partially followed: no venue shortlisting or caterer advice appears anywhere in the response."
      ]
    },
    {
      "id": 10,
      "prompt": "First edition of Composta Summit - a compost-tech developer conference, yes really - is in seven months, and nothing has ever run before. Three asks: (a) I read that serious events do 'continuous improvement' across editions, so set that up now so we're rigorous from day one; (b) a friend organizes a climate-tech meetup and offered to cross-promote with us, but I assume that kind of swap is only for established events with a track record?; (c) we're also weighing spinning up a monthly meetup series alongside the summit - which skill thinks that through? We definitely intend to run the summit every year.",
      "expected_output": "Continuous improvement deferred to not-now with an explicit unblocking condition; the cross-promotion assumption corrected because that skill is open to first editions; the second-property question routed to portfolio strategy on property count; first-edition promoted; intent to recur not treated as opening recurring gates.",
      "files": [],
      "expectations": [
        "The response declines to route to event-continuous-improvement now.",
        "The stated reason is that the recurring gate is about having a previous edition to read, not intent to repeat - a first edition has no debrief logs to compare.",
        "Continuous improvement is placed in a not-now list with an explicit unblocking condition (editions and their debriefs existing), rather than deleted or silently dropped.",
        "The response corrects the user's assumption for ask (b): cross-event-promotion is available to a first edition and is not recurring-gated.",
        "The response states why: the swap skill handles one-off boosts for a coming edition, and it is an acquisition lever a first edition can reach without a track record.",
        "Ask (b) is routed to samber/dev-event-organizer-skills@cross-event-promotion.",
        "Ask (c) is routed to samber/dev-event-organizer-skills@event-portfolio-strategy.",
        "The response states that the portfolio skill opens on property count - the day a team starts weighing a second property - whatever edition the flagship is on.",
        "event-first-edition is promoted or recommended for the flagship, tied to the stated first-edition answer.",
        "Cross-edition after-and-between entries (community building between editions, growth strategy, the trend read) are removed from the current short-list rather than listed low.",
        "Gates are read from stated facts, not inferred from the event's ambition or name.",
        "Routes are named in owner/repo@skill form.",
        "The stated intent to run the summit every year is not treated as satisfying the recurring gate."
      ]
    },
    {
      "id": 11,
      "prompt": "Fresh session on our repo for Kelpway Conf 2027. There's no event-context.md (we never made one), but the repo contains: budget-2027.xlsx committed last month with break-even at 410 tickets, schedule-grid.pdf published on the site two weeks ago (two days, three tracks, in-person, doors on a fixed date in about ten months), and venue-contract-signed.pdf. The git log shows steady commits until 19 days ago, then nothing. Get me going again - ask me whatever you need.",
      "expected_output": "Detection-first cold start: format and date read from the published grid, schedule design and venue sourcing deleted, risk management promoted by the signed contract, the budget treated as done, the stall read from git, and only the questions detection could not answer asked, one at a time.",
      "files": [],
      "expectations": [
        "The session is treated as a cold start because no context artifact exists, without asking the user which kind of start it is.",
        "The response does not ask the format question (shape, track count, delivery mode) - the published grid already fixes it.",
        "The response does not ask for the event date - it is read from the published grid.",
        "The published grid's existence removes event-schedule-design from the recommendations.",
        "The signed venue contract removes event-venue-sourcing from the recommendations.",
        "The signed venue contract promotes event-risk-management (go/no-go against the cancellation exposure) on the short-list.",
        "The committed budget is treated as making budget modelling near-free or already done, not recommended as a first task.",
        "The 19-day commit stall is read as a stall or pace signal and reflected in the session's state or routing.",
        "Interview questions are limited to what detection could not answer, and the total stays within the seven-question cap.",
        "Any questions are asked one at a time with multiple-choice options.",
        "An event-context.md artifact is created, or committed to before session end, recording the detected invariants (format, date, budget status, signed contract).",
        "The deleted skills (schedule design, venue sourcing) do not appear at the bottom of the short-list - they are removed entirely.",
        "Each short-list entry names the bottleneck it attacks and what the session costs."
      ]
    },
    {
      "id": 12,
      "prompt": "OtterForge Conf wrapped last Saturday - edition 5, 1,400 attendees, in-person, all talks recorded. Three things on my mind: (1) what's the right sequence now that it's over? Honestly I'm tempted to skip the attendee survey this year, people are tired of forms. (2) Our standing OtterForge talks YouTube channel has been dead for months, and separately the community wants a real developer-content and documentation push around the open-source tooling the conference is built on. (3) Next year we want a hackathon segment where teams build against our headline sponsor's public API - is that a platform question for a different skill collection? Route all of it.",
      "expected_output": "A post-event session: short-list reduced to the after-and-between class, the closing chain in dependency order with feedback kept first, the dormant channel routed to the podcast/channel skill, the docs push recommended to the DevRel sibling repo as a recommendation, and the sponsor-API hackathon question kept in-collection.",
      "files": [],
      "expectations": [
        "The finished-event answer reduces the current short-list to the after-and-between class alone.",
        "Marketing, sponsorship, on-the-day, and existence-check classes are deleted from the short-list, not listed at the bottom.",
        "A closing chain is presented in this order: event-feedback, then event-debrief, then event-content-repurposing, then event-continuous-improvement.",
        "The chain is framed as dependency order - each link handing its output to the next - and the chain itself is not ranked.",
        "event-feedback is kept as the first link despite the user's temptation to skip the survey, because the debrief and the trend read consume its output.",
        "event-continuous-improvement is treated as reachable, with the recurring gate read from edition 5 having prior editions.",
        "The dormant standing talks channel is routed to samber/dev-event-organizer-skills@tech-podcast-youtube-channel.",
        "The developer-content and documentation push is recommended to the samber/developer-relations-skills collection.",
        "That sibling-repo hand-off is framed as a recommendation, never a dependency; the collection stays usable standalone.",
        "The sponsor-API hackathon-challenge question is kept inside this collection and routed to hackathon-brief-design.",
        "The response states the boundary: event operations wearing platform vocabulary stays here, while a genuine public-API, SDK, or sandbox surface question would go to samber/developer-platform-skills.",
        "Routes are named in owner/repo@skill form.",
        "No skill name outside the collection's routing tables is offered as a route."
      ]
    }
  ],
  "trigger_queries": [
    { "query": "Start a new event project - we want to run our first hackathon next spring.", "should_trigger": true },
    { "query": "Design an event-driven architecture for our order service.", "should_trigger": false },
    { "query": "Run my event check-in.", "should_trigger": true },
    { "query": "What's the difference between event sourcing and CQRS?", "should_trigger": false },
    { "query": "Which event skill do I need? Sponsors keep asking what they actually get.", "should_trigger": true },
    { "query": "I'm speaking at a Go conference next month - help me structure my talk.", "should_trigger": false },
    { "query": "Where do I start? We have a date and a venue and nothing else.", "should_trigger": true },
    { "query": "Debug why my Node.js event loop is blocked.", "should_trigger": false },
    { "query": "The conference finished last week. What now?", "should_trigger": true },
    { "query": "Should our startup sponsor a booth at a big cloud conference this year?", "should_trigger": false },
    { "query": "Kick off planning for our company's first developer conference.", "should_trigger": true },
    { "query": "Set up AWS EventBridge rules to fan out S3 events.", "should_trigger": false },
    { "query": "We just decided to launch a monthly Kubernetes meetup in Denver. Set me up.", "should_trigger": true },
    { "query": "Grow our developer community Discord from 500 to 5,000 members.", "should_trigger": false },
    { "query": "New project: an internal AI hackathon for 80 engineers in Q2.", "should_trigger": true },
    { "query": "Our Kafka event consumers keep lagging - help me tune them.", "should_trigger": false },
    { "query": "I'm starting to plan a DevFest-style community event for our city, where do I begin?", "should_trigger": true },
    { "query": "Write the agenda for our sprint kickoff meeting on Monday.", "should_trigger": false },
    { "query": "Bootstrap an event project for a two-day API summit we're dreaming about.", "should_trigger": true },
    { "query": "Plan my sister's wedding reception for 120 guests.", "should_trigger": false },
    { "query": "We got budget approved to run a user conference next year. Let's start.", "should_trigger": true },
    { "query": "Add a click event handler to this React component.", "should_trigger": false },
    { "query": "Spin up the planning workspace for our first unconference.", "should_trigger": true },
    { "query": "Review my CFP submission before I send it to a Python conference.", "should_trigger": false },
    { "query": "Begin organizing a student hackathon at our university.", "should_trigger": true },
    { "query": "Track custom analytics events in our mobile app funnel.", "should_trigger": false },
    { "query": "I want to organize a tech meetup but I've never run one. Start me off.", "should_trigger": true },
    { "query": "Plan our open-source project's launch on Hacker News.", "should_trigger": false },
    { "query": "Weekly check-in on the conference project, what's changed and what's next?", "should_trigger": true },
    { "query": "Design the webhook event payload schema for our public API.", "should_trigger": false },
    { "query": "Resume the DevSummit project where we left off.", "should_trigger": true },
    { "query": "Which KubeCon sessions should I attend for platform engineering?", "should_trigger": false },
    { "query": "It's been a month since I touched the meetup planning - catch me up and re-route.", "should_trigger": true },
    { "query": "Kubernetes is flooding me with FailedScheduling events, diagnose it.", "should_trigger": false },
    { "query": "Pick up our hackathon project again, the context file is in the repo.", "should_trigger": true },
    { "query": "Improve our API documentation so developers stop churning.", "should_trigger": false },
    { "query": "Event check-in time. Read the context and tell me what today's session should attack.", "should_trigger": true },
    { "query": "Plan our booth staffing for the trade show we're exhibiting at.", "should_trigger": false },
    { "query": "Back from vacation - where does the conference planning stand?", "should_trigger": true },
    { "query": "Implement domain events in our DDD aggregate.", "should_trigger": false },
    { "query": "Re-run the kickoff on the conference project we started in August.", "should_trigger": true },
    { "query": "Organize a neighborhood food-truck festival this summer.", "should_trigger": false },
    { "query": "Which skill in the event collection handles picking our conference date?", "should_trigger": true },
    { "query": "Start a developer newsletter for our product.", "should_trigger": false },
    { "query": "I can't tell if my question is a venue thing or a budget thing - route me.", "should_trigger": true },
    { "query": "How do I replay events from an event store after a bad deploy?", "should_trigger": false },
    { "query": "Is my satellite-meetup question side-event coordination or cross-event promotion?", "should_trigger": true },
    { "query": "Negotiate my speaker fee for a corporate tech summit.", "should_trigger": false },
    { "query": "Which skill do I load first: CFP design or speaker sourcing?", "should_trigger": true },
    { "query": "Sync calendar events from Google Calendar into our CRM.", "should_trigger": false },
    { "query": "Not sure which event skill covers overbooking and waitlists - point me.", "should_trigger": true },
    { "query": "Kick off the new client project with a discovery workshop template.", "should_trigger": false },
    { "query": "Where in this event skill set does 'should we even run this' live?", "should_trigger": true },
    { "query": "Write a trip report from the conference I attended last week.", "should_trigger": false },
    { "query": "Do any of the event skills cover refund processing on our ticketing platform?", "should_trigger": true },
    { "query": "Design the sandbox and test mode for our public API.", "should_trigger": false },
    { "query": "Which skill decides whether we need our first paid event staffer?", "should_trigger": true },
    { "query": "Write a Postgres trigger that fires an event on row insert.", "should_trigger": false },
    { "query": "Route this: our judges need a rubric for the projects teams built overnight.", "should_trigger": true },
    { "query": "Max out the ROI of our company's sponsorship of a partner's hackathon.", "should_trigger": false },
    { "query": "Our CFP closes in three weeks and we have zero reviewers lined up. Help.", "should_trigger": true },
    { "query": "Draft a project kickoff email to stakeholders for the CRM migration.", "should_trigger": false },
    { "query": "Ticket sales are way behind where they should be four months out.", "should_trigger": true },
    { "query": "Our event bus is dropping messages under load.", "should_trigger": false },
    { "query": "Our two-person team is drowning - the meetup grew to 400 people and nothing is written down.", "should_trigger": true },
    { "query": "Build our developer advocacy content calendar for the quarter.", "should_trigger": false },
    { "query": "Sponsors from last year haven't re-signed and their budgets close soon. What do I do first?", "should_trigger": true },
    { "query": "Help me network effectively at meetups as an introvert.", "should_trigger": false },
    { "query": "We announced the date but haven't figured out talks, tickets, or a venue.", "should_trigger": true },
    { "query": "Instrument page-view events for the marketing site.", "should_trigger": false },
    { "query": "Half our attendees didn't show last time. What should we change for the next edition?", "should_trigger": true },
    { "query": "Draft the expense report for my conference travel.", "should_trigger": false },
    { "query": "The venue wants a signed contract by Friday and I don't know what else that decision touches.", "should_trigger": true },
    { "query": "Set up a weekly team check-in ritual for my engineering squad.", "should_trigger": false },
    { "query": "Edition two planning starts now - last year's retro doc is in the repo.", "should_trigger": true },
    { "query": "Write a technical blog post about our new SDK.", "should_trigger": false },
    { "query": "We want to add a workshop day to our conference next year. Where does that start?", "should_trigger": true },
    { "query": "Handle window resize events efficiently in vanilla JS.", "should_trigger": false },
    { "query": "Our volunteer roster fell apart mid-event last time. Rebuild this properly.", "should_trigger": true },
    { "query": "Put together my kid's birthday party at the trampoline park.", "should_trigger": false },
    { "query": "Someone proposed merging our meetup with a bigger local conference. How do I even think about that?", "should_trigger": true },
    { "query": "Set up our app marketplace listing and review process.", "should_trigger": false },
    { "query": "I inherited a conference from an organizer who left; there's a repo full of files and no handover.", "should_trigger": true },
    { "query": "Pick which developer conferences our team should attend next year.", "should_trigger": false },
    { "query": "We're deciding between running a hackathon or a talks day for our community.", "should_trigger": true },
    { "query": "Model lifecycle events for our IoT devices in the schema.", "should_trigger": false },
    { "query": "Our first event broke even but exhausted everyone. Should edition two even happen?", "should_trigger": true },
    { "query": "Plan the kickoff for our Q3 marketing campaign.", "should_trigger": false },
    { "query": "The keynote speaker just cancelled six weeks out and I don't know what this breaks.", "should_trigger": true },
    { "query": "Prepare Q&A answers for my keynote at someone else's summit.", "should_trigger": false },
    { "query": "Two hundred people registered and we haven't planned check-in, badges, or signage.", "should_trigger": true },
    { "query": "Create an OSS contribution guide and governance model for our repo.", "should_trigger": false },
    { "query": "Our company wants to turn the annual user meetup into a real conference.", "should_trigger": true },
    { "query": "Set up Sentry to group error events by release.", "should_trigger": false },
    { "query": "How do I decide what to charge for tickets versus leaning on sponsors?", "should_trigger": true },
    { "query": "We're a devtools brand - build our strategy for sponsoring university hackathons.", "should_trigger": false },
    { "query": "A local tech company offered us their office space for our event - what does saying yes commit us to?", "should_trigger": true },
    { "query": "Onboarding kickoff checklist for a new hire's first week.", "should_trigger": false },
    { "query": "We need to pick between March and June for our developer summit.", "should_trigger": true },
    { "query": "Plan the logistics for our charity 5K fun run.", "should_trigger": false },
    { "query": "ok so my meetup kind of blew up and i have no clue what to do next lol", "should_trigger": true },
    { "query": "Improve webhook reliability and retries for our platform's integrators.", "should_trigger": false },
    { "query": "conference planning is a mess rn, everything feels urgent, what actually matters first", "should_trigger": true },
    { "query": "As an attendee, how do I get the most out of an unconference?", "should_trigger": false },
    { "query": "help, first-time organizer here, 5 months to doors and a blank google doc", "should_trigger": true },
    { "query": "Run a design-sprint kickoff for the mobile app redesign.", "should_trigger": false },
    { "query": "hackathon in the spring, three volunteers, no budget, where do we even start", "should_trigger": true },
    { "query": "Organize the school science fair for 30 student projects.", "should_trigger": false },
    { "query": "so we said yes to organizing the community day at a bigger conf... now what", "should_trigger": true },
    { "query": "Write my visa invitation request letter to attend a conference abroad.", "should_trigger": false },
    { "query": "my cofounder wants hybrid, i want in-person only, who's right and what do we do", "should_trigger": true },
    { "query": "Design our developer champions and ambassador program.", "should_trigger": false },
    { "query": "sponsor emails are piling up and i don't have a rate card or answers", "should_trigger": true },
    { "query": "Kick off our annual budget planning cycle for the finance team.", "should_trigger": false },
    { "query": "we keep meeting about the event and deciding nothing. fix our process", "should_trigger": true },
    { "query": "Evaluate the sponsorship prospectus this conference sent us.", "should_trigger": false },
    { "query": "300 people are coming in November and nothing is booked yet.", "should_trigger": true },
    { "query": "Increase our GitHub stars and README conversion.", "should_trigger": false },
    { "query": "Doors open in ten weeks and the run sheet doesn't exist.", "should_trigger": true },
    { "query": "Daily standup check-in questions for a remote dev team.", "should_trigger": false },
    { "query": "The CFP brought in 140 submissions and the committee is three friends and a spreadsheet.", "should_trigger": true },
    { "query": "Book a band and caterer for our village's summer fete.", "should_trigger": false },
    { "query": "We sold 40 of 500 seats and the on-sale started a month ago.", "should_trigger": true },
    { "query": "Review my resume for an event coordinator role at a tech company.", "should_trigger": false },
    { "query": "Our fiscal sponsor asked for the budget and I have a napkin.", "should_trigger": true },
    { "query": "What salary should I ask for as a conference producer?", "should_trigger": false },
    { "query": "The after-party, the badges, and the wifi are all still question marks.", "should_trigger": true },
    { "query": "Write interview questions to screen candidates for our event producer opening.", "should_trigger": false },
    { "query": "Next spring, 500 devs, two days - make it real.", "should_trigger": true },
    { "query": "Plan a surprise retirement party for my manager.", "should_trigger": false },
    { "query": "Same venue as last year or somewhere bigger? Everything else hangs on this.", "should_trigger": true },
    { "query": "Plan our product launch webinar funnel and follow-up emails.", "should_trigger": false },
    { "query": "Planning edition four - what carries over and what do we redo?", "should_trigger": true },
    { "query": "Build an email drip campaign for our SaaS trial users.", "should_trigger": false },
    { "query": "We run a conference and a podcast and now maybe a hackathon. Is that too many?", "should_trigger": true },
    { "query": "Create a code of conduct for our open-source GitHub project.", "should_trigger": false },
    { "query": "Post-mortem season: the event's done, the team's tired, the survey isn't out.", "should_trigger": true },
    { "query": "Design a landing page for our new devtool's beta signup.", "should_trigger": false },
    { "query": "Between editions our Slack goes silent. What's the plan for the gap?", "should_trigger": true },
    { "query": "Build the content-repurposing pipeline for our marketing team's webinars.", "should_trigger": false },
    { "query": "New year, same meetup - reset the routines and the plan.", "should_trigger": true },
    { "query": "Set up a risk register for our software delivery project.", "should_trigger": false },
    { "query": "Our conference should probably stay at 400 people, but the waitlist says otherwise.", "should_trigger": true },
    { "query": "Negotiate my job offer from an events agency.", "should_trigger": false },
    { "query": "Initialize the organizing project for a regional DevOps-days-style event.", "should_trigger": true },
    { "query": "Kick off the migration project from MySQL to Postgres.", "should_trigger": false },
    { "query": "As the new lead organizer, I need a structured restart of this event project.", "should_trigger": true },
    { "query": "Set up a farmers-market stall rotation for our co-op.", "should_trigger": false },
    { "query": "Map my event-organizing task onto the right skill in the collection.", "should_trigger": true },
    { "query": "Sync error events from our mobile SDK into the crash dashboard.", "should_trigger": false },
    { "query": "First planning session for a virtual summit our foundation wants to host.", "should_trigger": true },
    { "query": "Plan a DevRel hiring roadmap for next year.", "should_trigger": false }
  ]
}
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: 471kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall