zerodha-kite-cli-router
Route natural-language trading/account queries to the correct `zerodha` CLI command with exact flags, validation constraints, and synonym mapping. Use when a user asks to view prices, place/modify/cancel orders, manage auth/profile/config, work with holdings/positions/margins/GTT/MF flows, or asks "which zerodha command should I run?"
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/jatinbansal1998/zerodha-kitePurpose
Translate a user query in plain English into one exact zerodha CLI command.
Do not invent commands or flags. Use only commands defined here.
Bootstrap: CLI Installation
If the user asks to install/setup the CLI, or reports zerodha: command not found, route to an installer command first.
This is the only exception to "commands must start with zerodha".
Install commands:
- Linux/macOS (
curl):curl -fsSL https://raw.githubusercontent.com/jatinbansal1998/zerodha-kite-cli/main/scripts/install.sh | sh - Linux/macOS (
wget):wget -qO- https://raw.githubusercontent.com/jatinbansal1998/zerodha-kite-cli/main/scripts/install.sh | sh - Windows PowerShell:
irm https://raw.githubusercontent.com/jatinbansal1998/zerodha-kite-cli/main/scripts/install.ps1 | iex - Windows CMD:
powershell -NoProfile -ExecutionPolicy Bypass -Command "irm https://raw.githubusercontent.com/jatinbansal1998/zerodha-kite-cli/main/scripts/install.ps1 | iex"
Post-install verification command:
zerodha version
Global Rules
- Always start commands with
zerodha(except install/bootstrap commands in "Bootstrap: CLI Installation"). - Prefer
--jsonwhen the user asks for machine-readable output. - Respect global flags when provided:
--profile <name>--config <path>--json--debug
- Profile selection:
- Most commands require an active profile (or explicit
--profile). - If no profile is selected, use:
zerodha config profile use <name>
- Most commands require an active profile (or explicit
- Auth/session:
- API data/order commands require an access token.
- If missing, run
zerodha auth login .... - CLI auto-refreshes access token when refresh token exists.
- Never guess missing required fields for write actions; ask for the missing values.
- If OS is required for installation routing and missing, ask for only the OS (
linux,macos, orwindows).
Login Flow (Multi-Message)
Use this flow when the user wants to authenticate and provides api_key, api_secret, and token across one or more messages.
Collected auth fields (can arrive in any order):
profile_name(default todefaultif user does not specify)api_keyapi_secret- one login mode:
request_token_or_redirect_url, orcallback(optionalcallback_port)
Rules:
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-jatinbansal1998-zerodha-kite": {
"enabled": true,
"auto_update": true
}
}
}