Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →butterbase-ai/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.
Passed 9 of 18 test cases with the skill, and 6 of 18 without it.
and 4 more in the full report
5 fixed6 passed either way10 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our `docs/butterbase/00-state.md` contains `app_id: 'app_98765'`. Should `app_id` be passed in `prep_and_submit_hackathon_entry` during action `submit`?
| Checked | Without skill | With skill |
|---|---|---|
| Passes app_id from docs/butterbase/00-state.md in the submit tool call arguments. | Missed | Passed |
| Explains that passing app_id awards bonus scoring points. | Missed | Passed |
The instructions your model reads when the skill loads.
Stage 5 (final) of the guided journey. Resolve the active hackathon, confirm fields, submit.
journey when current_stage: submit and hackathon_mode: true./butterbase-skills:submit."submit is disabled outside hackathon mode") if hackathon_mode: false.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.
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.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 the schema and it varies per hackathon.
// First, ask the user: "Do you have a submission code from the organizer? (paste it, or 'no')"
// If yes, pass it. If no, omit it.
{
"tool": "prep_and_submit_hackathon_entry",
"arguments": {
"action": "prep",
"submission_code": "<optional, from user>"
}
}
test cases passed, vs 6 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.