Skip to content

samber/dev-event-organizer-skills / skills/event-portfolio-strategy

event-portfolio-strategy

Verified

Shape one organizing team's set of event properties - flagship conference, meetup series, hackathon, podcast or always-on online space - into a portfolio where each one feeds the others. Covers what each property is for, the funnel path between them, cadence collisions against one team and audience, how much brand, audience list, team and sponsors are shared, the allocation posture, add/kill criteria written before they are needed, and the dated change-the-recipe, merge or retire call when attendance falls. Use whenever asked whether to add a second event or format, how a meetup feeds a conference, how to keep momentum between editions, whether to merge overlapping meetups, or which property to retire. Do NOT use for growing one event - use samber/dev-event-organizer-skills@event-growth-strategy - or swaps with other organizers' events - use samber/dev-event-organizer-skills@cross-event-promotion.

references/portfolio-case-record.md

View on GitHub
# The portfolio record

Three real multi-property portfolios sit behind every rung in this skill. Read this before quoting any of them, because each one demonstrates less than it first appears to, and the last section is what a plan must decide for itself.

## Contents

- A student hackathon network - the learn-build-share portfolio
- A cloud-native foundation - flagship plus co-located, on a fixed rotation
- A community conference's organizing guide - the minimal two-property portfolio
- What these portfolios do not tell you

## A student hackathon network - the learn-build-share portfolio

Properties it runs directly:

- An annual hackathon season, marketed as 1000+ annual events across 100 countries, organized on a named seasonal calendar.
- A separately named global hack week initiative, distinct from the season calendar.
- A second, separately branded hackathon series - a second line of the same format rather than a rebrand of the first.
- A twelve-week paid programme positioned as an internship alternative, with three engineering tracks, built around open-source project work rather than around an event at all.
- An always-on developer community platform, **acquired February 2026**, described as five million software creators who "learn, build, and share."

The stated cross-property logic, in the organization's own framing: attend a hackathon, document the build on the platform, and that record becomes "permanent, searchable, and useful to the next person" - feeding the next cohort's learning. The longer programme sits alongside that loop as a deeper-commitment pathway.

Why it matters here: this is the strongest single instance of the skill's exact scope - one organization's several properties deliberately feeding each other - and it is the only one where the between-editions continuity mechanism is a **non-event property**. That is the evidence behind the continuity surface being the default composition rung.

Two cautions before citing it:

- The scale is organizational, not a volunteer team. Do not transfer its property count to a city team.
- Its hackathon season is itself franchise-shaped inside - independently organized local hackathons under a shared brand. That inner structure is the franchise question this skill disclaims, not the portfolio question it documents. The organization owns the second hackathon series, the programme and the platform directly; those are the portfolio part.

## A cloud-native foundation - flagship plus co-located, on a fixed rotation

- **A fixed regional rotation.** The flagship conference series runs China, North America and Europe editions on a published annual rotation (China September 2026, North America November 2026, Europe March 2027). A scheduled cadence, not opportunistic expansion - and distinct in kind from demand-pulled city-by-city franchise growth.
- **Co-located bundling as the sharing mechanism.** Each regional edition bundles several specialized conferences under one venue and timeframe; the 2026 China edition is marketed as the flagship plus an infrastructure summit plus a machine-learning framework conference. One venue booking, one attendee travel decision, several co-branded programmes sharing infrastructure and a sponsor pool.
- **A much larger surrounding portfolio.** Beyond the flagship: a regional summit series, single-topic summits across many technologies, and closed member-only events - roughly 67 named events a year, 120,000+ attendees, clustered in quarterly waves rather than spread flat, with simultaneous co-location used deliberately to concentrate networking.
- **Segmentation by audience tier.** Open community conferences and closed member-only events are distinct property types serving different audiences inside one portfolio.

Why it matters here: the two cadence rungs with published precedent - fixed rotation and co-location - both come from here, as does seasonal waves. So does the observation behind the shared-infrastructure menu, that co-located programmes share sponsors.

Caution: what this shows is that co-located programmes share a venue, a week and a sponsor _pool_. Whether one sponsorship deal is written across several properties is a **different** claim, and this is not evidence for it. See the last section.

## A community conference's organizing guide - the minimal two-property portfolio

The passage, verbatim:

> "No local meetup? No problem! Start one. Even if it's once a quarter, it starts building up an audience, and you get a sense of who is out there."

Why it matters here: this is the smallest real instance of the skill's shape - one team, two formats, different cadences, the smaller one explicitly building the audience for the larger one. It is a recommendation in a guide read by prospective organizers, not a retrospective, so it evidences the _intent_ of the meetup-to-conference funnel rather than its measured result.

Same document, different subject: this project's growth from one city in 2009 to 80+ is a **franchise** model - independent local teams, own dates, own budgets, own sponsors, sharing a brand, a code of conduct requirement, a session format and an organizer chat. That is the boundary this skill names and declines, not an example of a portfolio.

## What these portfolios do not tell you

Three things a plan must decide for itself rather than borrow from the record above, and none of them may be filled with a plausible-sounding number.

1. **Cross-property resource allocation.** How staff hours and budget split across simultaneous properties, and what starves first, is each team's own arithmetic. The workflow's allocation step therefore ships a question set, not a formula.
2. **Add and kill criteria.** The portfolios above describe what runs, never why a property was retired or what threshold triggered it. Every criterion this skill produces is the team's own, declared in advance.
3. **Cross-property sponsor packaging.** The co-location evidence above is adjacent - shared venue, week and sponsor pool - but a single deal written across several properties is a different claim, and it must not be quoted as if it were the same one.

The portfolios describe structure and intent, not how many people move from one property to another. Every measurement floor in this skill is consequently self-set.
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: 472kUpdated 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