本文へ移動
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(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

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 のスキルをすべて見る

このスキルの問題を報告する