StableOps Treasury

Use this skill when a team, DAO, or builder wants to deploy USDC from a stablecoin treasury into LI.FI Earn vaults under explicit treasury policy limits, pre...

Security Scan

The skill's instructions, required resources, and scope are coherent with its stated purpose (governed USDC treasury deployment into LI.FI Earn via Composer); it is instruction-only, requests no credentials, and has no installers, but it depends on a local StableOps service and a connected treasury wallet to function.

Purpose & Capability

The name/description (deploying treasury USDC into LI.FI Earn vaults with Composer) matches the runtime instructions: extracting a treasury policy, building a plan, querying a local plan/quote API, preparing a Composer quote, and producing a report. No unrelated credentials, binaries, or installs are requested.

Instruction Scope

Instructions are narrowly focused on treasury policy, vault discovery, Composer quotes, execution, and reporting. They tell the agent to POST to a local service at http://localhost:3017 and to instruct the user/operator to connect and approve a treasury wallet for transaction signing. This assumes a local StableOps backend and an external signing flow; the skill does not instruct the agent to access files, secrets, or external endpoints beyond localhost.

Install Mechanism

No install spec or code files are present (instruction-only), so nothing is written to disk or fetched at install time. Lowest-risk install behavior.

Credentials

The skill declares no required environment variables, credentials, or config paths. The actions described (wallet connection and on-chain transaction submission) are consistent with the stated purpose and do not require the skill to request unrelated secrets.

Persistence & Privilege

always is false and there is no install-time persistence. The included agents/openai.yaml sets allow_implicit_invocation: true which permits autonomous invocation by the platform; this is a normal setting for skills and not by itself disproportionate. The skill does not request modifications to other skills or system-wide settings.

Assessment

This skill is instruction-only and coherent with its described purpose, but it requires a local StableOps service listening on http://localhost:3017 and a connected treasury wallet to actually perform actions. Before installing or invoking: (1) confirm you run and trust the local StableOps backend referenced by the curl examples (the skill will POST to localhost); (2) never provide private keys or paste secret material into the agent—use an external wallet signer or hardware wallet for transaction signing; (3) review prepared Composer quotes and on-chain transactions before approving or broadcasting; (4) be aware the skill can be invoked automatically by the agent (allow_implicit_invocation), so decide whether to restrict autonomous execution in your agent settings if you want manual oversight.

StableOps LI.FI Treasury

Use this skill for governed treasury execution powered by LI.FI Earn and Composer.

StableOps is for small teams, DAOs, and indie builders. It should not be framed as a personal wallet yield helper. The workflow starts from treasury rules and only then moves to vault discovery and Composer execution.

When To Use

• The user wants to manage a team, DAO, builder, or stablecoin treasury.
• The user gives rules like reserve target, max per execution, allowed chains, safe vaults only, or minimum TVL.
• The user wants to deploy USDC into an Earn vault with a policy-backed explanation.
• The user wants a report describing vault, protocol, chain, transaction hash, and receipt token.

Example requests:

Use StableOps to deploy 1 USDC from our team treasury into a safe LI.FI Earn vault on Base.
Run a treasury policy check: keep 60% reserve, max 5 USDC per execution, Base or Arbitrum only.
Prepare a Composer deposit for our builder treasury and explain the receipt token after execution.

Workflow

1. Extract the treasury policy:

   • treasury name
   • treasury size in USDC
   • deploy amount in USDC
   • reserve target
   • max per execution
   • allowed chains
   • risk mode
   • minimum TVL

2. Build a StableOps plan:

curl -sS -X POST http://localhost:3017/api/plan \
  -H 'Content-Type: application/json' \
  -d '{
    "policy": {
      "treasuryName": "Builder Treasury",
      "treasurySizeUsd": 100,
      "deployAmountUsd": 1,
      "reservePct": 60,
      "maxPerExecutionUsd": 5,
      "minTvlUsd": 5000000,
      "riskMode": "conservative",
      "allowedChainIds": [8453, 42161]
    }
  }'

3. Use the returned plan fields:

   • recommendedVault
   • approvedVaults
   • rejectedVaults
   • checks
   • agents
   • reportPreview

4. Only prepare Composer quote when all blocking checks pass:

curl -sS -X POST http://localhost:3017/api/quote \
  -H 'Content-Type: application/json' \
  -d '{
    "chainId": 8453,
    "vaultAddress": "<vault-address>",
    "walletAddress": "<treasury-wallet>",
    "fromAmountUsd": 1,
    "fromTokenAddress": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "assetDecimals": 6
  }'

5. For execution:

   • connect the treasury wallet
   • switch to the selected chain
   • approve USDC if required
   • submit the Composer transaction
   • wait for confirmation

6. After execution, return a treasury report:

   • deployed amount
   • vault name
   • protocol
   • chain
   • deposit transaction hash
   • receipt token symbol
   • plain-language explanation of what the receipt token represents

Output Rules

• Lead with the treasury decision: approved or blocked.
• Mention policy checks before APY.
• Do not recommend a vault that fails the policy.
• Do not create a Composer quote if reserve, max execution, chain, TVL, or Composer support fails.
• Explain receipt tokens plainly: a receipt token represents the treasury's position in the selected vault.
• If live LI.FI Earn discovery is unavailable, say that seeded examples are being used.