How do I install the Journey Auth skill?

Run npx skillmds@latest add butterbase-ai/journey-auth in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Journey Auth safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Journey Auth?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Journey Auth free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Journey Auth?

butterbase-ai (@butterbase-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Journey Auth by butterbase-ai — Agent Skill

Name: Journey Auth
Rating: 4.666666666666667 (3 reviews)
Author: butterbase-ai

Journey Auth

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.

butterbase-ai Updated Sep 9, 2026

File contents

Journey: Auth

Stage 3c of the guided journey. Configure OAuth providers and (optionally) auth hooks.

When to use

Dispatched by journey when current_stage: auth.
Directly via /butterbase-skills:journey-auth.
Skipped (annotated (n/a) in 00-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 — for app_id.

Procedure

Refresh docs. Call butterbase_docs with topic: "auth". For provider-specific setup (Google/GitHub/Apple), also WebFetch https://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 for yes.
Invoke butterbase-skills:auth-setup via the Skill tool, passing the Auth plan and app_id. The wrapped skill will prompt for each provider's client ID/secret and call manage_oauth action: configure. If a demo user is requested, it seeds one via insert_row on the users table.
After it returns, run manage_oauth action: get to 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] auth in 00-state.md, set current_stage: to the next unchecked stage.
Return to journey orchestrator (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.

---name: journey-authdescription: 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.--- # Journey: Auth Stage 3c of the guided journey. Configure OAuth providers and (optionally) auth hooks. ## When to use - Dispatched by `journey` when `current_stage: auth`. - Directly via `/butterbase-skills:journey-auth`. - Skipped (annotated `(n/a)` in `00-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` — for `app_id`. ## Procedure 0. **Refresh docs.** Call `butterbase_docs` with `topic: "auth"`. For provider-specific setup (Google/GitHub/Apple), also WebFetch `https://docs.butterbase.ai/auth`. Skip if cache is fresh. 1. Read the Auth section of `02-plan.md`. Print it back: `"About to configure auth: providers=<list>, demo_user=<yes/no>. Proceed?"`. Wait for `yes`. 2. Invoke `butterbase-skills:auth-setup` via the Skill tool, passing the Auth plan and `app_id`. The wrapped skill will prompt for each provider's client ID/secret and call `manage_oauth action: configure`. If a demo user is requested, it seeds one via `insert_row` on the users table. 3. After it returns, run `manage_oauth action: get` to confirm and print the redirect URLs the user must register with each provider. 4. Append one line to `docs/butterbase/04-build-log.md`: `<ISO timestamp> auth manage_oauth ok` 5. Tick `- [x] auth` in `00-state.md`, set `current_stage:` to the next unchecked stage. 6. Return to `journey` orchestrator (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.

Frequently asked questions