InjectiveLabsInjectiveLabs/agent-skills/skills/injective-trading-staking/SKILL.md

injective-trading-staking

Skill6 starsChanged 4 months agoApache-2.0View on GitHub

Query and manage Injective staking delegations, rewards, and validator info. Look up staker addresses, delegation amounts, unbonding status, and claimed rewards via Injective LCD/REST API.

In this repository20 other files it gives its agents.
- injective-ai-cost-optimizationSkill
- injective-cliSkill
- injective-core-detect-changesSkill
- injective-docs-styleSkill
- injective-evm-developerSkill
- injective-faucetSkill
- injective-frontend-walletSkill
- injective-fundingSkill
- injective-mcp-serversSkill
- injective-rfq-integrationsSkill
- injective-trading-accountSkill
- injective-trading-autosignSkill
- injective-trading-bridgeSkill
- injective-trading-chain-analysisSkill
- injective-trading-frontend-uxSkill
- injective-trading-market-dataSkill
- injective-trading-tokensSkill
- injective-usdc-integrationSkill
- injective-wallet-opsSkill
- linear-cliSkill

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
All endpoints use Injective LCD REST API:
line 27
Very specific:
All amounts in inj denom use 1e18 (like ETH wei)
line 35
Very specific:
Must be claimed via MsgWithdrawDelegatorReward.
line 39
Very specific:
Check signing_infos for validator jail status
line 45
Distinctive:
Use the archival node endpoints for historical queries:
line 115

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Injective Trading Staking, Skill Guide

Query Injective staking data via LCD REST API. Covers delegations, rewards, validators, and unbonding. Useful for treasury dashboards, staker audits, and validator monitoring.

When to apply

Sample prompts: ./references/sample-prompts.md

Important

Endpoints

All endpoints use Injective LCD REST API:

Mainnet: https://lcd.injective.network
Testnet: https://testnet.sentry.lcd.injective.network:443

Key Facts

Decimals:
- All amounts in inj denom use 1e18 (like ETH wei)
Unbonding period:
- 21 days on Injective mainnet
Rewards:
- Must be claimed via MsgWithdrawDelegatorReward.
- Track claimed vs accrued separately
Delegation shares:
- Not 1:1 with tokens.
- Use validator.tokens / validator.delegator_shares ratio
Slashing:
- Check signing_infos for validator jail status

Activities

Query Delegations for an Address

GET /cosmos/staking/v1beta1/delegations/{delegator_addr}

Returns all active delegations with validator address and shares.

Query Delegation to Specific Validator

GET /cosmos/staking/v1beta1/validators/{validator_addr}/delegations/{delegator_addr}

Query Unbonding Delegations

GET /cosmos/staking/v1beta1/delegators/{delegator_addr}/unbonding_delegations

Query Staking Rewards

GET /cosmos/distribution/v1beta1/delegators/{delegator_addr}/rewards

Returns pending (unclaimed) rewards per validator and total.

Query Validators

GET /cosmos/staking/v1beta1/validators?status=BOND_STATUS_BONDED&pagination.limit=100

Query Single Validator

GET /cosmos/staking/v1beta1/validators/{validator_addr}

Query Staking Parameters

GET /cosmos/staking/v1beta1/params

Returns unbonding time, max validators, bond denom (inj).

Check pending rewards

GET "https://lcd.injective.network/cosmos/distribution/v1beta1/delegators/inj1.../rewards"

Check total staked INJ for a wallet

curl -s "https://lcd.injective.network/cosmos/staking/v1beta1/delegations/inj1..." | python3 -c "
import json, sys
data = json.load(sys.stdin)
total = sum(int(d['balance']['amount']) for d in data.get('delegation_responses', []))
print(f'{total / 1e18:.2f} INJ staked')
"

Find all stakers with > N INJ delegated

Use the archival node endpoints for historical queries:

Tendermint RPC: https://tm.injective.network:443
LCD REST: https://lcd.injective.network
gRPC: grpc.injective.network:443

Query validators first. Then iterate delegations per validator. Note: Pagination required (default limit 100).

Get delegations

This uses the injective-py SDK.

from pyinjective.async_client import AsyncClient
from pyinjective.core.network import Network

async def get_delegations(address: str):
    network = Network.mainnet()
    client = AsyncClient(network)
    delegations = await client.fetch_delegations(delegator_addr=address)
    return delegations

Related skills

None

Prerequisites

curl installed
for some of these actions: python installed

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free