Guandata CLI Suite

Problem

Guandata BI work spans datasources, ETL, datasets, pages, cards, metrics, and workflows. Web UI troubleshooting lacks context, while ad hoc scripts easily miss ID references, permissions, schedules, and recycle-bin differences. This skill routes common CLI tasks to the right official components, keeping engineers inside explicit task boundaries for query, modification, and validation.

How It Works

• Capability routing: use guancli for query/analysis and form data, guands for datasource/dataset write operations and form structure, guanetl for ETL, guanvis for visualization and page directories, guanmetric for metrics, and guanwf for workflows.
• Execution order: determine whether the user wants capability info, setup, or a concrete task; check that the target component is available; then follow the target skill's rules for query, preview, confirmation, save, publish, and validation.
• Key constraint: prefer in-place updates when editing/renaming existing BI resources; use page commands for page rename/move and directory commands for directories; avoid simulating edits by deleting and recreating resources.
• Deletion semantics: page deletion may be soft delete, but CLI may not provide restore; directory deletion can be physical and require empty directories, so impacts must be explicit before running it.

Boundaries

Useful for engineering workflows that operate Guandata BI resources, orchestrate cross-component tasks, and validate production objects. Do not rely on it to restore every deleted object, and do not force delete-recreate when in-place update is unavailable. Some constraints, such as dataset directory moves, must be handled in the web UI.