agentscope-examples/agents/agentscope-dataagent/src/main/resources/shared/skills/chart-rendering/SKILL.md
Visualise the result of an analysis as a chart (line, bar, area, scatter, etc.). Use when the user asks to "plot...", "chart...", "show me the trend of...", "visualise...", or when a numerical result has more than ~10 rows and would be easier to read as a picture. Produces an image file plus the script that generated it.
npx skillsauth add agentscope-ai/agentscope-java chart-renderingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Repeatable SOP for turning a result set into a chart that actually communicates the point.
Match chart type to question. Decide before drawing:
| Question shape | Chart | |----------------|-------| | "How does X change over time?" | Line (single series) or multi-line | | "Composition / share of total" | Stacked bar, or 100% stacked area | | "Comparison across a small set of categories" | Bar (horizontal if labels are long) | | "Relationship between two numeric variables" | Scatter | | "Distribution of a single variable" | Histogram or box plot | | "Cumulative total" | Area |
If none fit, ask the user which view they want — do not default to "any chart will do".
Prepare the data. The query result from the [[sql-analysis]] Skill should
already be tidy (one row per data point, one column per dimension). If not,
reshape first using pandas (pivot, melt, groupby). Save the cleaned
frame to knowledge/cache/<topic>.csv so it can be re-rendered.
Render with matplotlib. Write the script to a file under
scratch/charts/<topic>.py and execute it via shell_run. Conventions:
Active users (count),
Date (UTC)).knowledge/style.md.bbox_inches='tight', dpi=150) under
knowledge/charts/<topic>.png.Show and explain. In the assistant reply, link the saved image with a
markdown image embed () and write
2–3 sentences interpreting it — what the chart shows, the one thing the
user should take away, and any caveat (incomplete latest data point,
outliers excluded, etc.).
Keep the script reproducible. The chart file is the artefact; the script
under scratch/charts/<topic>.py is the source of truth. If the user asks
for a tweak ("can we use a log y-axis?"), edit the script and re-run — do
not regenerate from scratch.
If the user wants a multi-chart dashboard with narrative around it (e.g. "build
me a weekly product health deck"), spawn the report-writer sub-agent —
this Skill is for individual charts.
documentation
四层技能合成、技能市场、自学习闭环
documentation
Four-layer skill composition, skill marketplaces, the self-learning loop
tools
# 技能(Skill) 一个 skill 就是一份写好的能力包:一个目录里放一份 `SKILL.md`(说明用途、给 agent 看的指令),可以再带一些参考文档、脚本或样例。写好后丢给 agent,它会在合适的时候自己用。 harness 让你从两个地方装 skill: - **接 skill 市场**:Git 仓库、Nacos、MySQL、classpath、或者自己写的后端 - **放在工作区**:项目里 `workspace/skills/` 下的就所有人共用;放在 `<userId>/skills/` 下的只有那个用户看得到 两类来源同时生效,不需要二选一。 > 关于 skill 自身的结构、`SKILL.md` 写法、资源加载、tool 绑定、代码执行这些通用概念,见 [Agent Skill](../task/agent-skill.md)。本文只讲 harness 这一层的用法。 --- ## 一个例子 把团队的 skill 仓库接进来,agent 立刻就能用: ```java HarnessAgent agent = HarnessAgent.bui
data-ai
Answer a quantitative business question by writing a SQL query against the data warehouse, validating it, and presenting the result. Use when the user asks "how many...", "what's the trend of...", "compare X vs Y over...", "what's our top N...", or anything that resolves to a query against tabular data. Produces a small result table plus the underlying query.