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

journey-auth

Skill535 starsChanged 5 months agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 0 are distinctive, and 4 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.

  • 4

    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 18
  2. Very specific:

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

    line 27
  3. Very specific:

    Read the Auth section of 02-plan.md.

    line 29
  4. Very specific:

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

    line 31

≈ “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: 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.

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