Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
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.
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.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Locus connects AI agents to crypto wallets via MCP. Tools are dynamic — each user gets different tools based on their permission group.
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:
command -v mcporter || npm i -g mcporter
mcporter config get locus 2>/dev/null If configured, skip to Usage. If the user wants to reconfigure, run: mcporter config remove locus
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.
mcporter config add locus \ --url "https://mcp.paywithlocus.com/mcp" \ --header "Authorization=Bearer <API_KEY>" \ --scope home
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.
Users can also run the setup script directly from the Clawdbot workspace root: bash skills/locus/scripts/setup.sh
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"}'
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
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
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.