본문으로 건너뛰기
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.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 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의 스킬 모두 보기

이 스킬의 문제 신고