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.
In this repository12 other files it gives its agents.
- alpha-scannerSkill
- clawhunter-bountiesSkill
- clawhunter-content-studioSkill
- clawpumpSkill
- dca-strategySkill
- dex-poolsSkill
- meme-analyzerSkill
- risk-managerSkill
- rug-checkSkill
- straight-talkSkill
- survivor-checkSkill
- whale-trackerSkill
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
- Very specific: line 7
Check setup with laso_status.
- Very specific: line 8
If the account is missing or expired, authenticate with laso_auth.
- Very specific: line 11
Before any paid order, call laso_quote and show:
- Distinctive: line 17
Wait for explicit user approval before paid orders.
- Very specific: line 18
After approval, call laso_order with:
- Very specific: line 22
After ordering, use laso_get_card_data or laso_refresh_card to poll status.
- Distinctive: line 34
Never invent Laso server ids, card ids, merchant data, prices, balances, or order status.
- Very specific: line 35
Never place a paid order without a fresh laso_quote.
- Very specific: line 36
Never set confirmSpend: true unless the user clearly approved the spend.
- Distinctive: line 37
Always use a stable idempotency key for paid orders.
- Distinctive: line 38
If a paid call returns a duplicate or reconciliation error, do not retry blindly.
- Distinctive: line 39
Never reveal sensitive card or gift-card secrets unless the user explicitly asks to reveal them.
- Distinctive: line 40
Do not paste secrets into public posts, emails, or social tools.
- Distinctive: line 41
If the wallet lacks USDC or SOL, tell the user exactly what is missing and stop.
≈ “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.
Files
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
- Check setup with
laso_status. - If the account is missing or expired, authenticate with
laso_auth. - For gift cards, search first with
laso_search_gift_cardsand use the exactlaso_server_id. - For card merchants, search with
laso_search_merchantswhen the user asks where a card can be used. - Before any paid order, call
laso_quoteand show:- product kind
- requested amount
- required USDC atomic amount
- agent wallet USDC balance
- whether SOL fees are ready
- Wait for explicit user approval before paid orders.
- After approval, call
laso_orderwith:confirmSpend: truemaxAmountAtomicfrom the quote- a stable
clientOrderIdorcorrelationId
- After ordering, use
laso_get_card_dataorlaso_refresh_cardto poll status. - Reveal card numbers, CVV, PINs, redemption URLs, or redemption codes only with
laso_reveal_order_secretafter 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. Requireslaso_server_id.push_to_card: push payout to card. SupportsUSD,EUR, andGBP.
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: trueunless 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 USDCFor reveals, keep the output limited to the requested fields and remind the user to store them securely.
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
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.

