Description

Interact with Mamo DeFi yield strategies on Base (Moonwell). Deposit/withdraw USDC, cbBTC, MAMO, or ETH into automated yield strategies. Check APY rates and account status.

README (SKILL.md)

Mamo — DeFi Yield Aggregator (Moonwell on Base)

Name: Mamo
Author: anajuliabit

Mamo is a DeFi yield aggregator built by Moonwell on Base chain. It deploys per-user smart contracts that split deposits between Moonwell core markets and Morpho vaults for optimized yield, with auto-compounding of rewards.

Chain: Base (8453) Strategies: USDC stablecoin, cbBTC lending, ETH lending, MAMO staking

Setup

cd ~/clawd/skills/mamo/scripts  # or wherever this skill lives
npm install
export MAMO_WALLET_KEY=0x...     # wallet private key
export MAMO_RPC_URL=https://...  # optional, defaults to Base public RPC

Commands

# Create a yield strategy (deploys your personal strategy contract via on-chain factory)
node mamo.mjs create usdc_stablecoin
node mamo.mjs create cbbtc_lending
node mamo.mjs create eth_lending

# Deposit tokens (approve + deposit to your strategy contract)
node mamo.mjs deposit 100 usdc
node mamo.mjs deposit 0.5 cbbtc

# Withdraw tokens
node mamo.mjs withdraw 50 usdc
node mamo.mjs withdraw all cbbtc

# Account overview — wallet balances + strategy positions
node mamo.mjs status

# Current APY rates
node mamo.mjs apy
node mamo.mjs apy usdc_stablecoin

How It Works

Create strategy → Calls the on-chain StrategyFactory to deploy a personal proxy contract owned by your wallet
Deposit → CLI approves token spend, then calls deposit(amount) on your strategy contract
Yield accrues → Strategy splits funds between Moonwell + Morpho, auto-compounds rewards via CowSwap
Withdraw → Only the owner (your wallet) can withdraw. Funds go directly to your wallet

Strategy addresses are stored locally in ~/.config/mamo/strategies.json (the on-chain registry may not be updated for user-created strategies).

Key Addresses

Token	Address
USDC	`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`
cbBTC	`0xcbB7C0000aB88B473b1f5aFd9ef808440eed33Bf`
MAMO	`0x7300b37dfdfab110d83290a29dfb31b1740219fe`
Registry	`0x46a5624C2ba92c08aBA4B206297052EDf14baa92`

Security

Use a dedicated hot wallet — not your main holdings
Only deposit what you're comfortable having in a hot wallet
Store MAMO_WALLET_KEY in env vars, never in committed files
All transactions are simulated before sending

Usage Guidance

