Reproduce Chat States
different-ai/openwork
Fires known chat states in the running OpenWork desktop app, such as provider errors, retries and tool steps, so you can check how each renders.
Use as the deploy-verification stage of the Butterbase journey, after journey-frontend (or after any build stage if there is no frontend).
Install Journey Deploy
$ npx skills add butterbase-ai/butterbase-skills --skill journey-deploy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install butterbase-ai/butterbase-skills journey-deploy --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-deploy .claude/skills/journey-deploy && 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-deploy" agent skill from https://github.com/butterbase-ai/butterbase-skills/tree/main/skills/journey-deploy into .claude/skills/journey-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "journey-deploy", 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-deployType 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-deploy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install butterbase-ai/butterbase-skills journey-deploy --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-deploy .agents/skills/journey-deploy && 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-deploy" agent skill from https://github.com/butterbase-ai/butterbase-skills/tree/main/skills/journey-deploy into .agents/skills/journey-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "journey-deploy", 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-deploy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install butterbase-ai/butterbase-skills journey-deploy --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-deploy .cursor/skills/journey-deploy && 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-deploy" agent skill from https://github.com/butterbase-ai/butterbase-skills/tree/main/skills/journey-deploy into .cursor/skills/journey-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "journey-deploy", 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-deploy--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-deploy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install butterbase-ai/butterbase-skills journey-deploy --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-deploy .gemini/skills/journey-deploy && 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-deploy" agent skill from https://github.com/butterbase-ai/butterbase-skills/tree/main/skills/journey-deploy into .gemini/skills/journey-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "journey-deploy", 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-deployInstalls 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-deploy -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-deploy .github/skills/journey-deploy && 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-deploy" agent skill from https://github.com/butterbase-ai/butterbase-skills/tree/main/skills/journey-deploy into .github/skills/journey-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "journey-deploy", 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-deploy -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-deploy --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-deploy .opencode/skills/journey-deploy && 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-deploy" agent skill from https://github.com/butterbase-ai/butterbase-skills/tree/main/skills/journey-deploy into .opencode/skills/journey-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "journey-deploy", 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-deploy- GitHub stars
- 534
- Token cost
- ~666 tokens
- SKILL.md length
- 291 words
- Files
- 1
- Skills in repo
- 39
- Repo updated
- First seen
- Licence
- MIT
At a glance
Use as the deploy-verification stage of the Butterbase journey, after journey-frontend (or after any build stage if there is no frontend).
- Works in 6 steps: Frontend reachable. If deployed_url is… → Functions respond. For each function in… → Auth round-trip (if configured). If the… → …
- Tasks that involve QA and bug reports
- SKILL.md covers When to use, Preflight, Inputs and Procedure, plus 2 more sections
- Calls curl; reaches docs.butterbase.ai
What it does
Journey Deploy is an agent skill from butterbase-ai/butterbase-skills. Use as the deploy-verification stage of the Butterbase journey, after journey-frontend (or after any build stage if there is no frontend). Smoke-tests the deployed app — hits the live URL, invokes any deployed functions, checks auth round-trip. Writes results to docs/butterbase/04-build-log.md. Blocks journey-submit if smoke fails.
Its SKILL.md is about 670 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering QA and bug reports. The repository describes itself as: Plugin for Butterbase.ai. The licence is MIT.
When your agent uses it
- Tasks that involve QA and bug reports
Example prompts
- “/journey-deploy”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Frontend reachable. If deployed_url is set, fetch it via Bash curl -sS -o /dev/null -w "%{http_code}" . Expect 200. Log deploy curl 200 ok…
- Functions respond. For each function in the plan with HTTP trigger, call mcpbutterbaseinvoke_function with a representative payload…
- Auth round-trip (if configured). If the plan included OAuth, prompt the user: "Open , click 'Sign in with ', and confirm you land…
- Function logs clean. Call mcpbutterbasemanage_function action: get_logs for the most recent invocations. Show the user any error-level…
- If all checks pass, tick - [x] deploy in 00-state.md, set current_stage: submit (if hackathon_mode: true) or current_stage: done…
- Return to journey orchestrator.
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
Shell commands in SKILL.md call:
curl
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
docs.butterbase.ai
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 Deploy loads about 666 tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 291 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). 291 words, ~666 tokens.
Download SKILL.mdSave it as
.claude/skills/journey-deploy/SKILL.md (or your agent's skills folder).- name
- journey-deploy
- description
- Use as the deploy-verification stage of the Butterbase journey, after journey-frontend (or after any build stage if there is no frontend). Smoke-tests the deployed app — hits the live URL, invokes any deployed functions, checks auth round-trip. Writes results to docs/butterbase/04-build-log.md. Blocks journey-submit if smoke fails.
Journey: Deploy verification
Stage 4 of the guided journey. Verify the deployed app actually works end-to-end.
When to use
- Dispatched by
journeywhencurrent_stage: deploy. - Directly via
/butterbase-skills:journey-deploy.
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.
Inputs
docs/butterbase/00-state.md— forapp_id,deployed_url.docs/butterbase/02-plan.md— for the function list to smoke.docs/butterbase/04-build-log.md— to know what shipped.
Procedure
- Refresh docs. Call
butterbase_docswithtopic: "frontend". For end-to-end smoke patterns, also WebFetchhttps://docs.butterbase.ai/deploy. Skip if cache is fresh.
For each check, log a one-line result to 04-build-log.md. Halt on the first ✗ and ask the user to fix or skip.
Frontend reachable. If
deployed_urlis set, fetch it via Bashcurl -sS -o /dev/null -w "%{http_code}" <url>. Expect200. Log<ISO> deploy curl 200 okor... <code> fail.Functions respond. For each function in the plan with HTTP trigger, call
mcp__butterbase__invoke_functionwith a representative payload. Expect 2xx. Log per function.Auth round-trip (if configured). If the plan included OAuth, prompt the user:
"Open <deployed_url>, click 'Sign in with <provider>', and confirm you land logged-in. Did it work? (yes/no)". Log the answer.Function logs clean. Call
mcp__butterbase__manage_function action: get_logsfor the most recent invocations. Show the user any error-level lines. Ask:"Anything concerning here? (no → continue, yes → fix and re-run)".If all checks pass, tick
- [x] deployin00-state.md, setcurrent_stage: submit(ifhackathon_mode: true) orcurrent_stage: done(otherwise).Return to
journeyorchestrator.
Outputs
- Multiple lines in
04-build-log.md. - Updated
00-state.md.
Anti-patterns
- ❌ Treating a 200 from the frontend root as proof the app works — actually invoke a function.
- ❌ Skipping the auth round-trip check just because OAuth is configured server-side — judges will try to log in.
© 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-deploy of butterbase-ai/butterbase-skills.
Open the folder on GitHubat commit aa8ae69
Compare with similar skills
Journey Deploy 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 Deploy this skillbutterbase-ai/butterbase-skills | 534 | — | ~666 | Automated safety check: Pass | MIT | |
| Reproduce Chat Statesdifferent-ai/openwork | 24k | — | ~673 | Automated safety check: Pass | Custom licence | |
| Visual QA For Web And Terminal UIscode-yeongyu/oh-my-openagent | 70k | — | ~9.5k | Automated safety check: Pass | Custom licence | |
| Test And Breakrohunj/claude-build-workflow | 231 | — | ~1.6k | Automated safety check: Pass | None | |
| Verify Form Validationreticlehq/reticle | 1.2k | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Scoutqa Testgithub/awesome-copilot | 40k | 1 repos | ~3.5k | Automated safety check: Pass | MIT |
Similar skills
Visual QA For Web And Terminal UIs
code-yeongyu/oh-my-openagent
Checks a built UI against a human-interface checklist and any reference image, pairing day and night screenshots at two screen widths.
Test And Break
rohunj/claude-build-workflow
Autonomous testing skill that opens a deployed app, goes through user flows, tries to break things, and writes detailed bug reports.
Verify Form Validation
reticlehq/reticle
Check that a form actually rejects bad input: the error message renders, the submit button stays disabled, and no request goes out.
- Official
Scoutqa Test
github/awesome-copilot
This skill should be used when the user asks to "test this website", "run exploratory testing", "check for accessibility issues", "verify the login flow works", "find bugs on this page", or requests…
Kb Testing Strategy
Community-Access/accessibility-agents
Reference data, not a reviewer. An agent skill from Community-Access/accessibility-agents.
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
Related
Categories
Questions about Journey Deploy
What does Journey Deploy do?
Use as the deploy-verification stage of the Butterbase journey, after journey-frontend (or after any build stage if there is no frontend). Journey Deploy is an agent skill from butterbase-ai/butterbase-skills. Use as the deploy-verification stage of the Butterbase journey, after journey-frontend (or after any build stage if there is no frontend).
When should I use Journey Deploy?
Journey Deploy fits situations like: tasks that involve QA and bug reports.
How do I install Journey Deploy in Claude Code?
Run `npx skills add butterbase-ai/butterbase-skills --skill journey-deploy -a claude-code`. Or copy the skill folder (skills/journey-deploy in butterbase-ai/butterbase-skills) into .claude/skills/journey-deploy in your project. Claude Code loads it when a task matches its description.
How do I install Journey Deploy in Codex?
Run `npx skills add butterbase-ai/butterbase-skills --skill journey-deploy -a codex`. Or copy the skill folder (skills/journey-deploy in butterbase-ai/butterbase-skills) into .agents/skills/journey-deploy in your project. Codex loads it when a task matches its description.
Can I use Journey Deploy 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-deploy -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-deploy, .gemini/skills/journey-deploy, .github/skills/journey-deploy and .opencode/skills/journey-deploy in your project.
What does Journey Deploy need to run?
Going by SKILL.md and its folder, Journey Deploy needs the command-line tools its instructions call (curl).
Does Journey Deploy access the network?
SKILL.md names 1 domain. In commands or code: docs.butterbase.ai; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Journey Deploy 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 Deploy use?
Journey Deploy 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 Deploy use?
About 666 tokens (SKILL.md is roughly 2.7k 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 Deploy?
Skills that share tags, products or a category with Journey Deploy: Reproduce Chat States (different-ai/openwork, 24k stars), Visual QA For Web And Terminal UIs (code-yeongyu/oh-my-openagent, 70k stars), Test And Break (rohunj/claude-build-workflow, 231 stars) and Verify Form Validation (reticlehq/reticle, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Journey Deploy?
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.