event-team-structure SKILL.md skillA
event-team-structure from samber/dev-event-organizer-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add samber/dev-event-organizer-skills/event-team-structure@v1.1.0Pins v1.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- samber/dev-event-organizer-skills
- Path
skills/event-team-structure/SKILL.md- Versions recorded
- 3
- Latest version
- v1.1.0, committed Oct 12, 2026
- First version recorded
- Aug 31, 2026
- Size
- 33,931 bytes
- Repository stars
- 4
- License
- MIT
Design the standing organizing team of a recurring technical event - the structure that persists between editions. Covers legal-entity posture (none, fiscal sponsorship, own non-profit), decision-rights shape (board-plus-organizers split, domain-lead federation, consensus committee), the role taxonomy, succession and bus-factor planning, burnout guardrails, organizer conflict of interest, a voluntary peer network of independent local communities, and the volunteer-to-paid-staff hiring gate.…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Event Team Structure You are an organizational designer for the standing teams behind recurring technical events - conferences, meetups, hackathons. Design the structure that exists _between_ editions: who holds which authority, how new organizers come in, how leaders hand over, and when volunteer effort must become paid work. You never re-derive first-edition team formation (that belongs to `samber/dev-event-organizer-skills@event-first-edition`) and never plan the day-of volunteer workforce. One comparison carries most of the defaults below: DjangoCon US and DjangoCon Europe sit under the same parent foundation and chose opposite designs - US kept a standing legal entity, Europe rotates a fresh host team every edition - and the standing-entity design proved demonstrably more stable. The full case record is in the references. ## Community-run vs company-run Who owns the event changes the menus (the same split `samber/dev-event-organizer-skills@event-market-fit` and `samber/dev-event-organizer-skills@event-growth-strategy` use): - **Community-run** - volunteer-led, ticket/sponsor-funded: every menu below applies in full, and the practice they describe comes from this pole. …
Read the whole file at its exact version.
How to install
mdr add samber/dev-event-organizer-skills/event-team-structure@sha256:67cf0dee06da3763The line at the top of this page pins the label v1.1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_p5sph2ewezkaqe6o)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Aug 31, 2026 and Oct 12, 2026, about one every 21 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1.0 latest | 2026-10-12 | 7368d8a | 33,931 B | A | view · diff |
| v1.0.0 | 2026-08-31 | 34d2012 | 26,835 B | A | view · diff |
| v1.0.0 | 2026-08-31 | 96b6359 | 26,835 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (33931 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
samber/dev-event-organizer-skills · 4 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_p5sph2ewezkaqe6o GET https://markdownregistry.com/api/v1/resolve?ref=samber/dev-event-organizer-skills/event-team-structure GET https://markdownregistry.com/api/v1/blob/67cf0dee06da3763f17976118b8a70a6a2beaf2ef3e9ce998bcab32ec3f25c90
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.