mixin-skills

This skill should be used when the user asks about "Mixin SDK", "how does Mixin work", "what's the difference between session key and spend key", "Safe vs legacy", or needs a high-level overview of the Mixin Network programming model in Go or Node.js.

This skill should be used when building Mixin bots — loading keystores and constructing SafeUser (Go) / MixinApi (Node), JWT auth, session/spend key separation, sending messages (direct, group, text, post, app card, buttons), Blaze WebSocket loop at wss://blaze.mixin.one (Mixin-Blaze-1, gzip), conversations and group management, user search, bare user TIP PIN registration, OAuth third-party login, idempotency, message_id dedup, and the mixin-kit-go wrapper (Go-only).

This skill should be used when calling the public Mixin Safe Computer service at https://computer.mixin.one — registering a Mixin user as a Computer user (AddUser), submitting Solana system calls via MTG transactions, encoding the OperationTypeAddUser / OperationTypeSystemCall extra format, querying computer info / users / deployed assets / system calls / nonce accounts, requesting fees in XIN based on SOL, deploying external assets, and locking nonce accounts.

This skill should be used when designing, implementing, reviewing, or debugging Mixin MTG / multisig Go programs — Mixin Trusted Group services, observer/signer nodes, deterministic action processing, threshold configuration, FROST or MPC signing, mtg.Group / AttachWorker, and Mixin Trusted Computer style services using github.com/MixinNetwork/safe/mtg and github.com/MixinNetwork/multi-party-sig.

Use this skill when the user asks about Mixin OAuth login, authorizing users via Mixin, mixin://codes QR code login, PKCE frontend login without client_secret, backend OAuth code exchange with client_secret, OAuthGetAccessToken, SignOauthAccessToken, OAuthKeystore, scope, or using Mixin as an identity provider for web/mobile apps.

This skill should be used for Mixin Safe operations — listing Safe outputs (UTXOs), building/encoding/signing/verifying raw transactions, ghost keys, MixAddress recipients, multisig requests (create/sign/unlock/cancel), output selection, withdrawal fees, withdrawal destination first output, MixinCashier, deposit entries, address book, asset metadata fetch, balances, snapshots, network ticker, transaction-to-group (MTG), MIX/MIN address encoding, MTG extra payload, storage entry pattern, mixin:// and https://mixin.one/pay URL schemes.