dataviz
Design guidance for charts, graphs, dashboards, maps, and data visualizations, including a local palette validator.
git clone --depth 1 https://github.com/QwenLM/qwen-code /tmp/dataviz && cp -r /tmp/dataviz/packages/core/src/skills/bundled/dataviz ~/.claude/skills/datavizSKILL.md
# Dataviz Use this skill before producing a chart, dashboard, map, or data visualization. ## Workflow 1. Identify the analytic task: comparison, trend, distribution, relationship, ranking, part-to-whole, geography, or status monitoring. 2. Choose the simplest chart form that answers that task. Read `references/choosing-a-form.md` when the form is not obvious. 3. Write the finding into the title, subtitle, axis label, or direct annotation. A viewer should know what changed, what is high or low, or what decision the chart supports. 4. Pick colors from `references/palette.md`, or validate any custom palette with the script below. 5. Check `references/anti-patterns.md` before finalizing the design. ## Palette Validation Resolve paths relative to the skill base directory shown above this skill body. Do not assume `$QWEN_SKILL_ROOT` is set for normal shell commands. Run: ```bash node <skill-base-directory>/scripts/validate_palette.js '#1d4ed8,#b45309,#166534' --mode light ``` Treat `FAIL` as a required palette change. Treat `WARN` as acceptable only when the chart also uses labels, shape, texture, ordering, or another secondary encoding. ## Mark Rules - Use categorical palettes for unordered groups; use sequential or diverging ramps only for ordered values. - Prefer direct labels over legends when the chart has a small number of series. - Keep gridlines subtle and fewer than the data marks. - Avoid dual axes unless both series share a clearly explained transformation. - Do not rely on color alone for critical distinctions. - Keep dashboards scan-friendly: align cards, use consistent number formats, and reserve saturated color for important state changes.
Use after a Codex or Claude Code feature has been implemented in Qwen Code to run the selected reference agent and Qwen Code under the same scenario, capture HTTP and terminal traces, compare request bodies, tool/function schemas, outputs, and iterate until the reproduced behavior is close enough.
Use when reproducing an existing Codex or Claude Code feature in Qwen Code or another agent CLI by choosing a reference agent, capturing HTTP request bodies, prompts, tool/function schemas, terminal output, and then implementing the matching behavior in the target repo.
Review and repair current local changes until they converge, or run Qwen Code Autofix issue and review workflows from GitHub Actions.
Fix a bug from a GitHub issue, following the reproduce-first
Classify a bounded batch of stale PR CI failures and choose the safest response.
Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection, auto-merge candidates, labeling). Also covers creating, inspecting, and repairing a CodeScope index. Use for: code structure, who calls what, why something changed, similar functions, module boundaries, bug tracing, class relationships, PR risk/conflicts, or any question benefiting from a code knowledge graph. Applies when a `.codegraph` index exists in the workspace, or when the user wants to create one.
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
Stabilize a flaky test with a minimal, assertion-preserving fix — never by weakening or deleting the check.