Individual skill
coordinated-data-views
Show a table and its map, diagram, timeline or chart together, with selection synced both ways. Use when data appears in two representations at once.
skills/coordinated-data-views/SKILL.md
Source commit 8f78f13f74a2356326d0c3c21bc63e5624e6a457
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 192
- Repository last updated
- Nov 1, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- accessibility Repository topic
- agent-skills Repository topic
- claude-code-skills Repository topic
- claude-skills Repository topic
- cursor-skills Repository topic
- design-system Repository topic
- design-tokens Repository topic
- enterprise-ux Repository topic
- skills-sh Repository topic
- typography Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Coordinated Data Views
Some data has more than one natural representation. A set of locations has both a map and a list. A dependency network has both a diagram and a node table. A dataset has both a chart and a raw table. When both representations are genuinely useful for different tasks, show them simultaneously and keep them synchronized — this is called a coordinated view.
The core rule: **any selection or highlight made in one view is immediately reflected in the other.**
---
## When to Use Coordinated Views
Use coordinated views when:
1. The two representations serve different tasks — the table is for finding/scanning; the visual view is for understanding arrangement or relationships
2. Users will frequently move between the two — not just glance at one occasionally