samber/dev-event-organizer-skills / skills/event-first-edition
event-first-edition
VerifiedLaunch the first edition of a tech event (conference, hackathon, large meetup) from zero - a minimum viable edition 1, scope discipline against the full vision, the first cross-organization team, the decision-to-doors-open reverse timeline, and a pre-mortem of first-edition-specific risks with written go/no-go dates. Use whenever asked to start a new conference or hackathon, plan a first edition, scope a minimum viable event, form a founding organizer team, or set a launch timeline for an event with no track record. Strategy layer for edition 1 only. Do NOT use to validate demand first - use samber/dev-event-organizer-skills@event-market-fit - or to grow an established event - use samber/dev-event-organizer-skills@event-growth-strategy.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 22.0 KB |
| evals/evals.json | config | 30.3 KB |
| references/first-edition-premortem.md | markdown | 4.7 KB |
| references/reverse-timelines.md | markdown | 8.0 KB |
| references/scope-and-appetite.md | markdown | 4.7 KB |
evals/evals.json
View on GitHub{
"skill_name": "event-first-edition",
"evals": [
{
"id": 1,
"prompt": "I'm the DevRel lead at Parqet Labs (we make a stream-processing engine). My colleague Tomas and I decided yesterday to launch 'StreamSummit', an independent community conference for streaming-data engineers, next year. We haven't asked anyone whether they'd come yet, but streaming is exploding right now so we know there's appetite. We plan to prove edition 1 worked by tracking viral coefficient, CAC versus LTV, and month-over-month cohort retention of attendees. Please give us the complete launch plan: venue, program, budget, marketing, the works.",
"expected_output": "The response withholds the requested launch plan and gates on demand validation first, routing to a demand-validation step; it rejects the Lean growth-engine metrics as unusable for a single edition and flags the two-person single-company founding team.",
"files": [],
"expectations": [
"The response does not deliver the requested complete launch plan (venue, program, budget, marketing) in this turn.",
"Demand validation is required before any launch planning, with the user routed to a demand-validation step or the event-market-fit sibling skill.",
"The team's own conviction ('streaming is exploding, we know there's appetite') is explicitly classified as unvalidated opinion or stated interest, not evidence.",
"Concrete acceptable validation evidence is named, such as waitlist signups, a sold-out precursor meetup, or an existing community asking for the event.",
"Viral coefficient, CAC/LTV, and cohort retention are rejected as edition-1 success measures because they measure sustained usage over time, which a single edition cannot generate.",
"The rejected growth metrics are redirected to their proper home (growing an established event / the event-growth-strategy sibling), not merely deleted.",
"Demand validation and edition sizing are distinguished as two sequential, different decisions: an event with real demand can still over-scope or under-scope its launch.",
"The two-colleague, single-company founding team is flagged against the floor of at least three organizers from at least three different organizations for a community-run event."
]
},
{
"id": 2,
"prompt": "We validated demand properly: our monthly DataStack Lisbon meetup sells out at 250 people within hours, and the conference waitlist we opened two months ago has 1,100 signups. Now we want to go big for edition 1 of DataStack Conf: simultaneous launches in Lisbon, Porto, and Madrid on the same weekend, two tracks in each city, an expo hall, a livestream, and a custom mobile app for attendees. There are five of us across four companies, all with day jobs, and we can each put in about 6 hours a week. Our plan is to design the dream program first and then work out what it costs. A friend of mine ran a 600-person conference in Barcelona last year, by the way. What should edition 1 look like?",
"expected_output": "A right-sized edition-1 recommendation: the multi-city launch is ruled out entirely, appetite is set before program design, a scope tier is chosen from the standalone/borrowed/full-footprint menu with candidates and trade-offs, written no-gos are produced, and the friend's real budget number is requested.",
"files": [],
"expectations": [
"The three-city simultaneous launch is ruled out for a first edition outright - not ranked last, kept as a stretch goal, or deferred to a later phase of edition 1.",
"Appetite (the organizer hours and money this launch is worth) is set before the program is designed; the user's 'dream program first, cost later' ordering is explicitly reversed.",
"The stated capacity (five organizers at roughly 6 hours a week alongside day jobs) is used to bound the scope.",
"A scope tier is recommended from a named menu of edition-1 shapes (single-focus standalone, borrowed edition, full-footprint edition), with 2-3 candidate shapes presented with trade-offs and a recommendation.",
"The recommendation is a single-city, single-track edition (single-focus standalone, or an explicitly argued borrowed edition) - not the full-footprint shape.",
"Written, named no-gos for edition 1 are produced (for example: no second track, no livestream, no custom app, no multi-city).",
"The custom mobile app is identified as a rabbit hole or no-go for edition 1, with an off-the-shelf substitute (ticketing platform built-ins or a form) acceptable instead.",
"The response recommends asking the friend who ran the comparable Barcelona conference for their actual budget number.",
"Full-footprint is not silently discarded: the condition that would promote it (committed budget plus evidence-backed audience of several hundred) is stated.",
"The user is asked to validate the scope-tier choice before the plan proceeds.",
"Scaling beyond the minimal tier is tied to real registrations actually claimed, not to enthusiasm or the size of the waitlist.",
"The team gate is acknowledged as passed: five organizers from four companies meets the three-organizers-from-three-organizations floor."
]
},
{
"id": 3,
"prompt": "Quick sanity check. I run developer relations at Hexlify, and my teammate Priya (also at Hexlify) and I are organizing EdgeConf Manchester as an independent community conference - it's not a Hexlify event, we just both happen to work there. Demand is solid: our meetup waitlist converted into 180 paid pre-registrations. The venue we love has one date left in October and we're signing the contract on Monday. We tried to get people from other companies involved but nobody committed yet. We'll recruit more organizers after the venue is locked. Good to go?",
"expected_output": "A block on Monday's signing: the two-person single-company team fails the three-organizers-from-three-organizations gate, which must pass before venue or date is locked; the failed outside recruitment is itself read as an early market warning.",
"files": [],
"expectations": [
"The response says the team is not good to go and advises against signing the venue contract on Monday.",
"The team gate is stated: at least three organizers from at least three different organizations before venue or date is locked.",
"Two organizers from the same single company is explicitly identified as failing that gate.",
"The gate's purpose is given: it blocks single-company vanity events and protects the cross-organization neutrality a community-run event's credibility rests on.",
"The inability to recruit outside co-organizers is read as an early demand or market warning signal, not merely a staffing inconvenience.",
"Recruiting the missing organizers is sequenced before venue lock - the user's 'recruit after the venue is locked' order is reversed.",
"The stated intent that 'it's not a Hexlify event' is not accepted as a substitute for actual cross-organization team composition.",
"A solo or two-person launch is not offered as an acceptable fallback.",
"The 180 paid pre-registrations are acknowledged as strong validation evidence, while making clear that passing the validation gate does not waive the team gate."
]
},
{
"id": 4,
"prompt": "We're a founding team of four (four different companies) launching QueueCraft, a message-queue community conference in Rotterdam. The announcement post and landing page go live this Friday. The page lists my personal Gmail as the contact address, since I'm the one checking email anyway. We figured we'd write a code of conduct closer to the event, once the venue and date are settled - no point publishing rules for an event that doesn't have a location yet. Anything we're missing before Friday?",
"expected_output": "The Friday launch is held until the administrative gate passes: code of conduct published before the first public listing (earlier than venue or date), a neutral shared contact alias replacing the personal Gmail, a shared credential vault, and a peer-organizer network joined.",
"files": [],
"expectations": [
"The code of conduct is required to be published before Friday's announcement, and the 'no point until venue and date are settled' reasoning is rejected.",
"The CoC is identified as the earliest hard administrative gate in the launch sequence - ahead of venue and ahead of date.",
"The personal Gmail is replaced with a dedicated, neutral shared event email alias.",
"The reason for the alias is stated: a personal or company address makes one organizer or their employer look like the event's owner, damaging a community-run event's neutrality.",
"A shared credential vault for vendor, social, and ticketing logins is prescribed rather than one organizer's personal password manager.",
"Joining a peer-organizer network for cross-event mentorship is recommended.",
"The response notes a first public listing needs only organizer names, city, and a coming-soon notice - no date or venue is required for it.",
"The content of the code of conduct is routed to the code-of-conduct sibling skill or explicitly marked out of scope, rather than drafted inline as the main deliverable.",
"The administrative items are framed as a gate that must pass before any public announcement, not as follow-ups to complete after going live.",
"The response does not approve going live on Friday with the current setup."
]
},
{
"id": 5,
"prompt": "TerraNimbus (my employer) is sponsoring my volunteer time to organize InfraDays Krakow as an independent community conference - one day, single track, around 250 infrastructure engineers, demand validated through our 400-member meetup's waitlist. Hard constraint: it has to happen in 7 months, during the city's big annual tech week, because that's our fifth meetup anniversary. I read that conferences take about 12 months to organize and hackathons 4 to 9, so splitting the difference I planned for 8 months, which means at 7 we're basically fine. Also useful: TerraNimbus has offered its 280-seat auditorium for free, and we want this to become an annual fixture in the region. How should I adjust the plan?",
"expected_output": "The 8-month average is rejected in favor of the conference-scale ~12-month baseline; the 7-month deadline triggers compression levers with the borrowed venue promoted, the invited-speaker trade-off weighed against the annual-asset mandate, the tech-week slot recognized as piggybacking, and go/no-go dates that cut scope while the date holds.",
"files": [],
"expectations": [
"Averaging the conference and hackathon timelines into roughly 8 months is rejected: the gap is format-driven (CFP pipeline, venue lead time, event duration), not a range to interpolate.",
"The conference-scale reverse timeline of roughly 12 months is applied as this event's baseline, not the hackathon-scale 4-9 months.",
"The 7-month deadline is treated as shorter than the format's runway, which triggers timeline-compression levers rather than a generic replan.",
"The borrowed-venue lever is promoted because of the offered auditorium, with the reasoning that venue search is the longest lead item in the conference timeline (starting around T-12 months).",
"The employer-offered auditorium is accepted and used as a compression lever, not rejected.",
"The invited-speaker lever is presented with its stated cost: the submission volume and program quality a long CFP buys, plus the community-openness signal.",
"The invited-speaker cost is weighed against the user's stated annual compounding-asset ambition, rather than the lever being recommended cost-free.",
"The tech-week slot is recognized as piggybacked scheduling (co-locating with an anchor event so travelling attendees justify both), with its coordination cost or calendar dependence noted.",
"Cutting a scope rung is stated as the default lever and standing circuit breaker.",
"The date is held fixed: any unready scope item gets cut, and the timeline is never extended.",
"The reason the date never moves is given: extending the timeline burns speaker, sponsor, and attendee trust an unknown first-edition event does not yet have.",
"Go/no-go dates are written into the plan, each paired with the scope item or budget tier it downgrades."
]
},
{
"id": 6,
"prompt": "Our founding team - Ana at Brightloop, Kofi who freelances, and me at Vektor Systems, all with day jobs - is launching ShipItCon Tampere, a one-day community conference, eight months out. Scope is settled: single track, 200 seats, Good/Better/Best budget planned. I drafted our risk list for review:\n1. Nobody shows up because nobody's heard of us (our number one worry - we're brand new)\n2. It rains on event day\n3. The venue wifi is slow\n4. A bigger conference announces for the same week\n5. Catering arrives late\nNo owners assigned yet - we'll figure out who handles things if they actually happen. Can you review and improve this?",
"expected_output": "A restructured pre-mortem using Tigers / Paper Tigers / Elephants: the 'nobody comes' worry demoted to paper tiger, the missing real tigers and the team-bandwidth elephant added, owners from existing delegation roles and decision dates assigned in advance, and launch-blocking risks wired to budget-tier downgrades rather than cancellation.",
"files": [],
"expectations": [
"The review applies the Tigers / Paper Tigers / Elephants categorization by name.",
"'Nobody shows up because we're unknown' is reclassified as a paper tiger, not treated as the top risk.",
"The paper-tiger verdict is justified by the existing-community attendance baseline: a first edition draws its floor of attendees from the community it grew out of.",
"At least two real tigers absent from the draft are added, from: the venue contract falling through, an anchor sponsor's payment landing after the deposits it covers, a lead speaker cancelling with no backup, day-of volunteer no-shows.",
"The elephant is surfaced: whether three organizers with day jobs actually have the weekly hours to hit the timeline - headcount on paper, untested in hours.",
"The prescribed technique for the elephant appears: each organizer states a weekly hour commitment out loud.",
"The draft is critiqued structurally: a pre-mortem where every risk is external and none is about the team itself has skipped its most valuable category.",
"Every launch-blocking risk is assigned a named owner and a decision date.",
"The user's plan to 'figure out who handles things if they happen' is rejected: owners and decision dates are set in advance, not improvised at failure time.",
"Owners are drawn from the delegation roles already stood up (for example the logistics owner takes the venue risk, the sponsorship owner the payment-timing risk); no separate risk-owner role is invented.",
"Risks are placed on an urgency ladder distinguishing launch-blocking, fast-follow (solvable within about 30 days after the event), and track-only.",
"A launch-blocking tiger firing triggers a budget-tier downgrade (Best to Better to Good), not cancellation.",
"Fast-follow risks are explicitly handed to the post-event debrief and edition 2, never solved by delaying edition 1.",
"The pre-mortem is scheduled for a revisit at the one-month-out checkpoint the timeline already carries."
]
},
{
"id": 7,
"prompt": "Great news for RenderWave, our first-edition WebGPU conference in Brisbane: the waitlist just crossed 1,400 signups and our announcement post got 3,000 reactions, so today we're signing the premium catering contract and booking the harbour-cruise afterparty - the full Best version of our budget. One worry though: we opened early-bird sales last week and only 60 tickets have sold, which feels slow. Should we be thinking about cancelling before we're in too deep? For what it's worth, sponsorship is going fine - about 70% of our target sponsor revenue has already been received.",
"expected_output": "The Best-tier signing is blocked because waitlist and reactions are stated interest, not registrations; tier movement is keyed to written downgrade dates and sponsorship revenue received; the slow early-bird signal downgrades the tier instead of cancelling, given the sponsorship-heavy funding model.",
"files": [],
"expectations": [
"Signing the Best-tier commitments today on the strength of the waitlist and reactions is refused.",
"An evidence ladder is applied, ranking opinion below stated interest below deposits or claimed tickets below actually showing up, with the waitlist signups and post reactions placed at stated interest.",
"Real claimed registrations are named as the required evidence before committing spend beyond the Good tier.",
"Committing Best-tier budget on stated-interest evidence is called out as premature scaling with a contract attached (or equivalent framing).",
"Budget-tier movement is keyed to written downgrade dates triggered by sponsorship revenue actually received by each date, not to waitlist size.",
"Cancellation is rejected: a soft early-bird signal downgrades the tier (Best to Better to Good) instead of cancelling the event.",
"The sponsorship-heavy funding model is used in the reasoning: with the bulk of budget targeted from sponsorship (around 80%+), viability is decoupled from ticket-sale velocity.",
"The 60 sold tickets are recognized as the strongest evidence class present - real claimed tickets - stronger than the 1,400-name waitlist.",
"Ticket-sale pace checkpoints are treated as a trend to watch, not a go/no-go gate for the launch itself.",
"The premium catering and afterparty are identified as Best-tier headroom items - the first things a downgrade removes - rather than baseline commitments."
]
},
{
"id": 8,
"prompt": "I lead developer relations at Faborate, an API-security vendor. Leadership approved our first developer conference, Faborate DevCon, with a real budget line and two full-time staff on it: me and our events manager. Two questions before Thursday's exec review. First, a community-conference guide I read says you need three organizers from three different companies before you can lock anything in - do we need to go recruit outside organizers? Second, here's the situation with my launch brief: the agenda section lists nine talk titles with speaker names and time slots, but only two speakers are actually confirmed; the other seven are aspirational. Can you polish the formatting so the whole thing looks finished and confident for the execs?",
"expected_output": "Company-run adjustments applied explicitly: the three-organizations gate relaxed by design (no outside recruiting needed), budget named as the binding constraint, the neutrality channel unavailable with the customer base substituting; the polish request refused, with unconfirmed speakers visibly marked not-yet-decided inside the agenda section, and a why/how/what brief delivered section by section.",
"files": [],
"expectations": [
"The event is identified as company-run, and recommendations state which ownership pole they assume where community-run and company-run advice differ.",
"The three-organizations team gate is relaxed for a company-run event by design - the company is the owner - and this relaxation is stated explicitly rather than the gate being silently waived or wrongly enforced.",
"The user is not told to recruit outside co-organizers to satisfy the community-run gate.",
"Budget is identified as the binding constraint for a company-run event, replacing volunteer bandwidth.",
"The cross-organization neutrality credibility channel is flagged as unavailable to a company-run event, with the existing customer or user base substituting as the audience baseline.",
"The request to polish the aspirational agenda into a finished-looking brief is refused as asked: the seven unconfirmed speakers must not be presented as booked.",
"Unconfirmed items are marked visibly as not yet decided inside the agenda section itself, not relegated to a separate risk list or footnote.",
"The reasoning appears: polished formatting makes a guess read as settled - a plausible placeholder gets read as decided the moment the formatting looks finished, where a stated 'not yet decided' reads honestly.",
"The launch brief is structured as why the event exists (mission and convictions), how it differs from what exists (signature choices), and what a day of it concretely looks like.",
"A success measure for the edition is fixed before the event (for example a post-event survey scored against a rubric agreed in advance), not defined after it runs."
]
}
],
"trigger_queries": [
{ "query": "We're starting a Kubernetes conference in Denver next year, the first one ever. Where do we begin?", "should_trigger": true },
{ "query": "How do I plan the first edition of a developer conference from scratch?", "should_trigger": true },
{ "query": "Three of us run a 300-person meetup and want to turn it into a one-day conference. Build us a launch plan.", "should_trigger": true },
{ "query": "Our company wants to run its first user conference in 9 months - help us scope it so we don't overreach.", "should_trigger": true },
{ "query": "We decided to launch a hackathon in our city, nothing like it exists here. What's the path from today to event day?", "should_trigger": true },
{ "query": "What's the minimum viable version of a tech conference? We don't want to overbuild edition one.", "should_trigger": true },
{ "query": "I want to start an annual AI summit. How big should year one be?", "should_trigger": true },
{ "query": "How many co-organizers do I need before green-lighting a brand-new community conference?", "should_trigger": true },
{ "query": "We're launching a brand-new event and I keep adding tracks and ideas. How do I keep the launch scope under control?", "should_trigger": true },
{ "query": "First-time conference organizers here - what has to be in place before we announce anything publicly?", "should_trigger": true },
{ "query": "Help me build a reverse timeline from our conference date back to today. It's our first edition.", "should_trigger": true },
{ "query": "Never organized an event before, but we're committed to turning our Rust meetup into a conference next fall. What do we do first?", "should_trigger": true },
{ "query": "My cofounder and I want to put on a 200-person tech event that has never existed. What risks are specific to a first-time event?", "should_trigger": true },
{ "query": "We have a date we can't move and less runway than a normal conference takes. How do we compress the launch?", "should_trigger": true },
{ "query": "How should we set go/no-go checkpoints for a conference nobody has heard of yet?", "should_trigger": true },
{ "query": "Starting a new developer festival - should edition one be multi-track, or should we keep it to one day?", "should_trigger": true },
{ "query": "We got budget to launch our first public developer day. Help us form the founding organizer team.", "should_trigger": true },
{ "query": "What team do we need to launch a hackathon for the first time?", "should_trigger": true },
{ "query": "Planning our inaugural data-engineering conference. What's the smallest edition worth running?", "should_trigger": true },
{ "query": "We've validated demand with a waitlist. Now how do we actually launch edition one?", "should_trigger": true },
{ "query": "I'm turning our community's demand into an actual first event. Walk me through decision to doors open.", "should_trigger": true },
{ "query": "What should the founding organizer team look like for a brand-new tech conference?", "should_trigger": true },
{ "query": "We want a one-day single-track conference next spring, first time organizing anything. Is 6 months enough runway?", "should_trigger": true },
{ "query": "How do I run a pre-mortem for an event that has no track record yet?", "should_trigger": true },
{ "query": "Nobody knows our event exists yet - which launch risks should we actually worry about?", "should_trigger": true },
{ "query": "Our meetup group is ambitious: first conference in 10 months, day jobs intact. Scope it for us.", "should_trigger": true },
{ "query": "we finally decided to do the thing - a proper conference, first one ever. where do we even start lol", "should_trigger": true },
{ "query": "Two friends and I said yes to organizing our city's first serverless conf. Give us the launch checklist.", "should_trigger": true },
{ "query": "How much of our big event vision should we cut for year one?", "should_trigger": true },
{ "query": "What has to be true before we book a venue for our brand-new conference?", "should_trigger": true },
{ "query": "Setting the budget appetite for a first-time community event - how do we decide what it's worth spending?", "should_trigger": true },
{ "query": "Our first hackathon is in 5 months. Reverse-plan it for me.", "should_trigger": true },
{ "query": "We're announcing our new conference soon. What admin groundwork must exist before the announcement?", "should_trigger": true },
{ "query": "As a vendor we want to launch a developer conference alongside our existing sales conference - first edition. How do we scope it?", "should_trigger": true },
{ "query": "The organizing committee keeps re-debating what's in and out of scope for our new event. How do we stop that?", "should_trigger": true },
{ "query": "I have zero events under my belt and 12 months. Take me from decision to doors open.", "should_trigger": true },
{ "query": "What's a realistic launch runway for a first-time community conference versus a first-time hackathon?", "should_trigger": true },
{ "query": "Our first edition planning feels like we're building the tenth edition. Help us right-size it.", "should_trigger": true },
{ "query": "How do I know if there's enough demand for a new DevOps conference in my city?", "should_trigger": false },
{ "query": "Our conference is in its fourth year - how do we grow attendance to 1,000?", "should_trigger": false },
{ "query": "Build a sponsorship prospectus for our conference.", "should_trigger": false },
{ "query": "What should we charge for tickets to our developer conference?", "should_trigger": false },
{ "query": "Help me write our event's code of conduct.", "should_trigger": false },
{ "query": "Design the CFP form and review process for our conference.", "should_trigger": false },
{ "query": "Find and shortlist venues for a 500-person conference.", "should_trigger": false },
{ "query": "Put together the run-of-show for our conference day.", "should_trigger": false },
{ "query": "Should we run a multi-city roadshow or a single user conference this year?", "should_trigger": false },
{ "query": "Why should our company even run a user conference? Help us define the goals and who owns the budget line.", "should_trigger": false },
{ "query": "Plan the retrospective for the conference we just ran last weekend.", "should_trigger": false },
{ "query": "Build the full risk register and insurance plan for our annual conference.", "should_trigger": false },
{ "query": "Draft the month-by-month planning timeline for edition five of our conference.", "should_trigger": false },
{ "query": "Which format fits us best: unconference, workshop day, or a classic talks conference?", "should_trigger": false },
{ "query": "Design the judging rubric for our hackathon.", "should_trigger": false },
{ "query": "How should teams form at our hackathon?", "should_trigger": false },
{ "query": "Write the hackathon challenge brief for our sponsor.", "should_trigger": false },
{ "query": "Build a full profit-and-loss budget for our conference.", "should_trigger": false },
{ "query": "How do I recruit and manage volunteers for event day?", "should_trigger": false },
{ "query": "Plan our conference's social media calendar for the next quarter.", "should_trigger": false },
{ "query": "Write cold outreach emails to potential speakers for our event.", "should_trigger": false },
{ "query": "How do we pick which talk submissions to accept?", "should_trigger": false },
{ "query": "Help me pick a date that avoids conflicts for next year's conference.", "should_trigger": false },
{ "query": "How should we restructure the organizing team for our established conference series?", "should_trigger": false },
{ "query": "We're launching the first edition of our company newsletter - help me plan it.", "should_trigger": false },
{ "query": "Plan the launch of the first version of our developer tool.", "should_trigger": false },
{ "query": "How do I publish the first edition of my technical book?", "should_trigger": false },
{ "query": "What marketing plan should promote our conference this year?", "should_trigger": false },
{ "query": "How do we position our conference against the two other events in our region?", "should_trigger": false },
{ "query": "Set up a partnership where two conferences promote each other's tickets.", "should_trigger": false },
{ "query": "Design the attendee onboarding email sequence for our event.", "should_trigger": false },
{ "query": "Our meetup attendance is stagnating - how do we build a stronger community around it?", "should_trigger": false },
{ "query": "How much should we offer in cash prizes at our hackathon?", "should_trigger": false },
{ "query": "I want to start a career as a developer-event organizer - what roles exist and how do I break in?", "should_trigger": false },
{ "query": "We need to hire an event manager for our conference team - write the job description.", "should_trigger": false },
{ "query": "Plan the sponsor booth layout and staffing for our expo hall.", "should_trigger": false },
{ "query": "Draft my onboarding plan for my first 90 days as a new DevRel manager.", "should_trigger": false },
{ "query": "How do we throw a launch party for our startup's Series A announcement?", "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 |