Install any skill in seconds. Free to start, no credit card required.
Get Started Free →internet-court/genlayer-cli
Use the GenLayer CLI to deploy, interact with, and debug intelligent contracts.
Passed 20 of 22 test cases with the skill, and 3 of 22 without it.
and 26 more in the full report
18 fixed2 passed either way1 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 18 test cases the skill fixed. Same model, same prompt, with and without the skill.
I have a contract in contracts/token.py that requires an initial supply integer of 1000 and an owner string address '0x123'. What is the exact GenLayer CLI command to deploy this specific contract with those arguments?
| Checked | Without skill | With skill |
|---|---|---|
| Uses genlayer deploy with --contract contracts/token.py. | Missed | Passed |
| Passes positional parameters following the --args flag. | Passed | Passed |
The instructions your model reads when the skill loads.
The genlayer CLI manages contract deployment, interaction, transaction inspection, and network configuration. Works with GenLayer Studio (local), studio.genlayer.com, and Testnet Bradbury.
npm install -g genlayer
genlayer network set # Interactive selector
genlayer network set testnet-bradbury # Direct
genlayer network info # Show current network config
genlayer network list # List all networks
Networks: localnet, studionet, testnet-asimov, testnet-bradbury
Note: studionet is gasless — no tokens are required to deploy or interact with contracts. A 0 GEN balance is expected and does not prevent any operations.
Note: studionet is rate-limited per IP — 60 req/min, 1000 req/hr, 10000 req/day. Limits aren't permanent — batching many deploy/write calls trips -32429 / HTTP 429 and further requests are rejected until the window resets (next minute / hour / day cycle). -32028 signals the pending-queue cap — up to 32 in-flight txs per sender; a separate cap also applies per contract. Throttle batch scripts, wait for receipts between submissions, or use localnet for heavy batches.
Always use genlayer network set instead of --rpc for built-in networks. The --rpc flag bypasses the chain configuration (consensus contract ABI, isStudio flag, etc.) and will cause transaction polling failures. Only use --rpc for custom/private networks not in the built-in list.
genlayer account # Show active account (address, balance, network)
genlayer account list # List all accounts
genlayer account create --name dev1 # Create new account
genlayer account use dev1 # Set active account
genlayer account unlock # Cache key in OS keychain (no password prompts)
genlayer account lock # Remove from keychain
# Import from private key or keystore
genlayer account import --name imported --private-key 0x...
genlayer account import --name imported --keystore ./keystore.json
test cases passed, vs 3 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.