Query and Skill context

Query and Skill are declared graph node kinds, but the current default Studio compiler does not assign a standalone execution tool to either. Do not add one and assume it performs a query or calls an agent merely because the canvas accepts that kind.

Query

A Query node's serialized section is query: {}. It represents query context. Published ontology queries have their own authoring, release, binding and execution interfaces; use those supported workflows or an implemented transform/tool path when actual reads are needed.

Skill

A Skill node carries skillIds and one mode: authoring-assist, execution-assist or validation-assist. These identify guidance/context; they are not proof of a default execution step. Nodes can also attach skills through attachedSkillIds.

Attach the existing data-quality guidance skill to the relevant pipeline authoring context. Explain where that guidance is consumed and which installed executable node performs the actual data checks. Do not represent the skill itself as an executable transform.

{
  "skillIds": [
    "<EXISTING_SKILL_UUID>"
  ],
  "mode": "authoring-assist"
}

Inspect that the referenced skill actually exists and its contents apply to the task. A new skill name does not create a transform implementation, permission or source binding. Check the supported authoring/validation/runtime use of the guidance before relying on it.