Skip to content
Early preview. authbase is in active development. The source code and packages are not public yet; these docs describe how it works ahead of the first public release.

Claude skills

Two Agent Skills that teach Claude to work with authbase. Each folder is self-contained: take one, both, or neither.

Skill Use it when you want Claude to…
authbase-integrate add authbase to an app’s backend: sign-up, login, refresh, logout, protected routes, roles, password reset (Node, Kotlin/JVM, Go, any language)
authbase-self-host put authbase on a Linux server with HTTPS, back it up, upgrade it, rotate keys, handle a leak

Both keep secrets out of code, files and chat, and ask before anything destructive. They carry their own references and scripts, so they work in any project, without this repository next to them.

The skills are published with the first public release, as zips attached to each release. Once they are out, install them like this.

Claude Code, for all your projects:

Terminal window
mkdir -p ~/.claude/skills
cp -R skills/authbase-integrate ~/.claude/skills/ # and/or authbase-self-host

or for one project only: copy the folder into that project’s .claude/skills/. Claude picks a skill up by itself when a task matches its description; you can also ask for it by name.

Claude apps (claude.ai, desktop): zip a skill (skills/package.sh writes build/skills/<name>.zip, and every release carries the zips), then upload it under Settings → Capabilities → Skills.

Without this repository: download authbase-integrate.zip or authbase-self-host.zip from a release, or just the folder from GitHub, and install it as above.

The skills describe this version of authbase. api/tests/skills_test.go fails when a skill names an endpoint the API does not have, when its error code table differs from the API’s, or when a script stops being runnable; update the skill in the same change as the API.

The integrate skill was tested the way it will be used: a fresh Claude, given only the skill, added authbase to a small Express app (sign-up, login, cookie refresh, per-user data, an admin route), and scripts/verify-flow.sh then passed all eleven checks against a real instance. Its feedback shaped the Express recipe and the error table.