polym-dashboard-watch

Retrieve BytePlus C360 customer usage data and generate trend reports.

8|Updated May 13, 2026
One-click install
npx skills add https://github.com/byteplus-sa/polym --skill polym-dashboard-watch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: polym-dashboard-watch
Source: https://github.com/byteplus-sa/polym/tree/main/skills/polym-dashboard-watch
Command: npx skills add https://github.com/byteplus-sa/polym --skill polym-dashboard-watch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It eliminates the manual effort of checking BytePlus C360 customer dashboards and turning raw usage charts into actionable insights about trends, quota risk, and anomalies.

Core Features & Use Cases

  • Customer dashboard query by name: Finds the customer in C360 (via React-fiber extraction) using customer name context and then opens the correct usage dashboard view.
  • Usage trend reporting: Produces a structured report covering last-30-days totals, MoM change, product distribution, and quota/balance status.
  • Actionable insight surfacing + optional knowledge write: Detects key events (growth/decline/stoppage, quota criticality, spikes, new activation) and can save important notes to the knowledge base on confirmation.

Quick Start

Ask the AI: 查一下客户X的数据并给出最近30天用量趋势与关键告警。

Frequently Asked Questions about polym-dashboard-watch

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

FAQPage Schema
How do I automate BytePlus C360 customer usage dashboard reporting?

Automating BytePlus C360 usage dashboard reporting involves retrieving customer dashboard data by name and converting it into a trend report with actionable insights. This eliminates manual chart checking.

Can I detect month-over-month usage changes and quota risks for specific customers?

Yes, you can detect month-over-month changes and quota risks by analyzing customer usage trends. The system identifies anomalies like spikes, declines, stoppages, and quota criticality, surfacing them as actionable insights.

Does extracting ECharts metrics from C360 require a specific browser environment?

Extracting ECharts metrics from C360 requires Claude in a Chrome extension-based browser automation environment. This setup is necessary to read visual dashboard data and extract customer metrics.

What is the best way to track last-30-days token usage and new activations?

The best way to track last-30-days token usage and new activations is to generate a structured usage trend report covering totals, product distribution, and key events. It highlights growth patterns and new activations.

How do I save dashboard insight signals to a local knowledge base?

To save dashboard insight signals to a local knowledge base, you use the local-wiki UX feature to optionally write detected events on confirmation. This stores important notes about growth, decline, or quota criticality.

Why does customer dashboard query require React-fiber extraction?

Customer dashboard query requires React-fiber extraction to correctly find the customer in C360 using the customer name context. This mechanism ensures the correct usage dashboard view is opened for data retrieval.