# Execute Starknet DeFi Transactions

Starknet DeFi workflows often require separate knowledge of quotes, protocols, recurring orders, and account configuration. This skill provides practical AVNU-based examples for swaps, DCA, staking, lending, and market data.

## Install

```bash
npx skillstore add internet-court/starknet-defi
```

## Metadata

- Status: approved
- Slug: internet-court-starknet-defi
- Version: 1.0.0
- Author version: 1.0.0
- Skillstore revision: r2
- Version status: not\_bumped
- Tree hash: f4a505eee1311d1f8e131fd0965f6ec1262fd14b299f237490aed58d9c38fd78
- Author: internet-court
- GitHub username: internet-court
- License: Apache-2.0
- Repository: https://github.com/internet-court/internet-court-skill/tree/main/vendored/starknet/starknet-defi
- Ref: 1c2ebded2116f8124f45dba86a2e567f56e64d8e
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, filesystem, env\_access
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/internet-court-starknet-defi
- Manifest: https://skillstore.pages.dev/api/skills/internet-court-starknet-defi/manifest

## Capabilities

- Build AVNU quote requests and execute token swaps with configurable slippage.
- Create, inspect, and cancel AVNU dollar-cost averaging orders.
- Start staking, claim rewards, compound rewards, and complete unstaking flows.
- Query verified token data, prices, routes, fees, and price impact.
- Configure Starknet RPC, AVNU API, and paymaster endpoints for mainnet or Sepolia.

## Use Cases

- Swap Tokens on Starknet: Get a verified token quote, compare route and fee data, then prepare an AVNU swap with a stated slippage limit.
- Set Up Recurring Buys: Define token amounts, order count, frequency, and start time for an AVNU DCA order, then review cancellation steps.
- Manage Staking Positions: Review staking pool information, stake STRK, inspect rewards, claim or compound them, and follow the unstaking cooldown.

## Prompt Templates

### Explain a Starknet Swap

```
Explain how to request an AVNU quote for swapping ETH to STRK. List the inputs, checks, fees, and user confirmations required before signing.
```

### Plan a DCA Order

```
Create a review checklist for a 100 USDC to STRK DCA order split across ten daily purchases. Include amount, frequency, start time, and cancellation checks.
```

### Review Staking Actions

```
Compare the documented STRK staking, reward claiming, compounding, and unstaking steps. Identify every state-changing action and the confirmation needed before it.
```

### Design a Controlled Execution Flow

```
Design a Starknet DeFi execution workflow using AVNU quotes and paymaster support. Add token verification, quote expiry, slippage limits, simulation, private-key isolation, and explicit approval before signing.
```

## Limitations

- It does not manage private keys, create wallets, or provide custody.
- It does not guarantee token prices, liquidity, transaction success, or protocol safety.
- It does not replace user confirmation, transaction simulation, or financial advice.
- Lending and borrowing guidance is limited to the documented protocol references.

## Best Practices

- Verify token addresses, protocol endpoints, quote freshness, fees, price impact, and slippage before signing.
- Use a hardware wallet or external signer, and keep private keys outside agent-readable files and logs.
- Test on Sepolia first, set strict amount limits, and require explicit confirmation for every state-changing action.

## Anti Patterns

- Never paste a Starknet private key into chat, source code, logs, or an unprotected environment.
- Do not approve or execute a swap without checking the token addresses, recipient, route, amount, and slippage.
- Do not create recurring orders or compound rewards without reviewing duration, total exposure, fees, and cancellation steps.

## Security Audit

- Audited at: 2026-08-07T08:53:15.804\+00:00
- Summary: The static catalog is mostly false positive noise from Markdown fences, documentation URLs, configuration examples, and a relative documentation link. The required signing key is a genuine high-risk credential, and the transaction examples lack an explicit confirmation and safety-control layer.

## Stats

- Views: 0
- Downloads: 5
- Favorites: 1
- Popularity score: 0