跳到正文
cccskills
免费在 GitHub 公开

chart-visualization

Design, critique, or specify honest charts and data visualizations from known data and audience needs. Use for chart selection, misleading-chart audits, accessibility, dashboard visuals, or "make this data easier to understand"; do not use for raw data analysis, PPT deck generation, spreadsheet surgery, or fabricated chart data.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(1)

  • SKILL.md3.0 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Chart Visualization

Purpose

Choose or review visualizations so the chart answers the user's question honestly, accessibly, and with clear data provenance.

When to Use

Use for:

  • selecting chart types for a known dataset or analysis result
  • auditing charts for misleading axes, bad encodings, clutter, inaccessible color, or unclear labels
  • specifying dashboard/chart requirements before implementation
  • improving chart titles, annotations, scales, legends, and captions

Do not use for:

  • performing the underlying numeric analysis; use data-analysis
  • generating a full slide deck; use pptx-generator
  • editing an XLSX file while preserving workbook internals; use minimax-xlsx
  • inventing sample data to make a chart look good

Workflow

  1. Identify the chart question: comparison, trend, distribution, composition, relationship, geospatial pattern, or ranking.
  2. Confirm data provenance, fields, units, denominators, time window, and transformations before choosing encodings.
  3. Choose the simplest chart type that answers the question.
  4. Specify encodings: x/y, series, grouping, sorting, scale, baseline, annotations, uncertainty, and interaction if needed.
  5. Audit for honesty: truncated axes, dual-axis confusion, hidden denominators, misleading aggregation, overplotting, cherry-picked ranges, and omitted uncertainty.
  6. Audit for usability: title states the takeaway, labels are readable, color is accessible, legend is close to data, mobile/print context is considered.

Data Authenticity Rules

  • Do not fabricate values, categories, units, totals, or trend direction.
  • If the data is unavailable, produce a chart specification or critique checklist, not a rendered claim.
  • Label derived metrics and normalized values clearly.
  • Prefer annotations that explain source-backed events; mark speculative explanations [UNVERIFIED].

Output Contract

STATUS: SPECIFIED | REVIEWED | PARTIAL | BLOCKED

QUESTION:
- <what the chart should answer>

DATA BASIS:
- <source fields, units, filters, transformations, or missing provenance>

RECOMMENDED VISUAL:
- Chart type:
- Encodings:
- Title / labels / annotations:
- Accessibility notes:

HONESTY AUDIT:
- <axis, scale, aggregation, uncertainty, denominator, or range concerns>

IMPLEMENTATION NOTES:
- <library-agnostic guidance or project-specific constraints>

UNVERIFIED:
- <missing data/provenance or N/A>

Provenance

Clean-room AILI/OpenCode adaptation inspired by the public DeerFlow chart-visualization skill pattern. No upstream skill text, runtime paths, tools, generated assets, provider assumptions, or chart templates are copied. Source family: bytedance/deer-flow, MIT License.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Review a single academic paper, preprint, DOI, arXiv link, or user-provided PDF/text with source-grounded critique. Use for paper summaries, methodology review, novelty checks, reproducibility concerns, or "review this paper" requests; do not use for multi-paper surveys, systematic literature reviews, citation management, or implementation from a paper.

中文简介正在准备中。当前显示原文说明。

Rosetears520/aili-workflows22026年9月27日 更新

AI regression scouting routing. Use when agents, prompts, skills, model/tool routing, harness fixtures, or generated-output expectations change and need regression scenarios; do not use for ordinary product-code regressions.

中文简介正在准备中。当前显示原文说明。

Rosetears520/aili-workflows22026年9月27日 更新

Run the AILI delivery lifecycle from natural-language IDEATE, DEFINE, BUILD, and SHIP intent or the equivalent slash shortcuts; use for idea shaping, spec/test definition, bounded BUILD package queues, review-repair closeout, or adapter routing without exposing internal stage commands.

中文简介正在准备中。当前显示原文说明。

Rosetears520/aili-workflows22026年9月27日 更新

Android native Kotlin/Compose app development, Material 3 UI, accessibility, and Gradle builds.

中文简介正在准备中。当前显示原文说明。

Rosetears520/aili-workflows22026年9月27日 更新

Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.

中文简介正在准备中。当前显示原文说明。

Rosetears520/aili-workflows22026年9月27日 更新

Route an explicitly requested independent/delegated browser QA assignment or durable E2E evidence need; do not trigger for direct Playwright/DOM/console/network inspection, ordinary UI implementation, backend-only work, or production-mutating flows.

中文简介正在准备中。当前显示原文说明。

Rosetears520/aili-workflows22026年9月27日 更新

查看 Rosetears520 的全部技能

报告此技能的问题