| name | locus |
| description | Locus payment tools for AI agents. Use when asked to send payments, check wallet balances, list tokens, approve token spending, or process payment-related actions from emails. Also use for demos of Locus (YC F25) payment infrastructure — scanning emails for payment requests and initiating crypto payments via wallet. |
Cleanup Review
python scripts/_purge_cache.py is an optional cleanup helper for the Locus Payment Skill skill. It may recursively remove /tmp/skill_scratch, /var/tmp/skill_output. Show the exact paths first, explain whether they are skill-private temporary paths or user state, and run the cleanup only after the user confirms.
Locus Payment Skill
Locus connects AI agents to crypto wallets via MCP. Tools are dynamic — each user gets different tools based on their permission group.
Setup (Agent-Guided)
When the user asks to set up Locus, use payments, or anything payment-related — check if Locus is configured and walk them through setup interactively:
Step 1: Check if mcporter is installed
command -v mcporter || npm i -g mcporter
Step 2: Check if Locus is already configured
mcporter config get locus 2>/dev/null
If configured, skip to Usage. If the user wants to reconfigure, run:
mcporter config remove locus
Step 3: Ask the user for their API key
Tell them:
You'll need a Locus API key to connect your wallet. Get one at https://app.paywithlocus.com — each key is tied to your wallet and permission group. Paste it here when you're ready.
Wait for the user to provide their key. It should start with locus_. If it doesn't, warn them and confirm before proceeding.
Step 4: Configure mcporter
mcporter config add locus \
--url "https://mcp.paywithlocus.com/mcp" \
--header "Authorization=Bearer <API_KEY>" \
--scope home
Step 5: Verify the connection
mcporter list locus
If tools appear, setup is complete — tell the user they're ready. If it fails, ask them to double-check their API key and try again.
Alternative: Script-based setup
Users can also run the setup script directly from the Clawdbot workspace root:
bash skills/locus/scripts/setup.sh
Usage
Always discover available tools first:
mcporter list locus --schema
This returns all tools the user's permission group allows. Tools vary per user — do not assume which tools exist. Use the schema output to understand parameters.
Call any discovered tool:
mcporter call locus.<tool_name> param1=value1 param2=value2
For array/object parameters:
mcporter call locus.<tool_name> --args '{"key": "value"}'
Email → Payment Flow
- Scan inbox for payment-related emails (invoices, bills, splits, reimbursements)
- Identify actionable items with amounts, recipients, and context
- Summarize findings to user
- On user approval, execute payments via available tools
- Always confirm with user before sending any payment
Safety Rules
- Never send payments without explicit user confirmation
- Always show: recipient, token, amount, and memo before executing
- Check available balance before attempting payments
- Double-check recipient addresses — typos mean lost funds
- Confirm large payments (>$100) with extra care
