8 skills · sorted by relevance
Develop Starknet apps with starknet.js v9.x using examples for contract calls, account management, wallet connections, and transaction handling. It also covers transaction simulation, fee estimates, and paymasters, services that sponsor fees or accept alternative tokens.
Execute token swaps, recurring purchases, and STRK staking on Starknet. Use avnu to obtain swap quotes, check prices and rewards, and pay transaction fees in a supported token through its paymaster service.
Create and operate Starknet wallets for AI agents. Check token balances, send transfers, interact with smart contracts, and manage session keys, temporary permissions that let an agent perform approved transactions within spending limits and an expiry time.
Review Cairo smart contracts on StarkNet for six vulnerability patterns involving arithmetic, cross-layer messages, addresses, and signature reuse. Receive a coverage table with evidence for every pattern, plus severity ratings and fixes for identified issues.
Register AI agents on Starknet as NFTs, unique digital ownership records, using ERC-8004. Manage agent details, collect authorized feedback, and request or review third-party assessments through the standard’s identity, reputation, and validation registries.
Specific rules for Starknet React projects, focusing on blockchain integration.
The English summary is being prepared. Showing the original description.
Scans Cairo/StarkNet smart contracts for 6 critical vulnerabilities including felt252 arithmetic overflow, L1-L2 messaging issues, address conversion problems, and signature replay. Use when auditing StarkNet projects. (project, gitignored)
The English summary is being prepared. Showing the original description.
Preflight that resolves which private key(s) to use for the warp-deploy chain across every protocol in the route (EVM / Sealevel / Cosmos / Starknet / Tron). For each protocol the user supplies either a specific key spec (GCP secret name, env var, or keystore path) or a candidate list of GCP secret names for the agent to surface and the user to pick. The agent never enumerates GCP secrets on its own and never reads secret values without an explicit user-approved pick. Persists the resolution to `~/.hyperlane/key-contexts/ticket-id.yaml` for downstream warp-deploy skills to auto-load.
The English summary is being prepared. Showing the original description.