Samuel BertheCreator of Go library lo, 21k+ GitHub stars324 installs on skills.shEvent Team Structure
Design the standing organizing team of a recurring technical event - the structure.
3 static scans, 0 counted findings.
Edge checks it again each time your agent loads it.
From the samber public repository. Edge did not write or edit this skill.
What it does
- 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, and the volunteer-to-paid-staff hiring gate.
- Use whenever the user mentions structuring or governing an organizing team, forming an association or non-profit for an event, splitting decision rights, organizer succession or rotation, organizer burnout, or hiring the first paid staff - even if they never say "team structure".
- Do NOT use for day-of staffing - use samber/dev-event-organizer-skills@event-volunteers instead.
Why Samuel Berthe
Go open source author. Each fact links its public source.
- Created samber/lo, 21k+ stars
His Lodash-style Go generics library lo has 21k+ GitHub stars.
GitHub - Packaged in Ubuntu
lo ships as an Ubuntu source package, golang-github-samber-lo.
Ubuntu packages - 3k+ stars on his Go skills
His Golang agent skills collection has 3k+ GitHub stars.
GitHub
Public sources, checked Oct 26, 2026.
How it works
- 1Copy
Try for free gives you one prompt.
- 2Paste
Paste it into Claude Code, Codex or Cursor.
- 3Ask
Ask for the outcome. Your agent loads Event Team Structure.
3 static scans, 0 counted findings.
Security state at 2026-09-30: reviewed. Static scans check the code, not how well the skill works.
State definitionsSkill details
Security scansReviewed
3 static scans, 0 counted findings. Security state at 2026-09-30: reviewed. Edge checks it again each time your agent loads it.
Edge static checks (Edge-run): edge-static/1.0.1. Scope: Static patterns for remote execution, credentials with network sends, obfuscation, prompt overrides, hidden Unicode, binaries and persistence. Raw findings: .
Cisco skill-scanner (Edge-run): cisco-skill-scanner/2.1.0. Scope: Local static, YARA, pipeline and behavioral analyzers; no LLM or AI Defense analysis. Raw findings: .
Semgrep Edge rules (Edge-run): semgrep/1.178.0+edge-rules.c15016a36fd3+offline-v1. Scope: Six Edge-authored static rules with Semgrep CE; offline execution and metrics disabled. Semgrep-maintained rules excluded. Raw findings: .
- Edge static checks
- Pass · 0 counted findings · 2026-09-27
- Cisco skill-scanner
- Pass · 0 counted findings · 2026-09-27
- Semgrep Edge rules
- Pass · 0 counted findings · 2026-09-27
Creator, source & licencesamber
From the samber public repository. Edge did not write or edit this skill.
- Repository
- samber/dev-event-organizer-skills
- Skill file
- View source at revision
- Revision
- 6fe636747398f8f3beb60dbe86f03a87d16f016a
- Package hash
- sha256:b383520f69546c3aea1c4ff94c9f09975d2329b56907acb81596b9ba54ebe603
- Licence
- MIT
- Description
- 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, and the volunteer-to-paid-staff hiring gate. Use whenever the user mentions structuring or governing an organizing team, forming an association or non-profit for an event, splitting decision rights, organizer succession or rotation, organizer burnout, or hiring the first paid staff - even if they never say "team structure". Do NOT use for day-of staffing - use samber/dev-event-organizer-skills@event-volunteers instead.
Quoted from the skill’s own description
Read skill files4 files
4 files, 81.6 KB at revision 6fe636747398.
Questions about Event Team Structure
What does Event Team Structure do?
Design the standing organizing team of a recurring technical event - the structure. Published by Samuel Berthe (samber/dev-event-organizer-skills).
Is Event Team Structure safe to use?
Edge security state: Reviewed (3 Edge-run static scans, scanned Sep 30, 2026). The Evidence tab shows the scan.
How do I use Event Team Structure in Claude Code, Codex or Cursor?
Click Try for free, pick your agent and follow its one step. Edge is free, with no Edge account.
Similar skills

A relentless interview to sharpen a plan or design.

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX"…

tasteskill 2.5.1, the anti-slop frontend skill. Builds professional company websites at the level of figma.com and x.ai: plain copy in a voi…

Emil Kowalski's design-engineering philosophy for UI polish, component design, animation decisions, and the invisible details that make soft…

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-design…

Extract design primitives from a public website and generate starter token files for your project.
Design and implement one-click post-purchase upsells and downsells that raise average order value without hurting the main conversion rate.…

Design skill for websites and new pages that look designed, not generated. Use when the user asks to build or design something new, or names…