tea-query

Query TEA-next dashboards, reports, and report data via gdpa-cli.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Accessing TEA-next (DataOpen) dashboards and report data normally requires navigating the web UI or writing custom API calls with credential management. This Skill lets you list dashboards, inspect reports, and retrieve report data directly through gdpa-cli commands. ## Core Features & Use Cases - Dashboard Discovery: List all dashboards under a TEA-next project and fetch dashboard details by ID. - Report Inspection: List reports within a dashboard and retrieve report metadata without pulling full data. - Report Data Querying: Query actual report data with global filters, profile filters, time periods, and parameter filters across CN and SG regions. - Use Case: A data analyst needs yesterday's conversion metrics from a TEA dashboard. They provide the project ID, list the dashboards, find the report, and query its data with a time filter—all from the chat. ## Quick Start Ask the assistant to list all TEA dashboards for project 12345 in the sg region, then query the data of a specific report.

Frequently Asked Questions about tea-query

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

FAQPage Schema
How do I query TEA report data from the command line?

Run gdpa-cli run tea-query with action query_report, providing region, project_id, and report_id. You can add global_filter, profile_filters, and period parameters to narrow the returned data.

How do I find dashboard and report IDs in TEA-next?

Use the list_dashboards action with your region and project_id to see available dashboards, then call list_reports with a dashboard_id to enumerate its reports. The returned IDs feed directly into query_report.

What credentials does TEA-next API access require?

TEA-next uses DataOpen application credentials (app_id and app_secret) per region. Obtain them from the DataOpen app page for your region, then run gdpa-cli tea credential set --region <region> to save them locally.

Does TEA query support both China and Singapore regions?

Yes, every action requires a region parameter set to cn or sg. CN uses data.bytedance.net while SG uses tea-captain.tiktok-row.net, and credentials are configured separately per region.

Why is my TEA report query slow or timing out?

Complex reports can take up to 5 minutes, which matches the 300,000ms API timeout. The APIs also enforce 5 QPS and 100,000 daily calls, so reduce filter complexity or retry if limits are hit.