Agent skill

Torch Liquidation Bot

by LeoYeAI in LeoYeAI/openclaw-master-skills

Autonomous vault-based liquidation keeper for Torch Market lending on Solana.

MITAuto-check passedBusiness, Finance & HR

Install Torch Liquidation Bot

skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill torch-liquidation-bot -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LeoYeAI/openclaw-master-skills torch-liquidation-bot --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/torchliquidationbot .claude/skills/torch-liquidation-bot && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
torch-liquidation-bot
GitHub stars
2.2k
Token cost
~4.8k tokens
SKILL.md length
1,510 words
Files
22
Skills in repo
1,235
Repo updated
First seen
Licence
MIT

At a glance

Autonomous vault-based liquidation keeper for Torch Market lending on Solana.

  • Works in 4 steps: Install → Create and Fund a Vault (Human Principal) → Run the Bot → …
  • Tasks that involve Banking and insurance
  • SKILL.md covers How It Works, Getting Started, Architecture and Vault Safety Model, plus 7 more sections
  • Runs JavaScript scripts from its folder; calls npm, npx and vault; needs SOLANA_PRIVATE_KEY

What it does

Torch Liquidation Bot is an agent skill from LeoYeAI/openclaw-master-skills. Autonomous vault-based liquidation keeper for Torch Market lending on Solana. Scans all migrated tokens for underwater loan positions (LTV 65%) using the SDK's built-in bulk loan scanner (getAllLoanPositions), builds and executes liquidation transactions through a Torch Vault, and collects a 10% collateral bonus. The agent keypair is generated in-process -- disposable, holds nothing of value. All SOL and collateral tokens route through the vault. The human principal creates the vault, funds it, links the agent…

Its SKILL.md is about 4.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 24 other files (for example `_meta.json`, `agent.json` and `audit.md`). Compatibility notes: REQUIRED: SOLANARPCURL (HTTPS Solana RPC endpoint) REQUIRED: VAULTCREATOR (vault creator pubkey). OPTIONAL: SOLANAPRIVATEKEY -- the bot generates a fresh…

It sits in Business, Finance & HR, covering Banking and insurance. It works with Solana. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.

When your agent uses it

  • Tasks that involve Banking and insurance

Example prompts

  • “/torch-liquidation-bot”

Requirements

  • Node.js
  • A credential in SOLANA_PRIVATE_KEY
  • Compatibility (from SKILL.md): REQUIRED: SOLANA_RPC_URL (HTTPS Solana RPC endpoint) REQUIRED: VAULT_CREATOR (vault creator pubkey). OPTIONAL: SOLANA_PRIVATE_KEY -- the bot generates a fresh disposable keypair in-process if not provided. The agent wallet holds nothing of value (~0.01 SOL for gas). All liquidation proceeds (collateral tokens) route to the vault. The vault can be created and funded entirely by the human principal. This skill sets disable-model-invocation: true -- it must not be invoked autonomously without explicit user initiation. The Torch SDK is bundled in lib/torchsdk/ -- all source included for full auditability. No API server dependency. The vault can be created and funded entirely by the human principal -- the agent never needs access to funds.

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Install
  2. Create and Fund a Vault (Human Principal)
  3. Run the Bot
  4. Configuration

What it can do on your machine

Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships script files (JavaScript, from the files we listed), which the agent can run.

    Shell commands in SKILL.md call:

    • npm
    • npx
    • vault
    • pnpm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com
    • torch.market
    • npmjs.com
    • clawhub.ai

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • SOLANA_PRIVATE_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    REQUIRED: SOLANA_RPC_URL (HTTPS Solana RPC endpoint) REQUIRED: VAULT_CREATOR (vault creator pubkey). OPTIONAL: SOLANA_PRIVATE_KEY -- the bot generates a fresh disposable keypair in-process if not provided. The agent wallet holds nothing of value (~0.01 SOL for gas). All liquidation proceeds (collateral tokens) route to the vault. The vault can be created and funded entirely by the human principal. This skill sets disable-model-invocation: true -- it must not be invoked autonomously without explicit user initiation. The Torch SDK is bundled in lib/torchsdk/ -- all source included for full auditability. No API server dependency. The vault can be created and funded entirely by the human principal -- the agent never needs access to funds.

    From compatibility in the SKILL.md frontmatter.

