Agent skill

Journey Auth

by butterbase-ai in butterbase-ai/butterbase-skills

Use as the auth build stage of the Butterbase journey, after journey-schema (and rls if separate).

MITAuto-check passedBackend & APIs

Install Journey Auth

skills CLI
$ npx skills add butterbase-ai/butterbase-skills --skill journey-auth -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install butterbase-ai/butterbase-skills journey-auth --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/butterbase-ai/butterbase-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/journey-auth .claude/skills/journey-auth && rm -rf skills-src

Use ~/.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/

Facts

Skill name
journey-auth
GitHub stars
534
Token cost
~584 tokens
SKILL.md length
250 words
Files
1
Skills in repo
39
Repo updated
First seen
Licence
MIT

At a glance

Use as the auth build stage of the Butterbase journey, after journey-schema (and rls if separate).

  • Works in 7 steps: Refresh docs. Call butterbase_docs with… → Read the Auth section of 02-plan.md.… → Invoke butterbase-skills:auth-setup via… → …
  • Tasks that involve Authentication
  • SKILL.md covers When to use, Preflight, Inputs and Procedure, plus 2 more sections
  • Reaches docs.butterbase.ai

What it does

Journey Auth is an agent skill from butterbase-ai/butterbase-skills. 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 manageoauth (configure) for providers and optionally manageauthconfig (configureauthhook, updatejwt). Skipped if the plan has no end-user auth.

Its SKILL.md is about 580 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 Backend & APIs, covering Authentication and OAuth and OpenID Connect. The repository describes itself as: Plugin for Butterbase.ai. The licence is MIT.

When your agent uses it

  • Tasks that involve Authentication
  • Tasks that involve OAuth and OpenID Connect

Example prompts

  • “/journey-auth”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Refresh docs. Call butterbase_docs with topic: "auth". For provider-specific setup (Google/GitHub/Apple), also WebFetch…
  2. Read the Auth section of 02-plan.md. Print it back: "About to configure auth: providers=, demo_user=. Proceed?". Wait for yes.
  3. Invoke butterbase-skills:auth-setup via the Skill tool, passing the Auth plan and app_id. The wrapped skill will prompt for each…
  4. After it returns, run manage_oauth action: get to confirm and print the redirect URLs the user must register with each provider.
  5. Append one line to docs/butterbase/04-build-log.md
  6. Tick - [x] auth in 00-state.md, set current_stage: to the next unchecked stage.
  7. Return to journey orchestrator (or ask "Continue to the next stage? (yes/no)").

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.

    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 Auth loads about 584 tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 250 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~85
When it runs · the whole SKILL.md, loaded when a task matches
~584

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). 250 words, ~584 tokens.

