Agent skill

Yida Chart

by openyida in openyida/openyida

ECharts 高级可视化报表。依赖宜搭原生报表 getDataAsync.json 接口获取聚合数据,禁止前端聚合。触发词:「更美观」「ECharts」「大屏」「定制化」。普通「报表」「统计」需求默认由 yida-report 处理。

MITAuto-check passed

Install Yida Chart

skills CLI
$ npx skills add openyida/openyida --skill yida-chart -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install openyida/openyida yida-chart --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/openyida/openyida.git skills-src && mkdir -p .claude/skills && cp -r skills-src/yida-skills/skills/yida-chart .claude/skills/yida-chart && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
yida-chart
GitHub stars
220
Token cost
~1.7k tokens
SKILL.md length
454 words
Files
5 (incl. references)
Skills in repo
58
Repo updated
First seen
Licence
MIT

At a glance

ECharts 高级可视化报表。依赖宜搭原生报表 getDataAsync.json 接口获取聚合数据,禁止前端聚合。触发词:「更美观」「ECharts」「大屏」「定制化」。普通「报表」「统计」需求默认由 yida-report 处理。

  • Works in 6 steps: 聚合统计禁止前端聚合:KPI、分组、求和、平均、趋势、占比都必须走原生报表… → 必须依赖原生报表:不能在没有原生报表数据源的情况下直接创建 ECharts… → 不要混用 cid 和 fieldId:cid 是… → …
  • SKILL.md covers 适用场景, 核心规则, 方案选择 and 开发流程, plus 7 more sections
  • Calls git; reaches g.alicdn.com and geo.datav.aliyun.com

What it does