Context cost

Torch Liquidation Bot loads about 4.8k tokens when it runs. Until then it costs about 156 tokens; SKILL.md has 1,510 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~156
When it runs · the whole SKILL.md, loaded when a task matches
~4.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 1,510 words, ~4,836 tokens.

Download SKILL.mdSave it as .claude/skills/torch-liquidation-bot/SKILL.md (or your agent's skills folder). This skill also uses 21 other files; get the full folder from GitHub.
name
torch-liquidation-bot
description
Autonomous vault-based liquidation keeper for Torch Market lending on Solana. Scans all migrated tokens for underwater loan positions (LTV > 65%) using the SDK's built-in bulk loan scanner (getAllLoanPositions), builds and executes liquidation transactions through a Torch Vault, and collects a 10% collateral bonus. The agent keypair is generated in-process -- disposable, holds nothing of value. All SOL and collateral tokens route through the vault. The human principal creates the vault, funds it, links the agent, and retains full control. Built on torchsdk v3.7.22 and the Torch Market protocol.
compatibility
REQUIRED: SOLANA_RPC_URL (HTTPS Solana RPC endpoint) REQUIRED: VAULT_CREATOR (vault creator pubkey). OPTIONAL: SOLANA_PRIVATE_KEY -- the bot generates a fresh disposable keypair in-process if not provided. The agent wallet holds nothing of value (~0.01 SOL for gas). All liquidation proceeds (collateral tokens) route to the vault. The vault can be created and funded entirely by the human principal. This skill sets disable-model-invocation: true -- it must not be invoked autonomously without explicit user initiation. The Torch SDK is bundled in lib/torchsdk/ -- all source included for full auditability. No API server dependency. The vault can be created and funded entirely by the human principal -- the agent never needs access to funds.
version
4.0.4
license
MIT
disable-model-invocation
true
metadata.author
torch-market
metadata.version
4.0.4
metadata.clawhub
https://clawhub.ai/mrsirg97-rgb/torch-liquidation-bot
metadata.kit-source
https://github.com/mrsirg97-rgb/torch-liquidation-kit
metadata.website
https://torch.market
metadata.program-id
8hbUkonssSEEtkqzwM7ZcZrD9evacM92TcWSooVF4BeT
metadata.keywords
solana, defi, liquidation, liquidation-bot, liquidation-keeper, collateral-lending, vault-custody, ai-agents, agent-wallet, agent-safety, treasury-lending…

Torch Liquidation Bot

You're here because you want to run a liquidation keeper on Torch Market -- and you want to do it safely.

Every migrated token on Torch has a built-in lending market. Holders lock tokens as collateral and borrow SOL from the community treasury (up to 50% LTV, 2% weekly interest). When a loan's LTV crosses 65%, it becomes liquidatable. Anyone can liquidate it and collect a 10% bonus on the collateral value.

That's where this bot comes in.

It scans every migrated token's lending market using the SDK's bulk loan scanner (getAllLoanPositions) -- one RPC call per token returns all active positions pre-sorted by health. When it finds one that's underwater, it liquidates it through your vault. The collateral tokens go to your vault ATA. The SOL cost comes from your vault. The agent wallet that signs the transaction holds nothing.

This is not a read-only scanner. This is a fully operational keeper that generates its own keypair, verifies vault linkage, and executes liquidation transactions autonomously in a continuous loop.


How It Works

┌──────────────────────────────────────────────────────────┐
│                  LIQUIDATION LOOP                          │
│                                                           │
│  1. Discover migrated tokens (getTokens)                  │
│  2. For each token, scan all loans (getAllLoanPositions)   │
│     — single RPC call, returns positions sorted by health │
│     — liquidatable → at_risk → healthy                    │
│  3. Skip tokens with no active loans                      │
│  4. For each liquidatable position:                       │
│     → buildLiquidateTransaction(vault=creator)            │
│     → sign with agent keypair                             │
│     → submit and confirm                                  │
│     → break when health != 'liquidatable' (pre-sorted)    │
│  5. Sleep SCAN_INTERVAL_MS, repeat                        │
│                                                           │
│  All SOL comes from vault. All collateral goes to vault.  │
│  Agent wallet holds nothing. Vault is the boundary.       │
└──────────────────────────────────────────────────────────┘
The Agent Keypair

The bot generates a fresh Keypair in-process on every startup. No private key file. No environment variable (unless you want to provide one). The keypair is disposable -- it signs transactions but holds nothing of value.

On first run, the bot checks if this keypair is linked to your vault. If not, it prints the exact SDK call you need to link it:

--- ACTION REQUIRED ---
agent wallet is NOT linked to the vault.
link it by running (from your authority wallet):

  buildLinkWalletTransaction(connection, {
    authority: "<your-authority-pubkey>",
    vault_creator: "<your-vault-creator>",
    wallet_to_link: "<agent-pubkey>"
  })

then restart the bot.
-----------------------

Link it from your authority wallet (hardware wallet, multisig, whatever you use). The agent never needs the authority's key. The authority never needs the agent's key. They share a vault, not keys.

The Vault

This is the same Torch Vault from the full Torch Market protocol. It holds all assets -- SOL and tokens. The agent is a disposable controller.

When the bot liquidates a position:

  • SOL cost comes from the vault (the liquidation payment to cover the borrower's debt)
  • Collateral tokens go to the vault's associated token account (ATA)
  • 10% bonus means the collateral received is worth 10% more than the SOL spent

The human principal retains full control:

  • withdrawVault() — pull SOL at any time
  • withdrawTokens(mint) — pull collateral tokens at any time
  • unlinkWallet(agent) — revoke agent access instantly

If the agent keypair is compromised, the attacker gets dust and vault access that you revoke in one transaction.


Getting Started

1. Install
bash
npm install torch-liquidation-bot@4.0.2

Or use the bundled source from ClawHub — the Torch SDK is included in lib/torchsdk/ and the bot source is in lib/kit/.

2. Create and Fund a Vault (Human Principal)

From your authority wallet:

typescript
import { Connection } from "@solana/web3.js";
import {
  buildCreateVaultTransaction,
  buildDepositVaultTransaction,
} from "./lib/torchsdk/index.js";

const connection = new Connection(process.env.SOLANA_RPC_URL);

// Create vault
const { transaction: createTx } = await buildCreateVaultTransaction(connection, {
  creator: authorityPubkey,
});
// sign and submit with authority wallet...

// Fund vault with SOL for liquidations
const { transaction: depositTx } = await buildDepositVaultTransaction(connection, {
  depositor: authorityPubkey,
  vault_creator: authorityPubkey,
  amount_sol: 5_000_000_000, // 5 SOL
});
// sign and submit with authority wallet...
3. Run the Bot
bash
VAULT_CREATOR=<your-vault-creator-pubkey> SOLANA_RPC_URL=<rpc-url> npx torch-liquidation-bot

On first run, the bot prints the agent keypair and instructions to link it. Link it from your authority wallet, then restart.

4. Configuration
VariableRequiredDefaultDescription
SOLANA_RPC_URLYes--Solana RPC endpoint (HTTPS). Fallback: RPC_URL
VAULT_CREATORYes--Vault creator pubkey
SOLANA_PRIVATE_KEYNo--Disposable controller keypair (base58 or JSON byte array). If omitted, generates fresh keypair on startup (recommended)
SCAN_INTERVAL_MSNo30000Milliseconds between scan cycles (min 5000)
LOG_LEVELNoinfodebug, info, warn, error

Architecture

packages/bot/src/
├── index.ts    — entry point: keypair generation, vault verification, scan loop
├── config.ts   — loadConfig(): validates SOLANA_RPC_URL, VAULT_CREATOR, SOLANA_PRIVATE_KEY, SCAN_INTERVAL_MS, LOG_LEVEL
├── types.ts    — BotConfig, LogLevel interfaces
└── utils.ts    — sol(), bpsToPercent(), withTimeout(), createLogger()

The bot is ~192 lines of TypeScript. It does one thing: find underwater loans and liquidate them through the vault.

Dependencies
PackageVersionPurpose
@solana/web3.js1.98.4Solana RPC, keypair, transaction
torchsdk3.7.22Token queries, bulk loan scanning, liquidation builder, vault queries

Two runtime dependencies. Both pinned to exact versions. No ^ or ~ ranges.


Vault Safety Model

The same seven guarantees from the Torch Market vault apply here:

PropertyGuarantee
Full custodyVault holds all SOL and all collateral tokens. Agent wallet holds nothing.
Closed loopLiquidation SOL comes from vault, collateral tokens go to vault. No leakage to agent.
Authority separationCreator (immutable PDA seed) vs Authority (transferable admin) vs Controller (disposable signer).
One link per walletAgent can only belong to one vault. PDA uniqueness enforces this on-chain.
Permissionless depositsAnyone can top up the vault. Hardware wallet deposits, agent liquidates.
Instant revocationAuthority can unlink the agent at any time. One transaction.
Authority-only withdrawalsOnly the vault authority can withdraw SOL or tokens. The agent cannot extract value.
The Closed Economic Loop for Liquidations
DirectionFlow
SOL outVault → Borrower's treasury debt (covers the loan)
Tokens inBorrower's collateral → Vault ATA (at 10% discount)
NetVault receives collateral worth 110% of SOL spent

The bot is profitable by design — every successful liquidation returns more value than it costs. The profit accumulates in the vault. The authority withdraws when ready.


Lending Parameters

ParameterValue
Max LTV50%
Liquidation Threshold65%
Interest Rate2% per epoch (~weekly)
Liquidation Bonus10%
Utilization Cap70% of treasury
Min Borrow0.1 SOL

Collateral value is calculated from Raydium pool reserves. The 0.03% Token-2022 transfer fee (3 bps, immutable per mint) applies on collateral deposits and withdrawals.

When Liquidations Happen

A loan becomes liquidatable when its LTV exceeds 65%. This happens when:

  • The token price drops (collateral value decreases relative to debt)
  • Interest accrues (debt grows at 2% per epoch)
  • A combination of both

The bot checks position.health === 'liquidatable' — the SDK calculates LTV from on-chain Raydium reserves and the loan's accrued debt.


SDK Functions Used

The bot uses a focused subset of the Torch SDK:

FunctionPurpose
getTokens(connection, { status: 'migrated' })Discover all tokens with active lending markets
getAllLoanPositions(connection, mint)Bulk scan all active loans for a token — returns positions pre-sorted by health (liquidatable first), fetches pool price once
getVault(connection, creator)Verify vault exists on startup
getVaultForWallet(connection, wallet)Verify agent is linked to vault
buildLiquidateTransaction(connection, params)Build the liquidation transaction (vault-routed)
confirmTransaction(connection, sig, wallet)Confirm transaction on-chain via RPC (verifies signer, checks Torch instructions)
Show full SKILL.md (590 more words)Show less
Scan and Liquidate Pattern
typescript
import { getTokens, getAllLoanPositions, buildLiquidateTransaction } from 'torchsdk'

// 1. Discover migrated tokens
const { tokens } = await getTokens(connection, { status: 'migrated', sort: 'volume', limit: 50 })

for (const token of tokens) {
  // 2. Bulk scan — one RPC call per token, positions sorted liquidatable-first
  const { positions } = await getAllLoanPositions(connection, token.mint)

  for (const pos of positions) {
    if (pos.health !== 'liquidatable') break  // pre-sorted, done

    // 3. Build and execute through vault
    const { transaction, message } = await buildLiquidateTransaction(connection, {
      mint: token.mint,           // token with the underwater loan
      liquidator: agentPubkey,    // agent wallet (signer)
      borrower: pos.borrower,     // borrower being liquidated
      vault: vaultCreator,        // vault creator pubkey (SOL from vault, tokens to vault)
    })
    transaction.sign(agentKeypair)
    await connection.sendRawTransaction(transaction.serialize())
  }
}

Log Output

=== torch liquidation bot ===
agent wallet: 7xK9...
vault creator: 4yN2...
scan interval: 30000ms

[09:15:32] INFO  vault found — authority=8cpW...
[09:15:32] INFO  agent wallet linked to vault — starting scan loop
[09:15:32] INFO  treasury: 5.0000 SOL
[09:15:33] INFO  LIQUIDATABLE | SDKTEST | borrower=3AyZ... | LTV=72.50% | owed=0.5000 SOL
[09:15:34] INFO  LIQUIDATED | SDKTEST | borrower=3AyZ... | sig=4vK9... | collateral received at 10% discount

Signing & Key Safety

The vault is the security boundary, not the key.

The agent keypair is generated fresh on every startup with Keypair.generate(). It holds ~0.01 SOL for gas fees. If the key is compromised, the attacker gets:

  • Dust (the gas SOL)
  • Vault access that the authority revokes in one transaction

The agent never needs the authority's private key. The authority never needs the agent's private key. They share a vault, not keys.

Rules
  1. Never ask a user for their private key or seed phrase. The vault authority signs from their own device.
  2. Never log, print, store, or transmit private key material. The agent keypair exists only in runtime memory.
  3. Never embed keys in source code or logs. The agent pubkey is printed — the secret key is never exposed.
  4. Use a secure RPC endpoint. Default to a private RPC provider. Never use an unencrypted HTTP endpoint for mainnet transactions.
RPC Timeout

All SDK calls are wrapped with a 30-second timeout (withTimeout in utils.ts). A hanging or unresponsive RPC endpoint cannot stall the bot indefinitely — the call rejects, the error is caught by the scan loop, and the bot continues to the next token or cycle.

Environment Variables
VariableRequiredPurpose
SOLANA_RPC_URL / RPC_URLYesSolana RPC endpoint (HTTPS)
VAULT_CREATORYesVault creator pubkey — identifies which vault the bot operates through
SOLANA_PRIVATE_KEYNoOptional — if omitted, the bot generates a fresh keypair on startup (recommended)
External Runtime Dependencies

The SDK contains functions that make outbound HTTPS requests to external services. The bot's runtime path contacts two of them:

ServicePurposeWhen CalledBot Uses?
CoinGecko (api.coingecko.com)SOL/USD price for displayToken queries with USD pricingYes — via getTokens(), getToken()
Irys Gateway (gateway.irys.xyz)Token metadata fallback (name, symbol, image)getToken() when on-chain metadata URI points to IrysYes — via getTokens()
SAID Protocol (api.saidprotocol.com)Agent identity verification and trust tier lookupverifySaid() onlyNo — the bot does not call verifySaid()

confirmTransaction() does NOT contact SAID. Despite living in the SDK's said.js module, it only calls connection.getParsedTransaction() (Solana RPC) to verify the transaction succeeded on-chain and determine the event type. No data is sent to any external service.

No credentials are sent to CoinGecko or Irys. All requests are read-only GET. If either service is unreachable, the SDK degrades gracefully. No private key material is ever transmitted to any external endpoint.


Testing

Requires Surfpool running a mainnet fork:

bash
surfpool start --network mainnet --no-tui
pnpm test

Test result: 9 passed, 0 failed (Surfpool mainnet fork).

TestWhat It Validates
ConnectionRPC reachable
getTokensDiscovers migrated tokens
getLendingInfoReads lending state for all tokens
getAllLoanPositionsBulk scans active loans, verifies sort order (liquidatable first)
getTokenToken metadata, price, status
getVaultForWalletVault link returns null for unlinked wallet
In-process keypairNo external key required

Error Codes

  • VAULT_NOT_FOUND: No vault exists for this creator
  • WALLET_NOT_LINKED: Agent wallet is not linked to the vault
  • NOT_LIQUIDATABLE: Position LTV below liquidation threshold
  • NO_ACTIVE_LOAN: No open loan for this wallet/token
  • INVALID_MINT: Token not found


This bot exists because Torch lending markets need keepers. When loans go underwater and nobody liquidates them, the treasury takes the loss. Active liquidation keepers protect treasury health and earn a profit doing it. The vault makes it safe — all value stays in the escrow, all risk is bounded, and the human principal keeps the keys.

© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 21 other files in skills/torchliquidationbot of LeoYeAI/openclaw-master-skills.

  • SKILL.md
  • _meta.json
  • agent.json
  • audit.md
  • design.md
  • lib/kit/config.js
  • lib/kit/index.js
  • lib/kit/types.js
  • lib/kit/utils.js
  • lib/torchsdk/constants.js
  • lib/torchsdk/ephemeral.js
  • lib/torchsdk/gateway.js
  • lib/torchsdk/index.js
  • lib/torchsdk/program.js
  • lib/torchsdk/quotes.js
  • lib/torchsdk/said.js
  • lib/torchsdk/tokens.js
  • lib/torchsdk/torch_market.json
  • … and 4 more

Open the folder on GitHubat commit e5199b5

Compare with similar skills

Torch Liquidation Bot next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Torch Liquidation Bot compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Torch Liquidation Bot this skillLeoYeAI/openclaw-master-skills2.2k—~4.8kAutomated safety check: PassMIT
Swapper Depositswapperfinance/swapper-toolkit852—~1.8kAutomated safety check: PassMIT
Solana Payments Wallets Tradingnpc-live/clawfirm1561 repos~4.7kAutomated safety check: PassMIT
Squadsinternet-court/internet-court-skill6.5k2 repos~5.9kAutomated safety check: PassApache-2.0
Kaminoalsk1992/CloddsBot2.9k—~486Automated safety check: PassMIT
Marginfialsk1992/CloddsBot2.9k—~356Automated safety check: PassMIT

Similar skills

  • Swapper Deposit

    swapperfinance/swapper-toolkit

    Deposit and bridge funds into a wallet or protocol using Swapper Finance.

    852 GitHub stars~1.8k tokensUpdated 6 mo ago
    Business, Finance & HRAuto-check passed
  • Pay people in SOL or USDC, buy and sell tokens, check prices, discover trending and new tokens, create and manage Solana wallets, stake SOL, earn yield through lending and managed vaults, borrow…

    156 GitHub starsUsed in 1 repo~4.7k tokens
    Business, Finance & HRAuto-check passed
  • Squads

    internet-court/internet-court-skill

    Complete guide for Squads Protocol - Solana's leading smart account and multisig infrastructure.

    6.5k GitHub starsUsed in 2 repos~5.9k tokens
    Business, Finance & HRAuto-check passed
  • Kamino

    alsk1992/CloddsBot

    Kamino Finance — Solana lending, borrowing, and liquidity vaults

    2.9k GitHub stars~486 tokensUpdated 7 days ago
    Business, Finance & HRAuto-check passed
  • Marginfi

    alsk1992/CloddsBot

    MarginFi — Solana lending and borrowing

    2.9k GitHub stars~356 tokensUpdated 7 days ago
    Business, Finance & HRAuto-check passed
  • Solend

    alsk1992/CloddsBot

    Solend — Solana lending and borrowing

    2.9k GitHub stars~378 tokensUpdated 7 days ago
    Business, Finance & HRAuto-check passed

More from LeoYeAI/openclaw-master-skills

All 1,235 skills in this repo
  • DevOps Pipeline Management

    LeoYeAI/openclaw-master-skills

    Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.

    2.2k GitHub stars~4.2k tokensUpdated 2 mo ago
    Auto-check: notes
  • Feishu Document Collaboration

    LeoYeAI/openclaw-master-skills

    Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.

    2.2k GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed
  • Files Memory System

    LeoYeAI/openclaw-master-skills

    Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.

    2.2k GitHub stars~3.8k tokensUpdated 2 mo ago
    Auto-check passed
  • GEO-Claw AI Visibility Agent

    LeoYeAI/openclaw-master-skills

    Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.

    2.2k GitHub stars~4.7k tokensUpdated 2 mo ago
    Auto-check passed
  • Google Workspace CLI

    LeoYeAI/openclaw-master-skills

    Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.

    2.2k GitHub stars~2.6k tokensUpdated 2 mo ago
    Auto-check: notes
  • HealthFit Health Advisors

    LeoYeAI/openclaw-master-skills

    Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.

    2.2k GitHub stars~4.4k tokensUpdated 2 mo ago
    Auto-check passed

Works with

Questions about Torch Liquidation Bot

What does Torch Liquidation Bot do?

Autonomous vault-based liquidation keeper for Torch Market lending on Solana. Torch Liquidation Bot is an agent skill from LeoYeAI/openclaw-master-skills. Autonomous vault-based liquidation keeper for Torch Market lending on Solana.

When should I use Torch Liquidation Bot?

Torch Liquidation Bot fits situations like: tasks that involve Banking and insurance.

How do I install Torch Liquidation Bot in Claude Code?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill torch-liquidation-bot -a claude-code`. Or copy the skill folder (skills/torchliquidationbot in LeoYeAI/openclaw-master-skills) into .claude/skills/torch-liquidation-bot in your project. Claude Code loads it when a task matches its description.

How do I install Torch Liquidation Bot in Codex?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill torch-liquidation-bot -a codex`. Or copy the skill folder (skills/torchliquidationbot in LeoYeAI/openclaw-master-skills) into .agents/skills/torch-liquidation-bot in your project. Codex loads it when a task matches its description.

Can I use Torch Liquidation Bot in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill torch-liquidation-bot -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/torch-liquidation-bot, .gemini/skills/torch-liquidation-bot, .github/skills/torch-liquidation-bot and .opencode/skills/torch-liquidation-bot in your project.

What does Torch Liquidation Bot need to run?

Going by SKILL.md and its folder, Torch Liquidation Bot needs JavaScript for the scripts in its folder, the command-line tools its instructions call (npm, npx, vault and pnpm) and credentials named SOLANA_PRIVATE_KEY. Our summary lists: Node.js; A credential in SOLANA_PRIVATE_KEY. Compatibility (from SKILL.md): REQUIRED: SOLANA_RPC_URL (HTTPS Solana RPC endpoint) REQUIRED: VAULT_CREATOR (vault creator pubkey). OPTIONAL: SOLANA_PRIVATE_KEY -- the bot generates a fresh disposable keypair in-process if not provided. The agent wallet holds nothing of value (~0.01 SOL for gas). All liquidation proceeds (collateral tokens) route to the vault. The vault can be created and funded entirely by the human principal. This skill sets disable-model-invocation: true -- it must not be invoked autonomously without explicit user initiation. The Torch SDK is bundled in lib/torchsdk/ -- all source included for full auditability. No API server dependency. The vault can be created and funded entirely by the human principal -- the agent never needs access to funds..

Does Torch Liquidation Bot access the network?

SKILL.md names 4 domains. As links in the text: github.com, torch.market, npmjs.com and clawhub.ai. This is read from the text; nothing was executed.

Is Torch Liquidation Bot safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Torch Liquidation Bot use?

Torch Liquidation Bot is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Torch Liquidation Bot use?

About 4.8k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Torch Liquidation Bot?

Skills that share tags, products or a category with Torch Liquidation Bot: Swapper Deposit (swapperfinance/swapper-toolkit, 852 stars), Solana Payments Wallets Trading (npc-live/clawfirm, 156 stars), Squads (internet-court/internet-court-skill, 6.5k stars) and Kamino (alsk1992/CloddsBot, 2.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Torch Liquidation Bot?

LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,160 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.

Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.