Journey auth
Plugin for Butterbase.ai
npx -y skills add butterbase-ai/butterbase-skills --skill journey-authAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Use as the auth build stage of the Butterbase journey, after journey-schema (and rls if separate). Implements the Auth section of 02-plan.md by delegating to auth-setup. Calls manage_oauth (configure) for providers and optionally manage_auth_config (configure_auth_hook, update_jwt). Skipped if the plan has no end-user auth.
SKILL.md
2.3 KB, as published. Nobody here has run it
Journey: Auth
Stage 3c of the guided journey. Configure OAuth providers and (optionally) auth hooks.
When to use
- Dispatched by
journeywhencurrent_stage: auth. - Directly via
/butterbase-skills:journey-auth. - Skipped (annotated
(n/a)in00-state.md) if the plan has no end-user auth.
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/02-plan.md— the Auth section.docs/butterbase/00-state.md— forapp_id.
Procedure
-
Refresh docs. Call
butterbase_docswithtopic: "auth". For provider-specific setup (Google/GitHub/Apple), also WebFetchhttps://docs.butterbase.ai/auth. Skip if cache is fresh. -
Read the Auth section of
02-plan.md. Print it back:"About to configure auth: providers=<list>, demo_user=<yes/no>. Proceed?". Wait foryes. -
Invoke
butterbase-skills:auth-setupvia the Skill tool, passing the Auth plan andapp_id. The wrapped skill will prompt for each provider's client ID/secret and callmanage_oauth action: configure. If a demo user is requested, it seeds one viainsert_rowon the users table. -
After it returns, run
manage_oauth action: getto confirm and print the redirect URLs the user must register with each provider. -
Append one line to
docs/butterbase/04-build-log.md:<ISO timestamp> auth manage_oauth ok -
Tick
- [x] authin00-state.md, setcurrent_stage:to the next unchecked stage. -
Return to
journeyorchestrator (or ask"Continue to the next stage? (yes/no)").
Outputs
- Configured OAuth providers.
- Optional seed user.
- One line in
04-build-log.md.
Anti-patterns
- ❌ Echoing OAuth client secrets back to the user.
- ❌ Forgetting to give the user the provider-side redirect URL — auth will silently fail without it.