reva
Complete Reva wallet management - passwordless authentication, PayID name claiming, multi-chain crypto transfers to PayIDs or wallet addresses, balance tracking across networks, account details information, and deposit management
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/pax47/revaReva
Passwordless authentication and wallet management for Reva users.
Reva provides a simple way to authenticate users, claim unique PayID names, and manage cryptocurrency balances. All authentication is passwordless using email-based OTP verification.
Authentication
Reva uses a passwordless authentication flow. Users receive a one-time password (OTP) via email, verify it, and receive an access token for subsequent operations.
Login/Register Flow
There is no difference between registration and login - both use the same passwordless flow:
- User provides their email address
- System sends OTP to the email
- User provides the OTP code
- System verifies OTP and returns access token
- Access token is stored securely for future operations
The access token MUST be stored securely after verification and reused for all protected operations.
Available Commands
1. Login or Register
Triggers: When user wants to login, register, sign in, sign up, authenticate, or access Reva
Process:
- Ask user for their email address if not provided
- Call the authentication script to send OTP:
{baseDir}/scripts/send-otp.sh <email> - Inform user that OTP has been sent to their email
- Ask user to provide the OTP code they received
- Call the verification script:
{baseDir}/scripts/verify-otp.sh <email> <otp> - If successful, inform user they are now authenticated
- The access token is automatically stored for future use
2. Claim PayID
Triggers: When user wants to claim a PayID, get a PayID name, register a PayID, or set their PayID
Requirements: User must be authenticated first (have valid access token)
Process:
- Check if user is authenticated by calling:
{baseDir}/scripts/check-auth.sh - If not authenticated, prompt user to login first
- Ask user for their desired PayID name if not provided
- Call the claim script:
{baseDir}/scripts/claim-payid.sh <desired_payid> - Handle response:
- Success: Inform user their PayID was claimed successfully
- Already taken: Inform user the PayID is taken and ask for another choice
- Invalid format: Explain format requirements and ask again
- Unauthorized: Token expired, ask user to login again
3. View Balance
Triggers: When user wants to check balance, see wallet balance, view funds, or check how much money they have
Requirements: User must be authenticated first (have valid access token)
Process:
- Check if user is authenticated by calling:
{baseDir}/scripts/check-auth.sh - If not authenticated, prompt user to login first
- Call the balance script:
{baseDir}/scripts/get-balance.sh - Display the balance to user in a friendly format showing each token with its amount, symbol, and chain (network)
- If unauthorized error, token expired - ask user to login again
Display Format Example:
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-pax47-reva": {
"enabled": true,
"auto_update": true
}
}
}