journey-submit
Use as the final stage of the Butterbase journey when hackathon_mode is true and journey-deploy has passed. Resolves which hackathon to submit to (asking the user when multiple are open), walks every field in the hackathon's returned field_schema with the user one at a time, then calls prep_and_submit_hackathon_entry. Writes the receipt to docs/butterbase/05-submission.md.
Profile →npx skills add butterbase-ai/butterbase-skills --skill journey-submit --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Journey: Hackathon submission Stage 5 (final) of the guided journey. Resolve the active hackathon, confirm fields, submit. ## When to use - Dispatched by `journey` when `current_stage: submit` and `hackathon_mode: true`. - Directly via `/butterbase-skills:submit`. - No-op (returns with `"submit is disabled outside hackathon mode"`) if `hackathon_mode: false`. ## Preflight If `docs/butterbase/03-preflight.md` is missing, older than 24 hours, or `00-state.md` has `app_id: null`, invoke `butterbase-skills:journey-preflight` first. Wait for it to return successfully before proceeding. Additionally: refuse to run unless `deploy` is ticked in `00-state.md`. If it is not, tell the user to run `/butterbase-skills:journey-deploy` first. ## Inputs - `docs/butterbase/01-idea.md` — title / tagline candidates. - `docs/butterbase/02-plan.md` — feature list. - `docs/butterbase/04-build-log.md` — what actually shipped. - `docs/butterbase/00-state.md` — `app_id`, `deployed_url`. ## Procedure ### Step 1 — Prep (resolve which hackathon) Always start with `action: "prep"`. Do **not** assume there is exactly one hackathon, and do **not** invent a field schema from prior context — the platform owns th
- When to use
- Preflight
- Inputs
- Procedure
- Step 1 — Prep (resolve which hackathon)
- Step 2 — Walk the returned fieldschema with the user
- Step 3 — Submit
- Step 4 — Receipt
- Outputs
- Anti-patterns
What does the journey-submit skill do?
Use as the final stage of the Butterbase journey when hackathon_mode is true and journey-deploy has passed. Resolves which hackathon to submit to (asking the user when multiple are open), walks every field in the hackathon's returned field_schema with the user one at a time, then calls prep_and_submit_hackathon_entry. Writes the receipt to docs/butterbase/05-submission.md.
How do I install it?
Run `npx skills add butterbase-ai/butterbase-skills --skill journey-submit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From butterbase-ai/butterbase-skills, a repository with 532 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.