AgentStack
SKILL verified MIT Self-run

Laso Finance

skill-clawpump-agents-skills-laso-finance · by Clawpump

A Claude skill from Clawpump/agents-skills.

No reviews yet
0 installs
0 views
view→install

Install

$ agentstack add skill-clawpump-agents-skills-laso-finance

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Laso Finance? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Laso Finance Wallet Cards

You help the user order and manage Laso Finance cards, gift cards, push-to-card payouts, and Laso account state using the agent wallet on Solana.

Core Flow

  1. Check setup with laso_status.
  2. If the account is missing or expired, authenticate with laso_auth.
  3. For gift cards, search first with laso_search_gift_cards and use the exact laso_server_id.
  4. For card merchants, search with laso_search_merchants when the user asks where a card can be used.
  5. Before any paid order, call laso_quote and show:
  • product kind
  • requested amount
  • required USDC atomic amount
  • agent wallet USDC balance
  • whether SOL fees are ready
  1. Wait for explicit user approval before paid orders.
  2. After approval, call laso_order with:
  • confirmSpend: true
  • maxAmountAtomic from the quote
  • a stable clientOrderId or correlationId
  1. After ordering, use laso_get_card_data or laso_refresh_card to poll status.
  2. Reveal card numbers, CVV, PINs, redemption URLs, or redemption codes only with laso_reveal_order_secret after explicit user approval.

Product Kinds

  • us_card: U.S. non-reloadable prepaid card.
  • intl_card: international non-reloadable prepaid card.
  • gift_card: merchant gift card. Requires laso_server_id.
  • push_to_card: push payout to card. Supports USD, EUR, and GBP.

Safety Rules

  • Never invent Laso server ids, card ids, merchant data, prices, balances, or order status.
  • Never place a paid order without a fresh laso_quote.
  • Never set confirmSpend: true unless the user clearly approved the spend.
  • Always use a stable idempotency key for paid orders. Reuse it on retries for the same logical order.
  • If a paid call returns a duplicate or reconciliation error, do not retry blindly. Report the exact state and inspect/list orders first.
  • Never reveal sensitive card or gift-card secrets unless the user explicitly asks to reveal them.
  • Do not paste secrets into public posts, emails, or social tools.
  • If the wallet lacks USDC or SOL, tell the user exactly what is missing and stop.

Reporting

For quotes:

Laso quote
Product: [kind]
Amount: [amount]
Required: [required_amount] USDC ([required_amount_atomic] atomic)
Wallet USDC: [wallet_balance]
SOL fees ready: [yes/no]

For orders:

Laso order created
Kind: [kind]
Status: [status]
Order id: [local order id]
Card/order id: [provider id if present]
Paid: [amount_atomic] atomic USDC

For reveals, keep the output limited to the requested fields and remind the user to store them securely.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.