kxmeta-discover

Probes kdb+ process discovery metadata via /meta HTTP route and qIPC fallbacks.

12|11|Updated May 20, 2026
One-click install
npx skills add https://github.com/KxSystems/kx-skills --skill kxmeta-discover
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kxmeta-discover
Source: https://github.com/KxSystems/kx-skills/tree/main/plugins/kdbx-knowledge/skills/kxmeta-discover
Command: npx skills add https://github.com/KxSystems/kx-skills --skill kxmeta-discover

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discovering metadata on a running kdb+ process using aimeta — cold-start probing, the /meta HTTP route, kx-meta discover, qIPC fallback, and reading the tier / references[] fields in the response. This enables an agent to learn what tables and functions a kdb+ host exposes, interpret kx-meta discover outputs, handle tier-1 fallbacks gracefully, and walk references[] for vocabulary resolution. For the wire model and full meta.json shape see ../../reference/agent-guide.md.

Core Features & Use Cases

  • Probe HTTP /meta surface to determine aimeta presence and tier.
  • Fall back to tier 2 (qIPC) and tier 1 (native introspection) when HTTP is unavailable.
  • Resolve vocabulary via references[] to map terms to underlying entities.

Quick Start

Run the kx-meta discover host:port to retrieve tiered metadata from a kdb+ process.

Frequently Asked Questions about kxmeta-discover

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I discover kdb+ metadata and exposed tables on a running process?

To discover kdb+ metadata, probe the HTTP /meta route to fetch tiered metadata from the running process. This action retrieves exposed tables and functions while determining the aimeta presence and tier level.

What does the references[] field mean in kdb+ discovery metadata?

The references[] field in kdb+ discovery metadata maps vocabulary terms to underlying entities. Walking references[] enables agents to resolve domain vocabulary and interpret the exposed tables and functions accurately.

How do I fetch kdb+ metadata when the HTTP /meta route is unavailable?

When the HTTP /meta route is unavailable, fetch kdb+ metadata by falling back to tier 2 qIPC connections. If qIPC fails, tier 1 native introspection provides a final fallback to learn exposed tables and functions.

What is the meta.json wire model used for in kdb+ agent integrations?

The meta.json wire model defines the tiered metadata shape and references[] semantics for kdb+ agent integrations. It provides the structure agents need to interpret discovery outputs and handle tier-1 fallbacks gracefully.

Can I use kx-meta discover to probe a kdb+ host without prior configuration?

Yes, you can run kx-meta discover host:port to retrieve tiered metadata from a kdb+ process. This probes the running host directly, checking aimeta presence and executing fallbacks without prior configuration.