Kong/ai-marketplace / plugins/kong-konnect/skills/kongctl-query
kongctl-query
VerifiedUse when the user wants read-only `kongctl` queries against Konnect: prove auth or scope, discover the right `get` path, list or fetch resources, or shape JSON/YAML output. Do not use for `kongctl` plan/apply/sync or declarative authoring.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.3 KB |
| references/auth-and-scope-checks.md | markdown | 1.7 KB |
| references/output-shaping.md | markdown | 1.9 KB |
| references/resource-discovery.md | markdown | 1.7 KB |
references/output-shaping.md
View on GitHub# Output Shaping
Use this file when the main problem is how to return read results cleanly.
## Core Rule
Prefer structured output for inspection, then summarize only the fields the
user actually needs.
## Defaults
- use JSON unless YAML is explicitly requested
- use explicit `-o json` or `-o yaml` to avoid profile/env surprises
- summarize IDs, names, states, timestamps, and the minimum fields needed to
answer the question
Use `text` output only when the user explicitly wants it and no `--jq` filter
is involved.
## Decision Rules
- If the user wants machine-shaped results, preserve structure.
- If the user wants a concise explanation, summarize after inspection instead
of switching to text-mode guessing.
- If the result is large, filter conceptually in the response even if the CLI
output is structured and verbose.
## `--jq` Use
- Use `--jq <expression>` on `get` queries when shaping the response is cheaper
than post-processing in prose.
- Keep `-o json` or `-o yaml` explicit when `--jq` is present.
- Quote the expression with single quotes to avoid shell parsing surprises.
- If `kongctl` reports that `--jq` only works with JSON or YAML output, rerun
the same command with `-o json` before changing anything else.
Minimal examples:
```bash
kongctl get portals -o json --jq 'map({id, name, display_name})'
kongctl get me -o json --jq '{id, email}'
```
## Profile and Environment Overrides
- Profile config and `KONGCTL_*` environment variables can change default
output behavior.
- When formatting is surprising, inspect override names only; never print
variable values or read credential files. Use explicit flags to prove behavior.
Useful checks:
```bash
env | grep -o '^KONGCTL_[A-Z0-9_]*' | grep -E 'OUTPUT|^KONGCTL_PROFILE$'
```
## What To Return
Return:
- the output format used
- the key fields that answer the question
- any profile/env caveat that may have affected formatting
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |