Customer Journey Map
phuryn/pm-skills
Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities.
Use as the final stage of the Butterbase journey when hackathonmode is true and journey-deploy has passed.
MITAuto-check passed
Install Journey Submit
$ npx skills add butterbase-ai/butterbase-skills --skill journey-submit -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install butterbase-ai/butterbase-skills journey-submit --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/butterbase-ai/butterbase-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/journey-submit .claude/skills/journey-submit && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "journey-submit" agent skill from https://github.com/butterbase-ai/butterbase-skills/tree/main/skills/journey-submit into .claude/skills/journey-submit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "journey-submit", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/butterbase-ai/butterbase-skills/tree/main/skills/journey-submitType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add butterbase-ai/butterbase-skills --skill journey-submit -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install butterbase-ai/butterbase-skills journey-submit --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/butterbase-ai/butterbase-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/journey-submit .agents/skills/journey-submit && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "journey-submit" agent skill from https://github.com/butterbase-ai/butterbase-skills/tree/main/skills/journey-submit into .agents/skills/journey-submit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "journey-submit", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add butterbase-ai/butterbase-skills --skill journey-submit -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install butterbase-ai/butterbase-skills journey-submit --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/butterbase-ai/butterbase-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/journey-submit .cursor/skills/journey-submit && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "journey-submit" agent skill from https://github.com/butterbase-ai/butterbase-skills/tree/main/skills/journey-submit into .cursor/skills/journey-submit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "journey-submit", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/butterbase-ai/butterbase-skills.git --path skills/journey-submit--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add butterbase-ai/butterbase-skills --skill journey-submit -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install butterbase-ai/butterbase-skills journey-submit --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/butterbase-ai/butterbase-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/journey-submit .gemini/skills/journey-submit && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "journey-submit" agent skill from https://github.com/butterbase-ai/butterbase-skills/tree/main/skills/journey-submit into .gemini/skills/journey-submit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "journey-submit", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install butterbase-ai/butterbase-skills journey-submitInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add butterbase-ai/butterbase-skills --skill journey-submit -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/butterbase-ai/butterbase-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/journey-submit .github/skills/journey-submit && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "journey-submit" agent skill from https://github.com/butterbase-ai/butterbase-skills/tree/main/skills/journey-submit into .github/skills/journey-submit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "journey-submit", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add butterbase-ai/butterbase-skills --skill journey-submit -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install butterbase-ai/butterbase-skills journey-submit --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/butterbase-ai/butterbase-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/journey-submit .opencode/skills/journey-submit && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "journey-submit" agent skill from https://github.com/butterbase-ai/butterbase-skills/tree/main/skills/journey-submit into .opencode/skills/journey-submit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "journey-submit", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
journey-submit- GitHub stars
- 534
- Token cost
- ~1.7k tokens
- SKILL.md length
- 644 words
- Files
- 1
- Skills in repo
- 39
- Repo updated
- First seen
- Licence
- MIT
At a glance
Use as the final stage of the Butterbase journey when hackathonmode is true and journey-deploy has passed.
- Works in 4 steps: Prep (resolve which hackathon) → Walk the returned field_schema with the… → Submit → …
- SKILL.md covers When to use, Preflight, Inputs and Procedure, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Journey Submit is an agent skill from butterbase-ai/butterbase-skills. Use as the final stage of the Butterbase journey when hackathonmode 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 fieldschema with the user one at a time, then calls prepandsubmithackathonentry. Writes the receipt to docs/butterbase/05-submission.md.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Plugin for Butterbase.ai. The licence is MIT.
Example prompts
- “/journey-submit”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit aa8ae69. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are jsonc and markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Journey Submit loads about 1.7k tokens when it runs. Until then it costs about 98 tokens; SKILL.md has 644 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from butterbase-ai/butterbase-skills at commit aa8ae69, republished under its MIT licence (© butterbase-ai). 644 words, ~1,695 tokens.
Download SKILL.mdSave it as
.claude/skills/journey-submit/SKILL.md (or your agent's skills folder).- name
- journey-submit
- description
- 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.
Journey: Hackathon submission
Stage 5 (final) of the guided journey. Resolve the active hackathon, confirm fields, submit.
When to use
- Dispatched by
journeywhencurrent_stage: submitandhackathon_mode: true. - Directly via
/butterbase-skills:submit. - No-op (returns with
"submit is disabled outside hackathon mode") ifhackathon_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 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>"
}
}The response shape is:
{
"matched": null | { "slug", "name", "submission_deadline", "ends_at", "field_schema": { "fields": [...] } },
"match_reason": null | "submission_code" | "already_bound" | "single_open",
"open_hackathons": [{ "slug", "name", "starts_at", "ends_at", "submission_deadline" }, ...],
"next_call": { ... } // present only when matched is non-null
}Branch on the result:
matched | open_hackathons.length | Action |
|---|---|---|
| non-null | any | Resolved — continue to Step 2 with matched.field_schema. Mention match_reason to the user ("Resolved via your submission code", "You're already a participant in X", "Only one hackathon is open: X"). |
| null | 0 | No hackathon is currently open for submissions. Tell the user, stop, and do not tick submit. |
| null | 1 | One hackathon is open but the user isn't bound and didn't supply a code. Ask: "The only open hackathon is '<name>' (deadline <submission_deadline>). Submit to this one? If so, paste the submission_code the organizer gave you." Re-run prep with the code. |
| null | ≥ 2 | Multiple open hackathons — ask the user which one. Present the list (name, slug, deadline) and ask: "Which hackathon are you submitting to? Paste its submission_code." Re-run prep with the code. Never guess. |
Anti-pattern: do not re-run prep in a loop hoping it resolves — it won't until the user provides a
submission_code. One question, then re-prep.
Step 2 — Walk the returned field_schema with the user
matched.field_schema.fields is the authoritative list of fields for this hackathon. Walk every field in order. For each:
- Show the user the field's
label(notkey) anddescription. - Propose a value drawn from journey artifacts where obvious:
- URL-typed fields (
is_url: trueortype: "url") for the deployed app →deployed_urlfrom00-state.md. - Project name / title field → top candidate from
01-idea.md. - Description / summary field → one-liner from
01-idea.md+ must-haves. - Repo URL → ask, no default.
- Team info → ask, no default.
- Demo video → ask, allow skip if
required: false. - Anything else → ask.
- URL-typed fields (
- Confirm one at a time. Do not batch. Required fields must have a non-empty value before moving on.
- For
options-typed fields, present the allowed choices verbatim.
Use next_call.arguments.data from the prep response as the literal template — it has one key per field with a placeholder string. Replace each placeholder with the confirmed value.
Show full SKILL.md (187 more words)Show less
Step 3 — Submit
Show the assembled data object back to the user verbatim and ask: "Submit now? (yes/no)". On yes:
{
"tool": "prep_and_submit_hackathon_entry",
"arguments": {
"action": "submit",
"hackathon_slug": "<matched.slug from prep — REQUIRED when multiple are open>",
"app_id": "<app_id from 00-state.md — strongly recommended, unlocks +50 scoring points>",
"submission_code": "<same code passed to prep, if any — required on first submission>",
"data": { /* user-confirmed values keyed by field.key */ }
}
}Always pass
hackathon_slug = matched.slugfrom prep. Without it, submit re-resolves and may target a different hackathon if more than one is open. Always passapp_id— scoring awards up to 50 points for Butterbase usage on that specific app.
Step 4 — Receipt
Capture the response (submission.id, submission.version, submission.updated_at, participant_created) and write docs/butterbase/05-submission.md:
# Submission
- submitted_at: <submission.updated_at>
- submission_id: <submission.id>
- version: <submission.version>
- hackathon_slug: <submission.hackathon_slug>
- hackathon_name: <matched.name>
- app_id: <submission.app_id>
- participant_created: <true|false>
## Fields submitted
<one bullet per field: label → value>Tick - [x] submit in 00-state.md, set current_stage: done. Print a one-line success to the user including the hackathon name and submission id.
Outputs
- Hackathon submission via
prep_and_submit_hackathon_entry(action: "prep"then"submit"). docs/butterbase/05-submission.md.
Anti-patterns
- ❌ Skipping
action: "prep"and callingsubmitdirectly with a hardcoded field list. - ❌ Assuming there is exactly one open hackathon. Always check
open_hackathonson the prep response. - ❌ Picking a hackathon for the user when prep returns multiple — always ask.
- ❌ Inventing field keys or labels — only use what's in
matched.field_schema.fields. - ❌ Submitting without
hackathon_slugfrom prep (can re-resolve to the wrong hackathon). - ❌ Submitting without
app_idwhen one exists (forfeits up to 50 scoring points). - ❌ Calling submit without explicit
yesfrom the user on the assembled payload.
© butterbase-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/journey-submit of butterbase-ai/butterbase-skills.
Open the folder on GitHubat commit aa8ae69
Compare with similar skills
Journey Submit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Journey Submit this skillbutterbase-ai/butterbase-skills | 534 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Customer Journey Mapphuryn/pm-skills | 27k | — | ~816 | Automated safety check: Pass | MIT | |
| Submitbrycewang-stanford/Auto-Empirical-Research-Skills | 4.6k | — | ~1k | Automated safety check: Notes | Custom licence | |
| Submitbrycewang-stanford/Auto-Empirical-Research-Skills | 4.6k | — | ~591 | Automated safety check: Notes | Custom licence | |
| Customer Journey Map Builderdeanpeters/Product-Manager-Skills | 7.2k | 1 repos | ~3.7k | Automated safety check: Pass | Custom licence | |
| Classroom Stage Design MethodTHU-MAIC/OpenMAIC | 40k | — | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Submit
brycewang-stanford/Auto-Empirical-Research-Skills
Final submission verification gate for the sewage-house-prices paper.
Submit
brycewang-stanford/Auto-Empirical-Research-Skills
Submission pipeline — journal targeting, replication package, audit, and final gate.
Customer Journey Map Builder
deanpeters/Product-Manager-Skills
Builds a stage-by-stage customer journey map covering actions, touchpoints, emotions, KPIs, goals, and owning teams for one persona and scenario.
Classroom Stage Design Method
THU-MAIC/OpenMAIC
Baseline procedure for building one new classroom stage: settle the page plan with you, create the stage, write the roster, then generate each page in order.
Stage Tamagotchi Godot Csharp
moeru-ai/airi
Apply the Stage Tamagotchi Godot C development method and code style when working in apps/stage-tamagotchi-kirie or its migration predecessor, engines/stage-tamagotchi-godot.
More from butterbase-ai/butterbase-skills
All 39 skills in this repoAI
butterbase-ai/butterbase-skills
A skill your agent uses when calling the app's AI gateway from agent tools — chat completions, embeddings, listing models, configuring defaults or BYOK, reading token/cost usage
Auth Setup
butterbase-ai/butterbase-skills
A skill your agent uses when configuring OAuth providers (Google/GitHub/Apple/X/etc.), setting up post-login auth hooks, tuning JWT lifetimes, or generating service API keys
Build App
butterbase-ai/butterbase-skills
A skill your agent uses when building a new Butterbase app from scratch, creating a full-stack application, or when the user asks to set up a complete backend with database, auth, and deployment
Contributing
butterbase-ai/butterbase-skills
A skill your agent uses when contributing to the Butterbase codebase, adding new MCP tools, creating API routes, writing migrations, or understanding the monorepo architecture
Debug Rls
butterbase-ai/butterbase-skills
A skill your agent uses when users report access denied errors, see wrong data, RLS policies are not working, or when troubleshooting Row-Level Security issues in Butterbase
Deploy Frontend
butterbase-ai/butterbase-skills
A skill your agent uses when deploying a frontend (React, Next.js, or static HTML) to a live URL on Butterbase, or when troubleshooting deployment issues like MIME type errors or blank pages
Questions about Journey Submit
What does Journey Submit do?
Use as the final stage of the Butterbase journey when hackathonmode is true and journey-deploy has passed. Journey Submit is an agent skill from butterbase-ai/butterbase-skills. Use as the final stage of the Butterbase journey when hackathonmode is true and journey-deploy has passed.
How do I install Journey Submit in Claude Code?
Run `npx skills add butterbase-ai/butterbase-skills --skill journey-submit -a claude-code`. Or copy the skill folder (skills/journey-submit in butterbase-ai/butterbase-skills) into .claude/skills/journey-submit in your project. Claude Code loads it when a task matches its description.
How do I install Journey Submit in Codex?
Run `npx skills add butterbase-ai/butterbase-skills --skill journey-submit -a codex`. Or copy the skill folder (skills/journey-submit in butterbase-ai/butterbase-skills) into .agents/skills/journey-submit in your project. Codex loads it when a task matches its description.
Can I use Journey Submit in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add butterbase-ai/butterbase-skills --skill journey-submit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/journey-submit, .gemini/skills/journey-submit, .github/skills/journey-submit and .opencode/skills/journey-submit in your project.
What does Journey Submit need to run?
SKILL.md names no scripts, command-line tools or credentials: Journey Submit is instructions for the agent only.
Does Journey Submit access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Journey Submit safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Journey Submit use?
Journey Submit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Journey Submit use?
About 1.7k tokens (SKILL.md is roughly 6.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Journey Submit?
Skills that share tags, products or a category with Journey Submit: Customer Journey Map (phuryn/pm-skills, 27k stars), Submit (brycewang-stanford/Auto-Empirical-Research-Skills, 4.6k stars), Submit (brycewang-stanford/Auto-Empirical-Research-Skills, 4.6k stars) and Customer Journey Map Builder (deanpeters/Product-Manager-Skills, 7.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Journey Submit?
butterbase-ai (a GitHub organization) maintains it in butterbase-ai/butterbase-skills, which has 534 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on October 5, 2026.
Source: butterbase-ai/butterbase-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.