kxmeta-author

Write aimeta annotations with mandatory @kind and @name markers for q codebases.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams write correct aimeta annotations so the compiler can publish tables and functions reliably.

Core Features & Use Cases

  • Enforces mandatory / @kind and / @name markers on every annotated item.
  • Guides use of chained @col modifiers and explains common qdoc traps that cause silent drops.
  • Provides diagnostics for items missing from meta.json and guidance to trigger recompile loops.

Quick Start

Use this skill to fix aimeta annotations so items appear in meta.json after a code change.

Frequently Asked Questions about kxmeta-author

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

FAQPage Schema
Why are my aimeta annotated items missing from meta.json after a q codebase recompile?

Items go missing from meta.json when aimeta annotations lack mandatory @kind and @name markers. You must enforce these required markers and address common qdoc traps that cause silent drops, then trigger a successful recompile to surface the items.

How do I write correct aimeta annotations to publish tables and functions in kdbx?

To write correct aimeta annotations for kdbx, apply mandatory @kind and @name markers on every annotated item. Use chained @col modifiers correctly to define columns, and avoid common qdoc traps that prevent the compiler from publishing tables and functions reliably.

What qdoc traps cause aimeta annotations to silently drop during compilation?

Common qdoc traps include omitting mandatory @kind or @name markers, and misusing chained @col modifiers. These mistakes cause the compiler to silently drop annotated items instead of publishing them to meta.json, requiring diagnostics and a recompile to fix.

Do I need both @kind and @name markers for every aimeta annotation?

Yes, @kind and @name are mandatory markers required on every aimeta annotation. Without both markers, the compiler fails to surface the annotated tables and functions in meta.json, resulting in silent drops during the build process.

How do I use chained @col modifiers in aimeta annotations?

Chained @col modifiers guide the definition of table columns within aimeta annotations. Correct usage ensures the compiler properly processes and publishes the table structure to meta.json, while misuse leads to common qdoc traps and missing items.

What is the best way to diagnose aimeta items failing to surface in meta.json?

The best way to diagnose missing aimeta items is to check for missing mandatory @kind and @name markers, verify chained @col modifiers, and identify common qdoc traps. Apply fixes and trigger a recompile loop to ensure items successfully surface in meta.json.