Skip to content
Docs: Teams and sign-in

Team and help

Teams and sign-in

Email links and passkeys, who can do what, and the tokens that the CLI and agents use.

On this page

Signing in

There are no passwords. Enter your work email on the sign-in page and open the link we send. The link works once and expires after 15 minutes; opening it shows a button, so a mail scanner that follows links cannot use it up. You can ask for five links per address every 15 minutes.

If your team set an allowed list of email domains, only those addresses can sign in. Anyone on an allowed domain gets an account the first time they sign in.

Passkeys

Add a passkey in Settings → Passkeys and sign in with your fingerprint, face or device PIN instead of an email. Add one per device, name them so you can tell them apart, and remove a lost one from any other device. Adding or removing a passkey asks you to confirm it is you if you have not signed in for a few minutes.

Roles

Everyone can browse the library, assign skills, write overlays, make and review proposals, and create tokens. Admins can also change roles and archive skills and repos. The first person to sign in is an admin; there is always at least one.

API tokens

Personal tokens (sk_…) are for the CLI, the REST API and the MCP server. Create them in Settings → API tokens. A token is shown once; Skillify keeps only a hash.

  • Read tokens can list and read, and run sync.
  • Write tokens can also assign skills, set overlays and open proposals.

Revoke a token at any time. Sign out everywhere in Settings ends every browser session at once; tokens are revoked one by one.

Passkey
Sign in with your device’s fingerprint, face or PIN instead of an email link. Add one in Settings.
Admin
Admins can also change roles and archive skills and repos. Everyone can assign, edit, propose and review.Also: role
API token
A personal token (sk_…) for the CLI, the REST API and MCP. Read tokens can look; write tokens can change things.Also: sk_, SKILLIFY_TOKEN
Ingest key
A write-only key in .skillify/config.json. It can only report status and usage, so it is safe to commit.It cannot read skills or change anything. Rotate it in the repo’s settings if you want to cut off old clones.Also: ik_, ingestKey