hackathon-team-formation SKILL.md skillA
hackathon-team-formation 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/hackathon-team-formation@v1.0.1Pins v1.0.1 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/hackathon-team-formation/SKILL.md- Versions recorded
- 2
- Latest version
- v1.0.1, committed Sep 1, 2026
- First version recorded
- Sep 1, 2026
- Size
- 35,738 bytes
- Repository stars
- 4
- License
- MIT
Decide how participants at a hackathon end up on teams - the published team-size rule including whether solo entry is allowed, the matchmaking mechanic that runs on the day, what happens to someone still unteamed after it, when membership freezes relative to the opening, and any track-conditioned team-composition rule. Use whenever the user mentions hackathon team size, a pitch-and-join or team-matching session, whether solo hackers are permitted, a participant nobody picked, or teams changing…
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
# Hackathon Team Formation You decide how people at a hackathon end up building with each other: the team-size rule the brief publishes, the mechanic that runs on the day, what happens to whoever it fails, when membership stops moving, and how all four fit around the opening. This is the participant-to-participant problem. It is not the participant-to-expert problem, and the two get confused constantly. ## What you own, and what is already decided You own: - the team-size number and its solo answer - the matchmaking mechanic - the unteamed-participant protocol - the mid-event change policy - any track-conditioned composition rule Four things arrive from, or leave for, siblings - hand them over rather than re-deciding them: - **The published rules text** belongs to `samber/dev-event-organizer-skills@hackathon-brief-design`. Its interview asks this skill for the team-size rule by name, and its pre-publication threshold counts that rule as one of seven items that must exist. You decide the number and the wording intent; that skill prints it. …
Read the whole file at its exact version.
How to install
mdr add samber/dev-event-organizer-skills/hackathon-team-formation@sha256:0b074a9ab472201eThe line at the top of this page pins the label v1.0.1, 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_axr3ivzj77c46rzf)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Sep 1, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.1 latest | 2026-09-01 | 48f37c3 | 35,738 B | A | view · diff |
| v1.0.1 | 2026-09-01 | 17f07df | 35,732 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 (35738 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_axr3ivzj77c46rzf GET https://markdownregistry.com/api/v1/resolve?ref=samber/dev-event-organizer-skills/hackathon-team-formation GET https://markdownregistry.com/api/v1/blob/0b074a9ab472201e5e10d1d7782962b9fb80c45784a30faaee940474b778c6b2
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.