---
name: gm-submission
description: Turn a finished project into a Season Zero submission drop for GM Spaces — the story in four beats, the track declared, and the vote count switched on — then have the platform check it before Demo Day.
---

# Entering the Season Zero build challenge

A submission is not a form. It is a **drop**: a card pinned at the venue on
Demo Day that the room collects to vote for. This file turns a project into
one, correctly, on the first try.

You do not have to use this. The same submission can be made by tapping
through the app, and the walkthrough is at gmcarl.xyz/season0/submit. Use this
when you would rather your agent draft it.

## When to load

Load this when somebody is entering, or fixing, a Season Zero submission for
GM Spaces. It is specific to this challenge and expires with it.

Do not load it to publish. There is no public write API. You produce the
words and the settings; a person pastes them into the composer and drops it
standing at the venue.

## Inputs

Ask for these. Do not invent any of them.

- **The project's name.** The real one, not a tagline.
- **The problem** it solves, in the person's own words.
- **What they actually built.** Working, half-working, or a prototype. Say
  which.
- **Who is on the team.** Names. If solo, say solo.
- **What happens next** after Demo Day.
- **A link** to the demo: a live URL, a video, a repo, or a deck. Https only.
- **A photo** of the thing working, or a screenshot.
- **The track.** `GM Spaces` if it is built for or with the app, `Custom` if
  it is their own thing on any stack. One submission, one track.

If the person cannot answer "what happens next," write the submission without
it and tell them it is missing. Do not fill it in for them. Judges are the
room, and the room can tell.

## Steps

1. **Write the name.** Up to 200 characters. The project's name alone. No
   colon, no tagline after it.

2. **Write the one line.** Up to 500 characters, and it is the line on the
   face of the card. What it is and why anyone should stop. This is the
   composer's *small print* field.

3. **Write the story, in four beats, in this order:** the problem, what you
   built, who is on the team, what happens next. Up to 2000 characters, and
   it goes in the composer's *story* field, not the one line. Plain
   paragraphs. Name the track in the last line, exactly: `Track: GM Spaces`
   or `Track: Custom`.

4. **Name the settings** the person has to set by hand, as a short checklist
   they can follow in the composer:

   - a photo of it working
   - the link, https only
   - how they keep it: **be there** (within a block of the pin)
   - the count: **show the count** — this is what makes it a ballot
   - pinned at the venue, which happens automatically if they drop it
     standing there

5. **Check the card.** If you have drafted any gm-code, or the person wants
   the card's layout checked, post it:

   ```
   POST https://app.gmcarl.xyz/api/gmcode
   {"code": "…"}
   ```

   Clean or it is not done. The vocabulary, if you need it, is at
   `GET https://app.gmcarl.xyz/api/gmcode?as=text` — fetch it, never recite it
   from memory.

## Checks

- **The story has all four beats**, in order, and each one is answerable by a
  stranger reading it cold.
- **The track is declared in the story**, spelled `GM Spaces` or `Custom`.
- **Every fact came from the person.** No invented teammates, no invented
  metrics, no invented launch date. If a beat is thin, it stays thin.
- **The link is https** and points at something a voter can open on a phone in
  a cafe, standing up, in under a minute.
- **The checklist names "show the count."** A submission with the count off
  cannot be voted for, and nobody will notice until it is too late to fix.
- **The one line is not the story repeated.** If they say the same thing, cut
  the one line down until it is the hook.

## Done when

The person has: a name, a one line, a four-beat story ending in the track, a
photo, a link, and the five-item settings checklist. Hand all of it over in
one message they can work from with the app open, in the order the composer
asks for it.

## Install

Save as `SKILL.md` in your harness's skills directory:

```
.agents/skills/gm-submission/SKILL.md     # or .claude/skills/, per your harness
```

No key, no account. The check endpoint is public.

---

*The rules this file obeys are at gmcarl.xyz/season0/docs. If the two ever
disagree, the rules win and this file is out of date.*