Yida Chart is an agent skill from openyida/openyida. ECharts 高级可视化报表。依赖宜搭原生报表 getDataAsync.json 接口获取聚合数据,禁止前端聚合。触发词:「更美观」「ECharts」「大屏」「定制化」。普通「报表」「统计」需求默认由 yida-report 处理。

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/echarts-bindding-guide.md`, `references/echarts-code-template.md` and `references/echarts-design-spec.md`).

The repository describes itself as: Your own personal YiDA AI assistant! The licence is MIT.

Example prompts

  • “Use the yida-chart skill to echart 高级可视化报表。依赖宜搭原生报表 getDataAsync.json 接口获取聚合数据,禁止前端聚合。触发词:「更美观」「ECharts」「大屏」「定制化」。普通「报表」「统计」需求默认由 yida-report 处理”
  • “/yida-chart”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. 聚合统计禁止前端聚合:KPI、分组、求和、平均、趋势、占比都必须走原生报表 getDataAsync.json / getCacheData.json。
  2. 必须依赖原生报表:不能在没有原生报表数据源的情况下直接创建 ECharts 聚合页面。
  3. 不要混用 cid 和 fieldId:cid 是 node_xxx,用于报表数据请求;fieldId 是组件标识,不能作为 API 请求参数。
  4. 不要编造报表参数:reportId、cid、dataSetKey、filterKey 必须来自 URL 或 Schema。
  5. ECharts 通过 CDN 加载:使用 this.utils.loadScript 或等价动态脚本加载,禁止 import / require。
  6. 数据失败必须有错误态:接口失败、无权限、空数据都要展示可理解提示,不要静默空白。

What it can do on your machine

Read from SKILL.md and the folder at commit 3dd4693. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • g.alicdn.com
    • geo.datav.aliyun.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Yida Chart loads about 1.7k tokens when it runs, and up to ~11k if it reads all its reference files. Until then it costs about 32 tokens; SKILL.md has 454 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~32
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~11k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from openyida/openyida at commit 3dd4693, republished under its MIT licence (© openyida). 454 words, ~1,702 tokens.

Download SKILL.mdSave it as .claude/skills/yida-chart/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
yida-chart
description
ECharts 高级可视化报表。依赖宜搭原生报表 getDataAsync.json 接口获取聚合数据,禁止前端聚合。触发词:「更美观」「ECharts」「大屏」「定制化」。普通「报表」「统计」需求默认由 yida-report 处理。

宜搭 ECharts 高级报表技能

适用场景

用户意图正确处理
"更美观"、"高级"、"定制化"、"ECharts"、"数据大屏"使用本技能
用户提供已有报表 URL,希望美化展示使用本技能的方案 C
多表关联分析当前不支持,先澄清或拆成单表报表

核心规则

致命规则(FATAL)
  1. 聚合统计禁止前端聚合:KPI、分组、求和、平均、趋势、占比都必须走原生报表 getDataAsync.json / getCacheData.json。
  2. 必须依赖原生报表:不能在没有原生报表数据源的情况下直接创建 ECharts 聚合页面。
  3. 不要混用 cid 和 fieldId:cid 是 node_xxx,用于报表数据请求;fieldId 是组件标识,不能作为 API 请求参数。
  4. 不要编造报表参数:reportId、cid、dataSetKey、filterKey 必须来自 URL 或 Schema。
  5. ECharts 通过 CDN 加载:使用 this.utils.loadScript 或等价动态脚本加载,禁止 import / require。
  6. 数据失败必须有错误态:接口失败、无权限、空数据都要展示可理解提示,不要静默空白。
重要规则(IMPORTANT)
  1. 原生报表双端隐藏:创建 ECharts 页面后,原生报表作为数据源应在 PC 和移动端导航中隐藏。
  2. 记录绑定关系:写入 .cache/<项目名>-report-bindding.json,记录 ECharts 页面、原生报表和组件映射。
  3. 更新时双页面同步:需求变化时先更新原生报表 Schema,再更新 ECharts 页面和绑定关系。
  4. 明细表走表单数据接口:仅数据明细表可用 this.utils.yida.searchFormDatas,聚合图表仍走报表接口。
  5. 遵循平台 JSX 组件页面规范:状态、生命周期、事件绑定、发布前校验按平台 Jsx 组件运行时规则执行。
  6. 当前应用报表绑定优先:修复或迁移现有 ECharts 页面时,不要复用其它应用的 REPORT_xxx、prdId/topicId 或 cid。必须在当前 app 内创建或同步原生报表,再批量替换绑定。

方案选择

场景方案流程
用户有原生报表 URL方案 C:基于已有报表创建 ECharts 页面解析 URL → get-schema → 提取组件参数 → 校验数据源 → 写 ECharts 页面
用户无原生报表但要 ECharts 高级报表方案 B:从头创建yida-report 创建原生报表 → get-schema → 创建 ECharts 页面
用户只要标准报表不使用本技能交给 yida-report

开发流程

bash
# Step 1: 只读检测环境和登录态
openyida env --json
openyida login --check-only --json

# Step 2: 准备原生报表数据源
# 无原生报表时先使用 yida-report 创建;已有 URL 时解析 appType/formUuid

# Step 3: 获取报表 Schema;需要文件时用 CLI 输出目录或结构化文件写入工具保存 stdout
openyida get-schema <appType> --all --keyword <报表名称> --output-dir .cache/openyida/<项目名或任务名>/schemas

# Step 4: 解析 cid / className / dataSetKey / filterKey / cname

# Step 5: 创建 ECharts 自定义页面并编写源码
openyida create-page <appType> "<ECharts页面名>" --mode dashboard
openyida check-page project/pages/src/<页面名>.oyd.jsx

# Step 6: 发布并验证
openyida publish project/pages/src/<页面名>.oyd.jsx <appType> <echartsFormUuid> --health-check
已有 ECharts 页面 / 跨应用迁移修复流程

当页面报错 no permission for the report、图表数据加载失败,或发现源码里绑定的 REPORT_xxx 属于旧应用时,按下面流程修复:

  1. openyida list-forms <当前appType> --json 确认当前应用是否已有 formType=report;没有则先用 yida-create-form-page 创建数据源表单,按业务场景写入示例数据,再用 yida-report 创建原生报表。
  2. openyida get-schema <当前appType> <新REPORT_xxx> --json,从 componentsTree 提取所有 Youshu* 组件的 id、componentName、props.dataSetModelMap key、dataViewQueryModel.filterList[].filterKey 和标题。
  3. 页面常量只保留 REPORT_FORM_UUID / REPORT_UUID,prdId/topicId 必须通过 getFormNavigationListByOrder 按该 REPORT 动态获取。
  4. 每个组件绑定使用真实 schema 值:cid 使用 node_oc...,className 使用 YoushuTable / YoushuSimpleIndicatorCard 等,表格 dataSetKey 以 schema 为准(常见 table),指标卡常见 youshuData。
  5. filterKey 必须按组件记录,例如 statusTableStatus、budgetTableStatus。不要把字段级的 status 当作多个组件通用的 filterKey。
  6. 写入 .cache/openyida/<任务名>/report-binding.json,记录数据源表单、新报表、组件映射和绑定的 ECharts 页面。
  7. 增加防回归测试:grep 或 Jest 断言源码不再包含旧 REPORT、旧 prdId、旧 appType 和旧 cid 前缀。
  8. 执行 openyida check-page、openyida compile、openyida publish ... --health-check,最后跑 git diff --check。

报表参数速查

参数来源位置用途注意
cidcomponentsTree[].children[].idgetDataAsync.json 请求参数必须是 node_xxx
className组件 componentName请求 componentClassName如 YoushuPieChart
dataSetKeyprops.dataSetModelMap 的 key请求数据集指标卡常见 youshuData,图表常见 chartData
filterKeydataViewQueryModel.filterList[]构造筛选参数每个组件独立,不能共用
cnameprops.componentTitle.zh_CN页面展示和调试可为空但建议保留
prdId / topicId导航接口 getFormNavigationListByOrder报表接口必填不能硬编码

图表组件白名单

componentName类型dataSetKey
YoushuSimpleIndicatorCard指标卡youshuData
YoushuPieChart饼图chartData
YoushuGroupedBarChart分组柱状图chartData
YoushuLineChart折线图chartData
YoushuFunnelChart漏斗图chartData
YoushuComboChart组合图chartData
YoushuRadarChart雷达图chartData
YoushuTable明细表chartData

必须排除 YoushuPageHeader、YoushuTopFilterContainer、YoushuSelectFilter、YoushuTimeFilter、YoushuInputFilter 等容器或筛选器组件。

Show full SKILL.md (169 more words)Show less

ECharts 页面必备结构

项要求
状态顶层 var _customState
状态方法getCustomState、setCustomState、forceUpdate
生命周期didMount 初始化,didUnmount 清理 chart 实例和 resize 事件
渲染入口renderJsx 每个 return 分支都包含隐藏的 this.state.timestamp
CDNhttps://g.alicdn.com/code/lib/echarts/5.6.0/echarts.min.js
工具函数不需要 this 的函数用 var _xxx = function () {}
组件方法需要宜搭运行时 this 的方法用 export function xxx() {}

数据接口速查

场景接口约束
聚合统计/visual/visualizationDataRpc/getDataAsync.json由原生报表接口返回,禁止浏览器端聚合
缓存聚合/visual/visualizationDataRpc/getCacheData.json可按报表配置复用缓存数据
明细表this.utils.yida.searchFormDatas只用于展示原始记录,不做分组求和
详情跳转/APP_xxx/formUuid/formInstId明细表记录需保留 formInstId
地图 GeoJSONhttps://geo.datav.aliyun.com/areas_v3/bound/100000_full.jsonECharts 5 地图需 registerMap('china', geoJson)

生成前自检

  • 已确认需求是 ECharts 高级可视化,而非普通原生报表
  • 已存在或已创建原生报表数据源
  • 已通过 openyida get-schema 获取 Schema 文件
  • 已提取每个图表组件的 cid、className、dataSetKey、filterKey、cname
  • prdId 通过导航接口动态获取,不硬编码
  • 页面绑定的 REPORT_xxx 属于当前 app,不是旧样例应用或其它应用
  • filterKey 按组件记录,未把同一字段的筛选 key 跨组件复用
  • 聚合图表不使用 searchFormDatas 做前端聚合
  • renderJsx 所有分支都有隐藏 timestamp div
  • didUnmount 清理 ECharts 实例、resize 监听和定时器
  • 发布前执行 openyida check-page <源文件>
  • 记录 .cache/<项目名>-report-bindding.json

常见问题

Q:用户说"优化已有报表",是不是改原生报表?
A:不是。本技能最终产物是 ECharts 自定义页面,原生报表只作为数据源。

Q:为什么不能前端聚合?
A:权限、过滤器、数据量和统计口径都由宜搭原生报表保证;前端聚合容易越权、慢且口径不一致。

Q:多个图表能共用同一个 filterKey 吗?
A:不能。同一个筛选器在不同组件里也可能有不同 filterKey,必须逐组件提取。

Q:页面点击筛选后怎么刷新?
A:更新 _customState.filterValueMap,重新调用报表数据请求函数,对已有 chart 执行 setOption,不要频繁 dispose 重建。

参考文档

文档覆盖范围何时阅读
ECharts 页面代码模板必备函数、CDN、prdId 动态获取、报表请求模板、meta 解析编写 ECharts 页面代码前必读
ECharts 视觉规范默认风格、配色、卡片、图表模板、多端适配、表格样式设计页面 UI 时必读
已有报表绑定指南方案 C、Schema 解析、filterKey、数据源完整性校验用户提供报表 URL 时必读
示例命令示例、页面代码示例、常见图表实现需要参考完整写法时阅读
yida-report 子技能原生报表创建、追加图表、Schema 生成需要先创建或补齐原生报表时调用 use_skill("yida-report", "创建或补齐原生报表")
平台 JSX 组件页面规范宜搭 React 16 自定义页面规则不确定页面运行时限制时读取对应规范

© openyida, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in yida-skills/skills/yida-chart of openyida/openyida.

  • SKILL.md
  • references/echarts-bindding-guide.md
  • references/echarts-code-template.md
  • references/echarts-design-spec.md
  • references/examples.md

Open the folder on GitHubat commit 3dd4693

Compare with similar skills

Yida Chart next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Yida Chart compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Yida Chart this skillopenyida/openyida220—~1.7kAutomated safety check: PassMIT
Chart Visualizationbytedance/deer-flow83k2 repos~840Automated safety check: PassMIT
Working With ChartsPostHog/posthog40k—~948Automated safety check: PassCustom licence
Helm Chartssickn33/agentic-awesome-skills47k1 repos~2.6kAutomated safety check: PassMIT
Claim Chartanthropics/claude-for-legal9.6k2 repos~10kAutomated safety check: PassApache-2.0
Chartmohitagw15856/pm-claude-skills1.4k—~893Automated safety check: PassMIT

Similar skills

  • Chart Visualization

    bytedance/deer-flow

    Picks a suitable chart type from 26 options for your data, maps the data to that chart's parameters and generates a chart image through a JavaScript script.

    83k GitHub starsUsed in 2 repos~840 tokens
    Data & AnalyticsAuto-check passed
  • Working With Charts

    PostHog/posthog

    Official

    Guides consumers of @posthog/quill-charts through chart selection, data, themes, sizing, and composition.

    40k GitHub stars~948 tokensUpdated today
    Data & AnalyticsAuto-check passed
  • Helm Charts

    sickn33/agentic-awesome-skills

    Create, manage, and deploy Helm charts for Kubernetes package management.

    47k GitHub starsUsed in 1 repo~2.6k tokens
    DevOps & CloudAuto-check passed
  • Claim Chart

    anthropics/claude-for-legal

    Official

    Build or review an element chart — a patent claim chart (infringement, invalidity, or review) or a civil element chart for any cause of action or defense — with every cell pin-cited and gap…

    9.6k GitHub starsUsed in 2 repos~10k tokens
    Legal & ComplianceAuto-check passed
  • Chart

    mohitagw15856/pm-claude-skills

    Turn numbers into a chart — bar, line, area, pie, or doughnut.

    1.4k GitHub stars~893 tokensUpdated yesterday
    Auto-check passed
  • Use this plugin when the user wants a "NYT-Style Data Chart Frame" HyperFrames motion video — NYT-newsroom typography, staggered reveal animation, and editorial-grade charts (line, bar, or range…

    100k GitHub stars~329 tokensUpdated today
    Frontend & DesignAuto-check passed

More from openyida/openyida

All 58 skills in this repo
  • Yida Canvas Custom Page

    openyida/openyida

    宜搭自定义页面开发规范,使用 YidaCodeCanvas 组件实现现代 React18 自定义页面。用于官网、看板、工作台、列表、详情、门户壳、可视化、hooks 交互、表单入口,以及需要门户组件、数据管理视图、成员、部门或上传组件的场景;发布层自动注入 yida/utils window 桥。

    220 GitHub stars~4.3k tokensUpdated 8 days ago
    Auto-check passed
  • Openyida Release

    openyida/openyida

    快速发布 OpenYida npm 正式版或测试版。用户说“发布正式版”“发布测试版”“发 beta”或要求按当天日期生成版本 tag 时使用;不用于宜搭应用或自定义页面发布。

    220 GitHub stars~520 tokensUpdated 8 days ago
    Auto-check passed
  • Yida Design Plan

    openyida/openyida

    Plan 模式的视觉设计分支。基于需求选择视觉方向,再结合业务页面规划维护 build-plan.json 的 visualStyle,供 CLI 派生 design.md。

    220 GitHub stars~756 tokensUpdated 8 days ago
    Auto-check passed
  • Prevent stale local OpenYida custom page source from overwriting live designer edits.

    220 GitHub stars~1.2k tokensUpdated 8 days ago
    Auto-check passed
  • Codemap

    openyida/openyida

    Generate, update, or drift-check agent-facing CodeMaps as progressive code terrain indexes for projects, features, capabilities, functions, modules, or bug chains.

    220 GitHub stars~1k tokensUpdated 8 days ago
    Auto-check passed
  • Sdd Riper One Light

    openyida/openyida

    面向 GPT-5.5 等强模型和熟练用户的轻量 AI Agent Harness / checkpoint-driven coding skill。默认用户已经把任务切到基本可执行的最小混沌单元;模型自行分解、探索与推进,人类通过最终目标、最小 spec、复述、checkpoint、证据验证与回写来低干扰控盘。

    220 GitHub stars~1.5k tokensUpdated 8 days ago
    Auto-check passed

Questions about Yida Chart

What does Yida Chart do?

ECharts 高级可视化报表。依赖宜搭原生报表 getDataAsync.json 接口获取聚合数据,禁止前端聚合。触发词:「更美观」「ECharts」「大屏」「定制化」。普通「报表」「统计」需求默认由 yida-report 处理。. Yida Chart is an agent skill from openyida/openyida.

How do I install Yida Chart in Claude Code?

Run `npx skills add openyida/openyida --skill yida-chart -a claude-code`. Or copy the skill folder (yida-skills/skills/yida-chart in openyida/openyida) into .claude/skills/yida-chart in your project. Claude Code loads it when a task matches its description.

How do I install Yida Chart in Codex?

Run `npx skills add openyida/openyida --skill yida-chart -a codex`. Or copy the skill folder (yida-skills/skills/yida-chart in openyida/openyida) into .agents/skills/yida-chart in your project. Codex loads it when a task matches its description.

Can I use Yida Chart in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openyida/openyida --skill yida-chart -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/yida-chart, .gemini/skills/yida-chart, .github/skills/yida-chart and .opencode/skills/yida-chart in your project.

What does Yida Chart need to run?

Going by SKILL.md and its folder, Yida Chart needs the command-line tools its instructions call (git).

Does Yida Chart access the network?

SKILL.md names 2 domains. In commands or code: g.alicdn.com and geo.datav.aliyun.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Yida Chart safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Yida Chart use?

Yida Chart is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Yida Chart use?

About 1.7k tokens (SKILL.md is roughly 6.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 9.4k tokens, read only when the agent opens those files.

What are the alternatives to Yida Chart?

Skills that share tags, products or a category with Yida Chart: Chart Visualization (bytedance/deer-flow, 83k stars), Working With Charts (PostHog/posthog, 40k stars), Helm Charts (sickn33/agentic-awesome-skills, 47k stars) and Claim Chart (anthropics/claude-for-legal, 9.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Yida Chart?

openyida (a GitHub organization) maintains it in openyida/openyida, which has 220 GitHub stars. The repository holds 58 skills in this directory. The repository was last updated on September 30, 2026.

Source: openyida/openyida on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.