Make your own AI.

Write a personality, sign it, and download a carrier anyone can drop onto a rewritable. The keypair is minted in your browser — the private key never leaves this page.

A short handle for this AI. Lowercase letters, digits, - and _; must start with a letter or digit; up to 64 characters.
One line, shown on the carrier card. Optional — defaults to “The <role> role.”
The system prompt — the heart of the AI. This is what retunes the ⌘K editor when the role is active. Cannot contain a backtick, ${, or <DOC> (reserved runtime markers).
Optional. Offered on activation (your session only; your key is untouched).
Optional. Where the recommended model runs.
Optional. Which product kinds this AI is best for — advisory only, a mismatch just warns.
Advanced
Optional. Credential namespaces this role may read/write, one per line (or comma-separated). The vault: prefix is added automatically. Each namespace is lowercase letters, digits, -, _.
Ed25519 signed in-browser. Nothing is uploaded.

Signed. Your two files.

Your intelligence is minted and signed with a fresh Ed25519 key. Both files should have downloaded automatically — if your browser didn’t save them, use the download links below. The carrier holds only your public key; the private key is in the separate .key.json.

signed · author

Keep the key.json secret

It holds your private key — the only thing that can publish updates to this intelligence under your author identity. Never commit or share it. If you lose it, you can still use this carrier, but you can never re-sign an update as the same author.

Test it: open role.intelligence.html in a browser. The carrier is itself a skill-host, so the role is already installed — activate it from the “AI” chip in the status bar. Then drop the same file onto any other rewritable to install the role there.

Back to the gallery

This browser can’t sign in-page

The AI Maker mints an Ed25519 keypair with WebCrypto, entirely in your browser. This browser doesn’t support Ed25519 (or isn’t running in a secure context). Open this page in a current Chrome, Safari 17+, Firefox, or Edge over https and try again. Nothing here works halfway — a signature has to be real to be trusted.