kibana-clilisted

# Kibana CLI Skill Use the instance and rules below when constructing all Kibana API commands. ## Instances Update the table below with your Kibana instance URLs and corresponding credential file paths: | Environment | Base URL | Credential File | |---|---|---| | Production | `https://<your-kibana-prod-url>` | `~/.kibana/prod.token` | | Staging | `https://<your-kibana-staging-url>` | `~/.kibana/staging.token` | If the target instance is unclear, ask the user before running any command. ## Prerequisites (one-time setup by user) Generate a Kibana API key for each instance you intend to use and save it to the corresponding credential file (see instance table above). Never print or display credential values. Do not perform these steps yourself. ```bash mkdir -p ~/.kibana && echo "<your-api-key>" > <CREDENTIAL_FILE> && chmod 600 <CREDENTIAL_FILE> ``` ## Command Format All API calls use `curl` with the API key read from the instance's credential file, and always require the `kbn-xsrf` header: ```bash curl -s -H "Authorization: ApiKey $(cat <CREDENTIAL_FILE>)" \ -H "kbn-xsrf: true" \ "<BASE_URL>/api/<endpoint>" | jq . ``` Example (production): ```bash curl -s -H "Authorization: ApiKey $(cat ~/.kibana/prod.token)" \ -H "kbn-xsrf: true" \ "https://<your-kibana-prod-url>/api/status" | jq . ``` ## Available API Endpoints ### Read-only (safe, no confirmation needed) | Endpoint | Method | Description | |---|---|---| | `/api/status` | GET | Check Kibana health/status