How do I install the Locus skill?

Run npx skillmds@latest add kernel8901/locus in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Locus safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Locus?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Locus free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

kernel8901 (@kernel8901) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Locus by kernel8901 — Agent Skill

Name: Locus
Author: kernel8901

Locus

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.

kernel8901 cde1e37 4 files · 7.3 KB Updated Sep 17, 2026

File contents

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

---name: locusdescription: 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 SkillLocus 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```bashcommand -v mcporter || npm i -g mcporter```### Step 2: Check if Locus is already configured```bashmcporter config get locus 2>/dev/null```If configured, skip to **Usage**. If the user wants to reconfigure, run:```bashmcporter config remove locus```### Step 3: Ask the user for their API keyTell 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```bashmcporter config add locus \ --url "https://mcp.paywithlocus.com/mcp" \ --header "Authorization=Bearer <API_KEY>" \ --scope home```### Step 5: Verify the connection```bashmcporter 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 setupUsers can also run the setup script directly from the Clawdbot workspace root:```bashbash skills/locus/scripts/setup.sh```## Usage**Always discover available tools first:**```bashmcporter 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:**```bashmcporter call locus.<tool_name> param1=value1 param2=value2```For array/object parameters:```bashmcporter call locus.<tool_name> --args '{"key": "value"}'```## Email → Payment Flow1. Scan inbox for payment-related emails (invoices, bills, splits, reimbursements)2. Identify actionable items with amounts, recipients, and context3. Summarize findings to user4. On user approval, execute payments via available tools5. **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

Frequently asked questions