dorado

Query Dorado DataLeap projects, batch tasks, and execute temporary SQL across regions.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/yuezhen-huang/my-bytedance-skillhub --skill dorado-yuezhen-huang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dorado
Source: https://github.com/yuezhen-huang/my-bytedance-skillhub/tree/main/dorado
Command: npx skills add https://github.com/yuezhen-huang/my-bytedance-skillhub --skill dorado-yuezhen-huang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It removes the need to manually navigate the Dorado (DataLeap) web console when you need to look up projects, inspect batch tasks, check yarn queue resources, or run ad-hoc SQL queries across multiple regions. ## Core Features & Use Cases - Project and Task Lookup: List projects, list or search batch tasks, and retrieve individual task metadata by task_id in regions like cn, sg, gcp, va, boe, and boei18n. - Temporary SQL Execution: Run debug SQL through an existing Dorado temporary-query task, then poll execution status and fetch results, with per-region defaults stored in ~/.gdp_config/dorado_defaults.yaml. - Queue Resource Inspection: List project yarn queues and query queue resource usage for capacity checks. - Use Case: A data engineer needs to verify why a batch task failed in the boei18n region. They fetch the task details by task_id, then run a debug SQL count query against the underlying table to confirm data availability. ## Quick Start Ask the agent to list my Dorado projects in the cn region or run a debug SQL query on a specific temporary-query task.

Frequently Asked Questions about dorado

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

FAQPage Schema
How do I run a temporary SQL query on Dorado DataLeap?

Use the debug_sql_exec action with a region, task_id, project_id, and your SQL statement. The task_id must reference an existing Dorado temporary-query task created under Project > Temporary Query, which acts as the execution carrier.

How do I find a Dorado task ID for debug SQL?

Open the temporary query in the Dorado web console and read the task_id from the page URL, which follows the pattern /query/<task_id>. For example, /query/123456789?project=cn_2059 means task_id is 123456789.

Which regions does Dorado task lookup support?

Builtin regions are cn, sg, gcp, va, boe, and boei18n, with cn as the default. Custom regions can be configured in ~/.gdp_config/dorado_regions.yaml following the repo's config convention.

Why does search_tasks fail without a folder_id?

Dorado batch search requires a folder_id parameter to scope the query. If you do not know it, copy it from the Dorado page URL or ask the task owner; alternatively use list_tasks to enumerate the project's searchable root folder.

Can I set default task_id and project_id for Dorado debug SQL?

Yes, persist per-region defaults in ~/.gdp_config/dorado_defaults.yaml with default_task_id and default_project_id per region. Explicit input parameters always take precedence over these saved defaults.