What to consider before installing/use: - Metadata mismatch: the registry lists no required env vars but the CLI requires MAMO_WALLET_KEY (your wallet private key). That omission is an integrity/visibility problem — treat the private key requirement as real even if not declared. Do not set your main/private key in the environment for this skill. - Use a dedicated hot wallet: if you try the tool, create a separate wallet with limited funds and use that key only. Never expose your main wallet private key in environment variables or committed files. - Prefer ephemeral signing: if possible, avoid placing a raw private key in plaintext. Use a hardware signer, a JSON-RPC signer with restricted permissions, or an ephemeral test key. - Review endpoints & addresses: the code posts SIWE messages and other requests to mamo-queues.moonwell.workers.dev and mamo-indexer.moonwell.workers.dev and interacts with on-chain contract addresses included in references. Verify these endpoints and contract addresses independently (official docs/repos) before trusting them. - Be aware of persistence: the CLI writes ~/.config/mamo/auth.json and strategies.json. Inspect these files if you run the tool to ensure no sensitive secrets are stored accidentally. - Autonomy risk: the platform allows the agent to invoke skills autonomously. If you set MAMO_WALLET_KEY in the agent environment, an autonomous agent could sign/send transactions without explicit per-transaction confirmation. If you must provide a key, prefer manual invocation or deny autonomous invocation for this skill. - Audit before use: the repository contains many source files implementing blockchain calls; if you plan to use real funds, have someone you trust audit the code (or run the official published mamo-cli from Moonwell's official repo/registry rather than an unknown registry copy). - Dry-run/testing: use the CLI's dry-run mode and test on a non-mainnet environment (or with tiny amounts) first. Don't store the private key in a repository or shared machine account. If you want, I can list precise code locations where the private key is read, where network calls happen, and where files are written so you (or an auditor) can inspect them quickly.

Capability Analysis

Type: OpenClaw Skill Name: Developer: Version: Description: OpenClaw Agent Skill Suspicious High-Entropy/Eval files: 25 The OpenClaw AgentSkills skill bundle for Mamo CLI is benign. The `SKILL.md` file provides clear, non-manipulative instructions for the AI agent and the user, including security best practices for handling private keys. The JavaScript/TypeScript code (`scripts/mamo.mjs`, `src/**/*.ts`) performs legitimate DeFi operations on the Base chain using the `viem` library, such as creating strategies, depositing/withdrawing tokens, and fetching account status/APY rates. Network communication is restricted to Moonwell-controlled API endpoints (`https://mamo-queues.moonwell.workers.dev`, `https://mamo-indexer.moonwell.workers.dev`) and CoinGecko for price data (`https://api.coingecko.com`), all of which are consistent with the stated purpose. Private keys are read from environment variables (`MAMO_WALLET_KEY`) as expected for a crypto CLI, and local state is stored in `~/.config/mamo/`.

Capability Assessment

ℹ Purpose & Capability

The code and documentation implement a CLI to deploy/operate per-user Mamo strategy contracts on Base and to query APYs — which matches the skill name/description. However, the skill metadata in the registry claims no required env vars while both SKILL.md/README and the code require a private key (MAMO_WALLET_KEY) and optionally MAMO_RPC_URL. That omission is an incoherence between declared requirements and actual needs.

⚠ Instruction Scope

SKILL.md instructs installing and exporting a private key (MAMO_WALLET_KEY) and running the CLI commands (create, deposit, withdraw, status). The runtime code will: load a .env file from the script directory if present, read MAMO_WALLET_KEY and MAMO_RPC_URL from environment, sign SIWE messages and on-chain transactions, call Mamo backend endpoints (mamo-queues.moonwell.workers.dev, mamo-indexer.moonwell.workers.dev), and read/write ~/.config/mamo/auth.json and strategies.json. These actions are within the expected scope for a wallet-using CLI, but they do involve reading local .env files and persistent storage and transmitting signed messages/auth payloads to external APIs — all high-impact operations for a wallet-enabled tool and worth explicit prominence in the metadata/instructions.

✓ Install Mechanism

No remote install script is embedded in the skill bundle; SKILL.md instructs running npm install and executing the included Node script. All dependencies are standard npm packages (viem, siwe, commander, dotenv). There are no downloads from obscure URLs or archives in the install spec. Risk from installation itself is low, but running npm install pulls third-party packages as usual.

⚠ Credentials

The functionality legitimately requires a signing key (MAMO_WALLET_KEY) and optionally an RPC URL, but the registry metadata lists no required env vars and the skill manifest did not declare the private key as the primary credential. Asking for a raw private key (and providing code that will read a .env file in the script dir) is expected for a CLI that signs txs, but is high-risk and should be declared clearly. The code stores auth tokens locally (~/.config/mamo/auth.json), which is expected but should be noted. No unrelated credentials are requested.

ℹ Persistence & Privilege

The skill writes persistent configuration to ~/.config/mamo (strategies.json, auth.json) and may store API auth tokens returned from the backend. always: false (not force-included). The skill can be invoked autonomously (platform default). If you set MAMO_WALLET_KEY in the environment for the agent, the skill gains the ability to sign and submit transactions autonomously — a meaningful risk that depends on whether you allow the agent to run skills without manual approval.

Version History

v1.0.1

Re-publish with full metadata

v1.0.0

Initial release — CLI for Mamo DeFi yield aggregator on Base (Moonwell)

Metadata

Slug mamo

Version 1.0.1

License —

All-time Installs 0

Active Installs 0

Total Versions 2

Frequently Asked Questions

What is Mamo?

Interact with Mamo DeFi yield strategies on Base (Moonwell). Deposit/withdraw USDC, cbBTC, MAMO, or ETH into automated yield strategies. Check APY rates and account status. It is an AI Agent Skill for Claude Code / OpenClaw, with 1381 downloads so far.

How do I install Mamo?

Run "/install mamo" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Mamo free?

Yes, Mamo is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Mamo support?

Mamo is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Mamo?

It is built and maintained by Ana (@anajuliabit); the current version is v1.0.1.

More Skills

Mamo