agentleFS
ClawpumpClawpump/agents-skills/skills/laso-finance/SKILL.md

laso-finance

Skill3 starsChanged 7 months agoMITView on GitHub

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. For reveals, keep the output limited to the requested fields and remind the user to store them securely.

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. About 0 are common, 7 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check setup with laso_status.

    line 7
  2. Very specific:

    If the account is missing or expired, authenticate with laso_auth.

    line 8
  3. Very specific:

    Before any paid order, call laso_quote and show:

    line 11
  4. Distinctive:

    Wait for explicit user approval before paid orders.

    line 17
  5. Very specific:

    After approval, call laso_order with:

    line 18
  6. Very specific:

    After ordering, use laso_get_card_data or laso_refresh_card to poll status.

    line 22
  7. Distinctive:

    Never invent Laso server ids, card ids, merchant data, prices, balances, or order status.

    line 34
  8. Very specific:

    Never place a paid order without a fresh laso_quote.

    line 35
  9. Very specific:

    Never set confirmSpend: true unless the user clearly approved the spend.

    line 36
  10. Distinctive:

    Always use a stable idempotency key for paid orders.

    line 37
  11. Distinctive:

    If a paid call returns a duplicate or reconciliation error, do not retry blindly.

    line 38
  12. Distinctive:

    Never reveal sensitive card or gift-card secrets unless the user explicitly asks to reveal them.

    line 39
  13. Distinctive:

    Do not paste secrets into public posts, emails, or social tools.

    line 40
  14. Distinctive:

    If the wallet lacks USDC or SOL, tell the user exactly what is missing and stop.

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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
  6. Wait for explicit user approval before paid orders.
  7. After approval, call laso_order with:
    • confirmSpend: true
    • maxAmountAtomic from the quote
    • a stable clientOrderId or correlationId
  8. After ordering, use laso_get_card_data or laso_refresh_card to poll status.
  9. 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.