Download SKILL.mdSave it as .claude/skills/journey-auth/SKILL.md (or your agent's skills folder).
name
journey-auth
description
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

  1. 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.

  2. 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.

  3. 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.

  4. After it returns, run manage_oauth action: get to confirm and print the redirect URLs the user must register with each provider.

  5. Append one line to docs/butterbase/04-build-log.md: <ISO timestamp> auth manage_oauth ok

  6. Tick - [x] auth in 00-state.md, set current_stage: to the next unchecked stage.

  7. 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.

© 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-auth of butterbase-ai/butterbase-skills.

Open the folder on GitHubat commit aa8ae69

Compare with similar skills

Journey Auth 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.

Journey Auth compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Journey Auth this skillbutterbase-ai/butterbase-skills534—~584Automated safety check: PassMIT
Fortify Developmentcoollabsio/coolify63k4 repos~1.9kAutomated safety check: PassMIT
Cognitoitsmostafa/aws-agent-skills1.2k1 repos~2.3kAutomated safety check: PassMIT
Security Reviewdoorkeeper-gem/doorkeeper5.5k—~1.4kAutomated safety check: PassMIT
OAuth Account Setupspinabot/brigade11k—~878Automated safety check: PassMIT
Auth Implementation Patternsynulihao/AgentSkillOS61810 repos~4.4kAutomated safety check: PassNone

Similar skills

  • Fortify Development

    coollabsio/coolify

    ACTIVATE when the user works on authentication in Laravel. An agent skill from coollabsio/coolify.

    63k GitHub starsUsed in 4 repos~1.9k tokens
    Backend & APIsAuto-check passed
  • Cognito

    itsmostafa/aws-agent-skills

    AWS Cognito user authentication and authorization service. An agent skill from itsmostafa/aws-agent-skills.

    1.2k GitHub starsUsed in 1 repo~2.3k tokens
    Backend & APIsAuto-check passed
  • Security Review

    doorkeeper-gem/doorkeeper

    Verify that code changes do not introduce OAuth security vulnerabilities.

    5.5k GitHub stars~1.4k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • OAuth Account Setup

    spinabot/brigade

    Connects an OAuth 2.0 account such as Gmail with the built-in oauth_authorize tool: an authorization link, automatic code capture and sealed token storage.

    11k GitHub stars~878 tokensUpdated 2 days ago
    Backend & APIsAuto-check passed
  • Auth Implementation Patterns

    ynulihao/AgentSkillOS

    Master authentication and authorization patterns including JWT, OAuth2, session management, and RBAC to build secure, scalable access control systems.

    618 GitHub starsUsed in 10 repos~4.4k tokens
    Backend & APIsAuto-check passed
  • Socialite Development

    hexlet-volunteers/hexlet-sicp

    Manages OAuth social authentication with Laravel Socialite. An agent skill from hexlet-volunteers/hexlet-sicp.

    114 GitHub starsUsed in 5 repos~1.2k tokens
    Backend & APIsAuto-check passed

More from butterbase-ai/butterbase-skills

All 39 skills in this repo
  • AI

    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

    534 GitHub stars~1.1k tokensUpdated 5 days ago
    Auto-check passed
  • 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

    534 GitHub stars~2.2k tokensUpdated 5 days ago
    Auto-check passed
  • 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

    534 GitHub stars~4.9k tokensUpdated 5 days ago
    Auto-check passed
  • 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

    534 GitHub stars~1.5k tokensUpdated 5 days ago
    Auto-check passed
  • 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

    534 GitHub stars~3.5k tokensUpdated 5 days ago
    Auto-check passed
  • 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

    534 GitHub stars~2.8k tokensUpdated 5 days ago
    Auto-check passed

Categories

Questions about Journey Auth

What does Journey Auth do?

Use as the auth build stage of the Butterbase journey, after journey-schema (and rls if separate). Journey Auth is an agent skill from butterbase-ai/butterbase-skills. Use as the auth build stage of the Butterbase journey, after journey-schema (and rls if separate).

When should I use Journey Auth?

Journey Auth fits situations like: tasks that involve Authentication; tasks that involve OAuth and OpenID Connect.

How do I install Journey Auth in Claude Code?

Run `npx skills add butterbase-ai/butterbase-skills --skill journey-auth -a claude-code`. Or copy the skill folder (skills/journey-auth in butterbase-ai/butterbase-skills) into .claude/skills/journey-auth in your project. Claude Code loads it when a task matches its description.

How do I install Journey Auth in Codex?

Run `npx skills add butterbase-ai/butterbase-skills --skill journey-auth -a codex`. Or copy the skill folder (skills/journey-auth in butterbase-ai/butterbase-skills) into .agents/skills/journey-auth in your project. Codex loads it when a task matches its description.

Can I use Journey Auth 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-auth -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-auth, .gemini/skills/journey-auth, .github/skills/journey-auth and .opencode/skills/journey-auth in your project.

What does Journey Auth need to run?

SKILL.md names no scripts, command-line tools or credentials: Journey Auth is instructions for the agent only.

Does Journey Auth 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 Auth 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 Auth use?

Journey Auth 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 Auth use?

About 584 tokens (SKILL.md is roughly 2.3k 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 Auth?

Skills that share tags, products or a category with Journey Auth: Fortify Development (coollabsio/coolify, 63k stars), Cognito (itsmostafa/aws-agent-skills, 1.2k stars), Security Review (doorkeeper-gem/doorkeeper, 5.5k stars) and OAuth Account Setup (spinabot/brigade, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Journey Auth?

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.