Viking App Dataset Bind

When to Use

Use this skill when the user wants to run vs app dataset bind and the bind step is responsible for inferring and confirming application-facing field settings instead of blindly reusing or omitting them.

Preconditions

• an application-id and a dataset-id are available
• you can access enough representative dataset context to infer bind-time field config
• prefer an existing plan directory or raw source file when available, because the inference prompts need Dataset_Description, Data, and Meaning
• schema and dataset-side field attributes have already been shown to the user and explicitly reconfirmed before bind-time inference starts
• do not assume the dataset-creation field-config.json already contains bind-time fields such as IndexFields, FilterFields, SuggestFields, ImageIndexFields, or VideoIndexFields
• if pulled dataset metadata already contains IndexFields, FilterFields, SuggestFields, ImageIndexFields, or VideoIndexFields, treat them as legacy/non-standard unless a human reviewer explicitly validates them

Commands