trifle-auth_skill

Overview

This skill authenticates with the Trifle API (bot.trifle.life) using Sign-In with Ethereum (SIWE) to enable wallet-based access to the Trifle ecosystem. It manages private key storage, performs SIWE signing, obtains a JWT, and persists session state so other skills can reuse the token. The workflow is focused on secure key handling and automated token storage for downstream tools.

How this skill works

The skill reads an EVM private key from an environment variable or 1Password (with a file fallback), generates or imports a wallet, and requests a SIWE nonce from the Trifle API. It constructs and signs a SIWE message, verifies the signature with the API, receives a JWT valid for 30 days, and writes an auth-state JSON file with token and user metadata. Commands expose login, status, token retrieval (written to a secure temp file), wallet generation, and balance checks.

When to use it

• Enable wallet-based access to Trifle-protected APIs or games
• Provide a reusable JWT for other local skills needing Trifle auth
• Automate periodic re-authentication or token refresh for long-running agents
• Securely generate and store a Trifle-specific EVM wallet

Best practices

• Keep TRIFLE_PRIVATE_KEY in a secure environment or use 1Password integration
• Limit file-based key fallback to user-only permissions (mode 600) and avoid printing private keys
• Use the provided token command to write tokens to a secure temp file rather than stdout
• Rotate wallets or private keys if you suspect compromise and regenerate auth tokens
• Set TRIFLE_AUTH_STATE to customize XDG state path for CI or multi-user setups

Example use cases

• Authenticate a bot that plays the snake game and needs JWT access to vote or act
• Scripts that need to read the user’s ball balance and act on economy rules
• Agents that aggregate user activity across platforms and credit auth bonuses
• Local CI tasks that require Trifle API access without interactive login