Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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.
Passed 11 of 18 test cases with the skill, and 4 of 18 without it.
and 5 more in the full report
8 fixed5 passed either way9 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
The OAuth provider configuration completed successfully. What exact record line must be appended to docs/butterbase/04-build-log.md?
| Checked | Without skill | With skill |
|---|---|---|
| Appends an entry formatted with ISO timestamp, auth, manage_oauth, and ok separated by spaces | Missed | Passed |
The instructions your model reads when the skill loads.
Stage 3c of the guided journey. Configure OAuth providers and (optionally) auth hooks.
journey when current_stage: auth./butterbase-skills:journey-auth.(n/a) in 00-state.md) if the plan has no end-user auth.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.
docs/butterbase/02-plan.md — the Auth section.docs/butterbase/00-state.md — for app_id.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)").
04-build-log.md.test cases passed, vs 4 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.