coordinated-data-views SKILL.md skillA
coordinated-data-views from dembrandt/dembrandt-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add dembrandt/dembrandt-skills/coordinated-data-views@git:20261119.9d2f652Pins git:20261119.9d2f652 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- dembrandt/dembrandt-skills
- Path
directory/skills/coordinated-data-views/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261119.9d2f652, committed Nov 19, 2026
- Size
- 8,100 bytes
- Repository stars
- 197
- License
- MIT
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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 3. The dataset is large enough that the visual view alone doesn't identify individual items, and the table alone doesn't communicate how they relate Do not add a coordinated view purely for visual richness. If users only ever look at the table and ignore the visual view, it adds complexity without benefit. --- ## The Synchronized Selection Model …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_3sxplba7rshd4mdm/af171ea2da558a6e359dc21b90650ed3b388fbfa430851c2a306deabe6b800ea.json
Then /plugin install coordinated-data-views@markdownregistry-3sxplba7rshd4mdm in Claude Code. It installs git:20261119.9d2f652, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add dembrandt/dembrandt-skills/coordinated-data-views@sha256:af171ea2da558a6eThe line at the top of this page pins the label git:20261119.9d2f652, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_3sxplba7rshd4mdm)
0 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in dembrandt/dembrandt-skills/coordinated-data-views since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of coordinated-data-views from somewhere else? Ask it: where did my coordinated-data-views come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Nov 19, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/coordinated-data-views/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8100 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
dembrandt/dembrandt-skills · 197 stars · license MIT · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3sxplba7rshd4mdm GET https://markdownregistry.com/api/v1/resolve?ref=dembrandt/dembrandt-skills/coordinated-data-views GET https://markdownregistry.com/api/v1/blob/af171ea2da558a6e359dc21b90650ed3b388fbfa430851c2a306deabe6b800ea
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from dembrandt/dembrandt-skills
Every file in dembrandt/dembrandt-skills