Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →butterbase-ai/journey-templates
Use as the optional template-publishing stage of the Butterbase journey, after deploy (and substrate, if used). Walks the user through authoring a clone-ready README, bundling agent spec files, dry-running and pushing the repo snapshot, flipping visibility to public + listed, and self-clone-testing. Delegates the mechanics to the `templates` skill. Skipped by default in hackathon mode.
Passed 15 of 20 test cases with the skill, and 4 of 20 without it.
and 12 more in the full report
13 fixed4 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
What standard commit message parameter is passed when executing the final snapshot upload via the Butterbase CLI?
| Checked | Without skill | With skill |
|---|---|---|
| Uses butterbase repo push -m "publish v1" | Missed | Passed |
The instructions your model reads when the skill loads.
Turn the deployed app into a public, forkable template. This stage is only for apps the user explicitly wants to share — most journeys end at deploy (or submit in hackathon mode).
journey when current_stage: templates./butterbase-skills:journey-templates.journey-deploy).docs/butterbase/02-plan.md — to know what features the app uses (agents, MCP servers, OAuth providers, function env vars).docs/butterbase/04-build-log.md — to confirm deploy smoke passed.00-state.md must have current_stage: templates or later AND deploy ticked.@butterbase/cli must be installed locally (butterbase --version works). If not, invoke journey-preflight to fix..butterbase/config.json exists with the right currentApp. If not, run butterbase repo init <app_id>.Refresh docs. Call butterbase_docs with topic: "templates" (and topic: "repo" if the cache doesn't already cover snapshot push). Skip if 03b-docs-cache.md is fresh.
Confirm intent. Ask:
"Publish '<app_name>' as a public template? Public + listed makes it appear in the gallery; public + unlisted is forkable by anyone with the app_id but hidden from search. Or skip. (listed / unlisted / skip)"
Default: skip (especially in hackathon mode unless the user explicitly chose to publish their submission).
On skip: mark the row - [x] templates (skipped — not publishing) in 00-state.md. Write docs/butterbase/06-template.md with one line: Skipped on <date>. Return to orchestrator.
On listed / unlisted: delegate to butterbase-skills:templates. The wrapped skill walks the user through:
a. Author / review README.md. This is the most important step — clone replay does not carry OAuth secrets, agent records, MCP server registrations, function secrets, or user data. The README must explain every manual step a cloner will need. The templates skill has the full checklist; do not let it write a short README and move on.
b. Bundle agent specs. If the app has agents, ensure agents/<name>.json exist (export with butterbase agents get <name> if missing) and are tracked.
c. Inspect drift. butterbase repo status. Walk the modified / untracked / deleted lists with the user. This is the chance to catch a stray secret file or an unwanted directory before it ends up in the snapshot.
d. Dry-run. butterbase repo push --dry-run. Confirm the final upload manifest matches what repo status showed.
e. Push. butterbase repo push -m "publish v1". Capture the snapshot id.
f. Flip visibility. butterbase visibility public --listed (or --unlisted).
test cases passed, vs 4 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.