samber/dev-event-organizer-skills / skills/event-community-building
event-community-building
VerifiedAnimate 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, how to make attendees come back next year, or who takes over the community platform when an organizer leaves. Do NOT use to decide whether that space belongs in the team's property set at all - use samber/dev-event-organizer-skills@event-portfolio-strategy.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 29.5 KB |
| evals/evals.json | config | 36.7 KB |
| references/cadence-and-content-shapes.md | markdown | 7.4 KB |
| references/community-asset-handoff.md | markdown | 6.7 KB |
| references/returning-participant-ladder.md | markdown | 6.0 KB |
| references/sibling-boundaries.md | markdown | 4.0 KB |
evals/evals.json
View on GitHub{
"skill_name": "event-community-building",
"evals": [
{
"id": 1,
"prompt": "We run PortoBuild, an annual developer conference in Porto, about 900 attendees, fourth edition wrapped two weeks ago. Our Discord (about 1,400 members, carried over from the conference) goes dead for most of the year. The team is buzzing right now and we've drafted a content calendar: twelve monthly themes (January is 'CI/CD month', February is 'observability month', and so on), each with weekly discussion prompts, a monthly live AMA, and new topic sub-channels. Everyone on the team is a volunteer with a day job; realistically after October nobody has hours until we start planning the next edition in spring. Can you review the plan and tell us what to post?",
"expected_output": "A between-editions cadence plan that rejects the twelve-theme calendar, chooses a posture the team's real quiet-months capacity can hold (dormant-but-open or a light pulse), names an owner, and includes a dated dormancy notice or a pulse plan fed from existing material.",
"files": [],
"expectations": [
"Rejects or substantially scales back the twelve-theme monthly calendar rather than refining, filling in, or endorsing it.",
"Grounds the cadence choice in who has recurring hours in the quiet months, not in the team's current post-edition enthusiasm.",
"Identifies the proposed plan (live AMAs, new sub-channels, standing prompts) as the heaviest cadence posture, which requires funded or guaranteed moderation capacity this volunteer team lacks.",
"Recommends dormant-but-open, or at most a light occasional pulse, as the posture for this team.",
"States that a recurring digest or spotlight rhythm is only viable when one named person holds recurring hours across the whole gap, and lapses otherwise.",
"Names, or requires the team to name, a single owner for the chosen posture, and states that a cadence with no named owner is not a decided posture.",
"Warns that a published calendar the team then abandons reads worse to members than deliberate, stated silence.",
"If dormancy is chosen, prescribes one pinned dated notice containing a date tied to the next build-up, a named owner, a conduct-report route that still works, and a promise small enough to keep.",
"States that dormancy keeps the archive readable and the member list intact and owned; it is not deleting or closing the server.",
"Any pulse plan proposed fills its slots from material that already exists (edition recordings, members' own posts) rather than requiring original content per slot.",
"Treats missed posting cycles as a signal to demote the cadence next gap, not as a team-discipline problem to push through.",
"Requires the member list to have a named owner and a written retention decision at the start of the gap, whatever cadence is chosen.",
"Does not set message-volume, engagement-rate, or activity targets for the space as success measures."
]
},
{
"id": 2,
"prompt": "Priya founded DataPipe Conf (annual, Bengaluru, six editions) and is stepping down at the end of next month. The community Slack, 2,100 members, is a workspace registered under her personal Gmail. She has already added Arjun, next year's lead, as a workspace admin, so we think access is sorted. Our team charter says leadership handovers run 6 to 12 months, so we were planning to stretch the community-platform transfer across the next year too. Priya also has the only export of the member email list on her laptop. She's a volunteer like the rest of us. What else should we tick off before she goes?",
"expected_output": "A community-asset handoff plan that transfers ownership of record first, refuses to borrow the team charter's 6-12-month window for the platform, inventories every asset with holder-today and holder-after, restates the member-list retention decision, and is dated with a review date.",
"files": [],
"expectations": [
"Identifies that adding Arjun as admin while the workspace stays registered to Priya's personal account leaves the space unrecoverable the day that account closes, so access is not sorted.",
"Requires transferring ownership of record of the workspace first, before rearranging admin roles.",
"Requires adding a second admin who is neither Priya nor Arjun, so the handoff does not produce a bus factor of one.",
"Rejects stretching the platform transfer across the charter's 6-12-month window, on the grounds that window covers the lead role while the platform account's timeframe is a separate deliberate call.",
"Prescribes a one-page written inventory listing each asset (workspace ownership, admin and moderator roles, billing, domain or vanity links, standing invite links, member-list export, archive, conduct reporting route) with a holder today and a holder after per row.",
"Treats any inventory row with no holder-after as the finding to resolve, not a blank to leave.",
"Requires the member-list export to move off Priya's laptop, with its format, location, and consent basis recorded and a named person able to reach it.",
"Restates the member-list retention decision explicitly at the handoff (named living owner, what members were told when they joined, permitted scope, a review-or-deletion date) rather than letting it be inherited by silence.",
"Checks that the conduct-reporting route resolves to someone who will still be reading it after Priya leaves.",
"Prescribes posting to the space, in the event's established voice, that ownership of the space and the data has changed.",
"Dates the handoff document and sets a next review date.",
"Frames the handoff as something a departing volunteer will want to complete, not as an employee offboarding procedure with enforceable obligations.",
"Runs the transfer as a session with both people present, filling the inventory together, not as a document sent to the person leaving.",
"Separates the community-asset transfer from the team/decision-rights handover and from the operational learning log, treating them as distinct artifacts rather than one bundle."
]
},
{
"id": 3,
"prompt": "GridForge Summit is our annual open-source energy-software conference in Berlin, about 1,200 people. Community members in Lisbon, Krakow and Zagreb have each asked to run 'GridForge Lisbon' style local editions under our banner, and honestly it sounds like free growth. Can you draft the chapter program for us: chapter-lead application form, brand usage guidelines, quality standards for local events, and a plan to keep those local groups engaged in our Discord between summits?",
"expected_output": "An answer that splits the request in two, declines the chapter/brand-licensing half as out of scope, and delivers only the engagement half: per-city threads on the existing surface, a named local member per city, the same content feed, one member list under one retention decision.",
"files": [],
"expectations": [
"Applies the decisive test of whether anyone outside the organizing team would run an event under the event's name, and classifies the chapter request as governance and brand licensing.",
"Declines to draft the chapter-lead application form, brand usage guidelines, and local-event quality standards, rather than producing them.",
"States plainly that licensing the brand to independently-run local editions is a gap it has no playbook for, instead of quietly improvising an answer.",
"Splits the request into a governance half and an engagement half, and answers only the engagement half.",
"The engagement half stays on the team's own surface: per-city threads or sub-spaces inside the existing Discord, run by the organizing team.",
"Recommends finding a named local member willing to keep each city thread warm.",
"Feeds the city threads the same digest and spotlight stream the main space gets, rather than inventing separate local programming.",
"Keeps local members in the same member list under the same retention decision, not in per-city lists.",
"Warns concretely that letting the brand question ride informally fails at the first incident at an event carrying the name that the team did not organize.",
"Does not treat 'free growth' as a reason to proceed, and makes no growth recommendation.",
"Does not reframe the local groups as external partner events to cross-promote with.",
"Tells the user explicitly which half of their request was answered and that the governance half needs a decision path this plan does not provide."
]
},
{
"id": 4,
"prompt": "ShipItCon (annual, Dublin) here. Two wins to run past you. One: we changed registration so every ticket buyer is now automatically added to our Circle community. Membership jumped from 600 to 2,900 overnight, and the sponsor prospectus now leads with 'a 2,900-member developer community'. Two: the community has been quiet since August, so our first post of the year will announce that early-bird tickets are live, ends Friday, book now, and we'll email the whole list too. Sound good?",
"expected_output": "A response that reverses both 'wins': auto-enrollment is rejected on consent grounds and the sponsor figure corrected, and the sales blast is replaced by a re-engagement touchpoint that references the past edition, makes one cheap ask, and is signed by a person.",
"files": [],
"expectations": [
"Rejects auto-enrolling ticket buyers as community members rather than optimizing or softening it.",
"Gives the consent reason: the ticketing sign-up granted consent for a different purpose, and community membership was never part of what was granted.",
"Identifies the 2,900 figure as a manufactured membership number and flags leading the sponsor prospectus with it as misrepresentation.",
"Recommends an opt-in path into the community for ticket buyers instead of automatic enrollment.",
"Rejects 'tickets are live, ends Friday, book now' as the first contact after months of silence.",
"Explains the specific damage of the sales blast: it converts the warmest people who were coming anyway, and teaches everyone else the space only contacts them to sell.",
"The replacement first contact references something that happened (the edition they attended, what members shipped), because members have a memory of the past edition and none of the announced one.",
"The replacement makes one low-cost ask that is not 'buy', such as answering a call for talks, naming a topic, or saying whether they are coming.",
"The replacement is signed by a named person and written in the event's established voice.",
"States that contact with the attendee list rides on the consent basis it was collected under, an inherited duty, not a fresh policy invented for the community.",
"Requires correcting the membership number given to sponsors to genuinely opted-in members, not keeping 2,900 with a caveat."
]
},
{
"id": 5,
"prompt": "KernelDays is a systems-programming conference that runs once a year in Helsinki. To keep our forum alive between editions we're building a points system: badges for posting, a monthly leaderboard, levels that unlock a 'Community Champion' title, and we'll feature the top three champions with photos on the conference homepage. A volunteer already built a prototype bot. We also want the ladder to eventually feed people toward helping organize. Thoughts?",
"expected_output": "A rejection of the points/leaderboard scheme with the three reasons it fails an annual-cycle audience, replaced by a small named-step ladder whose rungs are asynchronously climbable, with consent gates on public naming and the organizer-candidate endpoint routed out.",
"files": [],
"expectations": [
"Rejects the points, badges, and leaderboard scheme for an audience that meets once a year, rather than tuning its parameters.",
"States that the scheme measures posting volume, which is not the outcome the space exists for (people returning to the next edition, some bringing work).",
"States that the scheme rewards the loudest members rather than the returning ones.",
"States that the scheme demands maintenance in exactly the months the team has no hours.",
"Replaces it with a small ladder of named steps (attendee, regular, contributor shaped), each step with a stated way in and a stated reward.",
"Requires every step above the first to be climbable entirely asynchronously, because an annual event gives one live touch per year.",
"Requires each step's way in to work without personally knowing an organizer, so the ladder is not a clique with a diagram.",
"Requires asking consent before publishing anyone's name or photo as a champion or regular, with an opt-out that needs no explanation.",
"Routes the 'feed people toward helping organize' endpoint to the team-structure candidate flag, and stops the ladder there rather than building organizer recruitment into the community mechanism.",
"Scopes the mechanism to non-volunteer members, with volunteer recognition handled by its own separate loop.",
"Reports ladder movement as a raw count of members who moved a step, never as a rate or percentage.",
"Ties success to attendees returning next edition rather than to posting frequency, streaks, or leaderboard positions."
]
},
{
"id": 6,
"prompt": "Our board asked for community KPIs for RustReef (annual conference, 2,800 attendees, 3,100-member Slack). Draft proposal: (a) daily active members and monthly message volume as the headline numbers; (b) we read that the events industry's blended retention rate is barely above 30 percent, so we'll commit to beating it with a 45 percent return-rate target next edition; (c) a community consultant told us healthy communities follow the 5/12/45 group-size thresholds, and with only about 50 people talking out of 3,100 we're failing badly and need an activation push. Can you finalize the KPI sheet?",
"expected_output": "A KPI sheet centered on carry rate as a self-set threshold plus three binary gates, with the 30 percent industry figure demoted to context, the 5/12/45 numbers corrected and ruled inapplicable to a member list, and the activation push rejected.",
"files": [],
"expectations": [
"Rejects daily active members and message volume as headline KPIs, naming the failure: they measure the space, not whether the edition's audience returns.",
"Makes the share of one edition's attendees who register for the next one (carry rate) the central outcome number.",
"Treats the roughly 30 percent blended industry retention figure as evidence that return rates run lower than teams assume, and explicitly not as a target or baseline to beat.",
"Notes that the blended figure mixes every event type, none of them a technical conference, so it cannot anchor a commitment.",
"Requires the carry-rate threshold to be self-set and fixed before the gap starts, not derived from the industry figure or set after the data arrives.",
"Identifies 5/12/45 as a misquote of the community-size threshold series (the actual sequence being 7, 13, 50, 90, 150).",
"States that those thresholds describe groups with ongoing interaction and say nothing about a member list, which is a stock, not a group.",
"States that around 50 active talkers out of 3,100 members is a normal shape for an event's space, not a failure, and rejects the activation-push premise.",
"Includes a binary gate for cadence kept: posts planned versus posts actually made across the gap, on the chosen posture.",
"Includes a binary gate for list integrity: a named owner and a written retention decision for the member list on the day the gap starts.",
"Includes a binary gate for handoff readiness: a dated access document naming a living holder for every account, checked on a schedule.",
"Positions the carry rate as evidence handed onward to the demand/market-fit read, not as a growth recommendation the community plan itself makes.",
"Labels every threshold on the sheet as self-set rather than presenting any as an industry benchmark."
]
},
{
"id": 7,
"prompt": "Two things for FjordSec, our annual security conference in Oslo. First: on stage we're quite formal, sober and precise, no memes, but that feels heavy for the Discord in the off months, so we want to write a second, cosier 'off-season voice' guide for the community mods: more casual, more emoji, more banter. Second: to bridge the ten-month gap we'd like to run a small quarterly meetup, a borrowed office, 40 seats, one invited speaker each time. Can you write the voice guide and sketch the quarterly format?",
"expected_output": "A refusal on both counts: the off-season voice is written as a delta against the fixed register rather than a second voice, and the quarterly meetup is routed out as an event property, with in-scope gap-bridging alternatives offered instead.",
"files": [],
"expectations": [
"Refuses to author a second, separate off-season voice guide.",
"States the principle that the event's identity or register is fixed and only its expression modulates between editions.",
"Prescribes a delta document mapping each existing register attribute to its between-editions expression, instead of a standalone tone guide.",
"Covers the hardest rows of that delta: what the register sounds like when nothing has happened, and when the news is somebody else's.",
"Requires the existing register as input, and if none has been decided, routes to fix that first, labeling anything written before it as provisional.",
"Declines to sketch the quarterly meetup format.",
"Gives the reason: a touchpoint that needs a venue, a schedule, or an invited speaker is an event property, not a between-editions community tactic.",
"Routes the quarterly-meetup question to the portfolio-level property decision rather than answering it inside the community plan.",
"Offers in-scope gap-bridging alternatives on the existing surface (a digest, a member spotlight, discussion threads) that need no venue, schedule, or speaker.",
"Does not offer the cosy second voice as a compromise, pilot, or A/B option alongside the recommendation.",
"Presents the between-editions expression for approval before the mods change anything members can see."
]
},
{
"id": 8,
"prompt": "CloudCamp Antwerp wrapped in September. The edition comms team archived the attendee announcement channels on their published wind-down date and left #general plus the per-team project channels running; that's now mine to run until next summer. Three questions. One: can I reorganize the surviving channels? I'd fold the small per-project channels into #general to tidy up, and I think their wind-down archived some channels too aggressively, so I want to restore two. Two: about 60 past volunteers are in the space, and I'd like to build them a recognition program with a dedicated volunteers server. Three: next edition's comms lead asked what I'll give them at build-up, and I said 'the Discord will still be there'. Anything wrong with that?",
"expected_output": "An answer that keeps the per-project channels, refuses to reverse the wind-down, routes volunteer recognition to its own loop as a segment inside the existing surface, and replaces 'the Discord will still be there' with a live member-list handback carrying consent basis and reachable count.",
"files": [],
"expectations": [
"Rejects folding the per-project channels into #general, because a returning member reopens the channel scoped to their project and the general channel does not replace that.",
"Refuses to restore the two archived channels or otherwise reverse the edition team's wind-down decisions; the between-editions role starts where wind-down ended.",
"Does not redesign the edition's channel roster or routing rules in any other way.",
"Declines to build the volunteer recognition program, because the volunteer alumni loop (list, thank-you, candidate flag) belongs to its own owner, not to the community role.",
"Rejects a dedicated second volunteers server; past volunteers run as a segment inside the existing surface.",
"Scopes the between-editions programming audience to non-volunteer members.",
"States that 'the Discord will still be there' is not a handback.",
"Specifies the handback as a live member list: who joined, on what consent basis, and who is actually reachable.",
"Times the handback to the next edition's build-up, when the new edition's channels open.",
"Establishes the user as the named owner of the space for the gap, with the conduct-report route stated as still monitored.",
"Requires the member list's owner and retention decision to be settled now, at the start of the gap, not at handback.",
"Frames the role as two handovers: receiving the space at wind-down and returning the live list at build-up."
]
},
{
"id": 9,
"prompt": "For NimbusFest (annual, Toronto, fifth edition coming), our long-standing hygiene practice is to delete the community Slack about a month after each edition and spin up a fresh workspace the next spring: clean slate, no stale channels, and our privacy-minded co-organizer likes that it 'solves data retention automatically'. This year someone objected, so before we delete: how long are we actually allowed to keep member data under PIPEDA? If you know the exact retention period, put it in our policy doc along with the deletion date.",
"expected_output": "A response that stops the delete-and-reopen cycle for a recurring event, refuses to quote any jurisdiction's retention period and routes that ruling to counsel, and writes the retention decision as four fields with a concrete review date.",
"files": [],
"expectations": [
"Rejects deleting and reopening the workspace each edition for a recurring event, rather than endorsing it as hygiene.",
"States what deletion actually discards: the member list and the archive, which are the community asset itself.",
"Notes that export-plus-deletion is a legitimate end state only for a one-off edition, not a recurring event.",
"Rejects 'deletion solves data retention automatically': a retention decision is a deliberate written artifact, not a side effect of clean-up.",
"Declines to quote a PIPEDA retention period, or any jurisdiction's, and does not write one into the policy doc.",
"Routes the actual retention ruling to the organizer's own counsel.",
"Prescribes the retention decision as four fields: a named living owner, the basis in the words members were told at join, the permitted scope, and a review-or-deletion date.",
"Distinguishes scope grants: 'announcing our own next edition' and 'anything the team decides later' are different scopes, and only the one granted applies.",
"States that the retention duty is inherited from the sign-up and attendee-list consent framework, to be restated, not re-derived as a second policy.",
"Requires the review-or-deletion date to be a concrete date, not 'when it stops being useful'.",
"Presents the dormant alternative: archive readable, member list intact and owned, one dated notice, at near-zero effort, so deletion is not the cheap option it looks like.",
"Requires the retention decision to be restated at every future handoff rather than inherited silently."
]
}
],
"trigger_queries": [
{ "query": "Our conference Discord is a ghost town for eleven months a year. What should we actually be posting?", "should_trigger": true },
{ "query": "How do we keep our annual developer conference's community warm between editions?", "should_trigger": true },
{ "query": "Half our attendees are brand new every year. How do we get last year's people to come back?", "should_trigger": true },
{ "query": "Our founder is stepping down and the community Slack is registered to her personal account. What has to happen before she leaves?", "should_trigger": true },
{ "query": "Should our event's Slack go dormant until the next announcement, or should we keep programming it year-round?", "should_trigger": true },
{ "query": "What do we do with the attendee community in the ten months between conferences?", "should_trigger": true },
{ "query": "conf ended in june, server's dead til next spring. post something or let it sleep?", "should_trigger": true },
{ "query": "Write a between-editions plan for our event's community server.", "should_trigger": true },
{ "query": "People in three other cities want to run a local version of our conference. Is that ours to say yes to?", "should_trigger": true },
{ "query": "How should we hand over the community platform to the next organizing team?", "should_trigger": true },
{ "query": "The next edition just got announced. What's the first message we send to last year's attendee list after months of silence?", "should_trigger": true },
{ "query": "Is deleting our event's Slack every year and starting fresh a bad idea?", "should_trigger": true },
{ "query": "We want a badges-and-leaderboard system to keep the community active between summits. Good idea?", "should_trigger": true },
{ "query": "What does a good dormancy notice look like for a community space that's quiet until next year?", "should_trigger": true },
{ "query": "Who should own our event's member list now the edition is over, and how long do we keep it?", "should_trigger": true },
{ "query": "Our hackathon runs once a year and the Discord dies in between. Digest, or just let it rest?", "should_trigger": true },
{ "query": "We meet once a year and I want regulars to end up contributing talks and reviews. What's the path from attendee to contributor?", "should_trigger": true },
{ "query": "How do I measure whether our between-editions community work is actually paying off?", "should_trigger": true },
{ "query": "What's a sane posting cadence for the quiet months when no edition is imminent?", "should_trigger": true },
{ "query": "Our organizer is leaving next month. Checklist for transferring the community server, member list and invite links?", "should_trigger": true },
{ "query": "Keep the fans of our annual tech event engaged in the off-season. Where do we start?", "should_trigger": true },
{ "query": "The conference is over and everyone's asking what happens to the Slack now. Advice?", "should_trigger": true },
{ "query": "How do we turn one-time attendees into people who come back and bring a talk with them?", "should_trigger": true },
{ "query": "We promised the community 'lots of exciting stuff soon' after the event and then went silent for five months. How do we recover?", "should_trigger": true },
{ "query": "Between-editions engagement: should we do monthly AMAs or just a quarterly digest?", "should_trigger": true },
{ "query": "Members in Lyon want their own local chapter of our event's community. How do we keep them engaged without licensing the brand?", "should_trigger": true },
{ "query": "What belongs in the handoff document when the person who runs our community server rotates out?", "should_trigger": true },
{ "query": "Months after the conference, our surviving community server still has per-project channels. Fold them into general to tidy up?", "should_trigger": true },
{ "query": "How early before the next edition do we wake the community space up, and who hands what to whom?", "should_trigger": true },
{ "query": "Our event's community feels like it only hears from us when we want to sell tickets. How do we fix that?", "should_trigger": true },
{ "query": "The team wants to auto-add all ticket buyers to our community platform. Any downside?", "should_trigger": true },
{ "query": "What should the one re-engagement email to past attendees say when registration opens?", "should_trigger": true },
{ "query": "Annual conf, volunteer team, zero hours between editions. What's the least we can do without the space looking abandoned?", "should_trigger": true },
{ "query": "How do we decide between letting the community space idle and running a monthly digest in it?", "should_trigger": true },
{ "query": "Who's on duty for our community space in the months when nothing is happening?", "should_trigger": true },
{ "query": "Our event community's member count looks great but nobody comes back next year. What are we doing wrong?", "should_trigger": true },
{ "query": "Give me a lightweight plan so the community server never reads as abandoned between conferences.", "should_trigger": true },
{ "query": "The previous organizer left and took the admin account with them. How do we stop this happening again?", "should_trigger": true },
{ "query": "attendees loved the conf, joined the discord, went quiet. how do i get them back for next year's edition?", "should_trigger": true },
{ "query": "Draft the quarterly digest plan for our conference community's quiet season.", "should_trigger": true },
{ "query": "Do community-size thresholds like Dunbar's number apply to our event's 4,000-member mailing list?", "should_trigger": true },
{ "query": "Our conference community's carry-over rate to the next edition is terrible. Where do we start?", "should_trigger": true },
{ "query": "What consent do we need before featuring a community member by name as a 'regular' on our site?", "should_trigger": true },
{ "query": "Between two editions, what jobs should our standing community space explicitly not take on?", "should_trigger": true },
{ "query": "We're rotating organizers every two years. How do we make the community platform survive each rotation?", "should_trigger": true },
{ "query": "One month after the event: what do we tell the community server about the coming year?", "should_trigger": true },
{ "query": "How do I keep a city-specific group of our event's fans warm between our visits?", "should_trigger": true },
{ "query": "Plan the wake-up: our community was dormant and next edition's build-up starts in six weeks.", "should_trigger": true },
{ "query": "Is it OK that our community Slack's only owner is a role nobody currently fills?", "should_trigger": true },
{ "query": "The board wants engagement KPIs for our event's community. What should I actually report?", "should_trigger": true },
{ "query": "Design the Slack channel structure for this year's conference: which channels exist and who's in each?", "should_trigger": false },
{ "query": "When and how should we wind down the attendee channels after the event ends?", "should_trigger": false },
{ "query": "Which class of announcement goes to email versus the event Discord during conference week?", "should_trigger": false },
{ "query": "Should our organizing team add a year-round online community to our portfolio alongside the conference and the hackathon?", "should_trigger": false },
{ "query": "Would a quarterly meetup feeding our flagship conference make sense as a new property?", "should_trigger": false },
{ "query": "Design a thank-you and recognition program for this year's conference volunteers.", "should_trigger": false },
{ "query": "How do we keep our past volunteers engaged so they sign up again next year?", "should_trigger": false },
{ "query": "Set up a newsletter swap and discount-code exchange with a friendly conference in another city.", "should_trigger": false },
{ "query": "Another event wants to promote theirs to our audience in exchange for promoting ours. How do we structure the deal?", "should_trigger": false },
{ "query": "Help us define our conference's register, hacker or corporate, and how it shows up in swag and stage production.", "should_trigger": false },
{ "query": "Our conference sells out every year. Should we add a second track or move to a bigger venue?", "should_trigger": false },
{ "query": "Write a code of conduct for our conference and its online spaces.", "should_trigger": false },
{ "query": "How do we launch a Discord community for our developer-tools startup?", "should_trigger": false },
{ "query": "Which health metrics and dashboards should we track for our product's developer community?", "should_trigger": false },
{ "query": "Design the moderation policy and enforcement ladder for our company's community forum.", "should_trigger": false },
{ "query": "Build an ambassador program with perks for our SaaS's power users.", "should_trigger": false },
{ "query": "How do we grow attendance at our monthly JavaScript meetup?", "should_trigger": false },
{ "query": "Our monthly meetup is outgrowing an evening. How do we turn regulars into co-organizers?", "should_trigger": false },
{ "query": "Plan the event's social media calendar for the ticket-sales campaign.", "should_trigger": false },
{ "query": "Write the attendee email sequence from registration through know-before-you-go.", "should_trigger": false },
{ "query": "Design the post-event feedback survey for attendees and speakers.", "should_trigger": false },
{ "query": "What do we do with the talk recordings after the conference: publishing cadence and licence?", "should_trigger": false },
{ "query": "Our event lead is stepping down. Design the succession plan for the organizer role and decision rights.", "should_trigger": false },
{ "query": "Turn five years of post-event debrief notes into a learning log the next team can act on.", "should_trigger": false },
{ "query": "Should our conference start its own podcast to stay visible between editions?", "should_trigger": false },
{ "query": "How do we vet the third-party side events that want to run during our conference week under our umbrella?", "should_trigger": false },
{ "query": "Is there enough demand in our city for a second edition of our conference?", "should_trigger": false },
{ "query": "Build the attendee-acquisition marketing plan for next year's edition.", "should_trigger": false },
{ "query": "How do I build a community-led growth motion for my B2B startup?", "should_trigger": false },
{ "query": "Grow our open-source project's Discord server and recruit contributors.", "should_trigger": false },
{ "query": "Plan the launch of a user community for our API product, from platform choice to seeding.", "should_trigger": false },
{ "query": "Draft the sponsorship prospectus highlighting our engaged developer community.", "should_trigger": false },
{ "query": "Design the on-site hallway-track and networking experience for attendees.", "should_trigger": false },
{ "query": "Set up the call for papers for next year's conference.", "should_trigger": false },
{ "query": "We're launching our first conference. Walk me through edition one from zero.", "should_trigger": false },
{ "query": "How should we price tickets to reward returning attendees with an alumni discount?", "should_trigger": false },
{ "query": "Which channels should the marketing plan use to reach last year's attendees during the campaign?", "should_trigger": false },
{ "query": "Moderate our subreddit better. We're drowning in spam.", "should_trigger": false },
{ "query": "How do we pick between running a hackathon and an unconference as our next event?", "should_trigger": false },
{ "query": "Keep our customers engaged in our product's Slack between quarterly feature releases.", "should_trigger": false },
{ "query": "Design the volunteer shift plan and roster for this edition.", "should_trigger": false },
{ "query": "Our DevRel team wants a champions program tied to our annual user conference: perks and intake.", "should_trigger": false },
{ "query": "Plan our event's X content for the speaker-reveal campaign phase.", "should_trigger": false },
{ "query": "How many admins should our company's community Slack have, and what's the moderator rotation?", "should_trigger": false },
{ "query": "Write the wind-down message announcing the conference channels will close next Friday.", "should_trigger": false },
{ "query": "Our conference brand is being used by an unaffiliated meetup. How do we enforce our trademark?", "should_trigger": false },
{ "query": "Recruit mentors from our community for the hackathon this spring.", "should_trigger": false },
{ "query": "Set up a monthly community call for users of our open-source library.", "should_trigger": false },
{ "query": "How do we structure our organizing team so it survives turnover?", "should_trigger": false },
{ "query": "Announce our partner conference's CFP to our community. What do we ask for in return?", "should_trigger": false }
]
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |