agentleFS
Sign inStart free
butterbase-aibutterbase-ai/butterbase-skills/skills/journey-deploy/SKILL.md

journey-deploy

Skill535 starsChanged 5 months agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 0 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If docs/butterbase/03-preflight.md is missing, older than 24 hours, or 00-state.md has app_id: null, invoke …

    line 17
  2. Very specific:

    Refresh docs: Call butterbase_docs with topic: "frontend".

    line 27
  3. Very specific:

    Frontend reachable: If deployed_url is set, fetch it via Bash curl -sS -o /dev/null -w "%{http_code}" <url>.

    line 31
  4. Very specific:

    Auth round-trip (if configured): If the plan included OAuth, prompt the user: "Open <deployed_url>, click 'Sign in with <provider>', and …

    line 35
  5. Very specific:

    Function logs clean: Call mcp__butterbase__manage_function action: get_logs for the most recent invocations.

    line 37
  6. Very specific:

    If all checks pass, tick - [x] deploy in 00-state.md, set current_stage: submit (if hackathon_mode: true) or current_stage: done …

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Journey: Deploy verification

Stage 4 of the guided journey. Verify the deployed app actually works end-to-end.

When to use

  • Dispatched by journey when current_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 — for app_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

  1. Refresh docs. Call butterbase_docs with topic: "frontend". For end-to-end smoke patterns, also WebFetch https://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.

  1. Frontend reachable. If deployed_url is set, fetch it via Bash curl -sS -o /dev/null -w "%{http_code}" <url>. Expect 200. Log <ISO> deploy curl 200 ok or ... <code> fail.
  2. Functions respond. For each function in the plan with HTTP trigger, call mcp__butterbase__invoke_function with a representative payload. Expect 2xx. Log per function.
  3. 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.
  4. Function logs clean. Call mcp__butterbase__manage_function action: get_logs for the most recent invocations. Show the user any error-level lines. Ask: "Anything concerning here? (no → continue, yes → fix and re-run)".
  5. If all checks pass, tick - [x] deploy in 00-state.md, set current_stage: submit (if hackathon_mode: true) or current_stage: done (otherwise).
  6. Return to journey orchestrator.

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free