[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BY4JS3T8NPPGP6AC1ZC6GE":3,"skill-same:01M7BY4JS3T8NPPGP6AC1ZC6GE":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7BY4JS3T8NPPGP6AC1ZC6GE","d3-visualization",null,"Build deterministic, verifiable data visualizations with D3.js. Generate standalone HTML\u002FSVG (and optional PNG) from local data files without external network dependencies. Use when tasks require charts, plots, axes\u002Fscales, legends, tooltips, or data-driven SVG output.","linyouxue\u002Fskill-repair-benchmark","linyouxue","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F216151464?v=4","01M7BJEVCXKD74KH6FG9CBVSQB","林宥学","01M7BJEVE02NP217V93BKZFC0J",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fevaluation\u002Fresults\u002FSkillAxe-Opus47-Gold15-20260921\u002Ftasks\u002Fdata-to-d3\u002Frepaired_run\u002Finputs\u002Fskills\u002Fd3-visualization\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: d3-visualization\ndescription: Build deterministic, verifiable data visualizations with D3.js. Generate standalone HTML\u002FSVG (and optional PNG) from local data files without external network dependencies. Use when tasks require charts, plots, axes\u002Fscales, legends, tooltips, or data-driven SVG output.\n---\n\n# D3.js Visualization Skill\n\nUse this skill to turn structured data (CSV\u002FTSV\u002FJSON) into **clean, reproducible** visualizations using **D3.js**. The goal is to produce **stable outputs** that can be verified by diffing files, hashing, or by an automated browser-based test harness (e.g., Playwright\u002Fjsdom).\n\n## When to use\n\nActivate this skill when the user asks for any of the following:\n\n- \"Make a chart\u002Fplot\u002Fgraph\u002Fvisualization\"\n- bar\u002Fline\u002Fscatter\u002Fbubble\u002Farea\u002Fhistogram\u002Fbox\u002Fviolin\u002Fheatmap\n- timelines, small multiples, faceting\n- axis ticks, scales, legends, tooltips\n- data-driven SVG output for a report or web page\n- converting data to a static SVG or HTML visualization\n- interactive dashboards linking multiple views (e.g., chart + table, click-to-highlight)\n\nIf the user only needs a quick table or summary, **don't** use D3—use a spreadsheet or plain markdown instead.\n\n---\n\n## Inputs you should expect\n\n- One or more local data files: `*.csv`, `*.tsv`, `*.json`\n- A chart intent:\n  - chart type (or you infer the best type)\n  - x\u002Fy fields and aggregation rules\n  - sorting\u002Ffiltering rules\n  - dimensions (width\u002Fheight) and margins\n  - color rules (categorical \u002F sequential)\n  - any labeling requirements (title, axis labels, units)\n- Output constraints:\n  - \"static only\", \"no animation\", \"must be deterministic\", \"offline\", exact output paths, exact D3 major version, etc.\n\nIf details are missing, **make reasonable defaults** and document them in comments near the top of the output file.\n\n### Honor task-specified paths and versions\n\nWhen the task specifies **any** of the following, they override the defaults in this skill:\n\n- Output directory \u002F file names (e.g., `\u002Froot\u002Foutput\u002Findex.html`, `output\u002Fjs\u002Fvisualization.js`).\n- D3 **major version** (e.g., v6 vs v7). Download the matching minified bundle to the exact filename the task requests (e.g., `js\u002Fd3.v6.min.js`). Do **not** substitute a different major version.\n- Data-copy requirements (\"copy input data into `output\u002Fdata\u002F`\"). Copy the files exactly, preserving subdirectory structure and file names (including case) so relative paths in the HTML resolve.\n\nA quick self-check before you finish:\n\n- [ ] Every path listed in the task exists on disk.\n- [ ] The D3 file is the requested major version (grep the file for `d3.js v6` or `d3.js v7`).\n- [ ] Data files referenced by your JS exist under the copied `data\u002F` tree with matching case.\n\n---\n\n## Outputs you should produce\n\nWhen the task does not specify paths, prefer producing **all of** the following:\n\n1. `dist\u002Fchart.html` — standalone HTML that renders the visualization\n2. `dist\u002Fchart.svg` — exported SVG (stable and diff-friendly)\n3. (Optional) `dist\u002Fchart.png` — if the task explicitly needs a raster image\n\nWhen the task **does** specify paths (common for web-app tasks), follow them exactly. A typical layout requested by tasks:\n\n```\noutput\u002F\n  index.html\n  js\u002F\n    d3.v6.min.js         # pinned D3, exact filename from task\n    visualization.js     # your code\n  css\u002F\n    style.css\n  data\u002F                  # copies of input data, same structure as source\n```\n\n---\n\n## Determinism rules (non-negotiable)\n\nTo keep results stable across runs and machines:\n\n### Data determinism\n- **Sort** input rows deterministically before binding to marks (e.g., by x then by category).\n- Use stable grouping order (explicit `Array.from(grouped.keys()).sort()`).\n- Avoid locale-dependent formatting unless fixed (use `d3.format`, `d3.timeFormat` with explicit formats).\n\n### Rendering determinism\n- **No randomness**: do not use `Math.random()` or `d3-random`.\n- **No transitions\u002Fanimations** by default (transitions can introduce timing variance).\n- **Fixed** `width`, `height`, `margin`, `viewBox`.\n- Use **explicit tick counts** only when needed; otherwise rely on D3 defaults but keep domains fixed.\n- Avoid layout algorithms with non-deterministic iteration unless you control seeds\u002Fiterations (e.g., force simulation). If a force layout is required:\n  - fix the tick count (e.g., run 300 warm-up ticks with `simulation.tick()` then let it continue for user interaction),\n  - fix initial positions deterministically (e.g., sorted nodes placed on a grid or on per-cluster centers),\n  - use deterministic cluster\u002Fattractor centers (e.g., points on a circle around the chart center),\n  - always add `forceCollide` when circles must not overlap.\n\n### Offline + dependency determinism\n- Do **not** load D3 from a CDN.\n- Pin D3 to the **major version the task requests** (default when unspecified: **d3@7.9.0**). Common task requests: `d3.v6.min.js`, `d3.v7.min.js`.\n- Vendor the minified D3 bundle at the exact path the task asks for (e.g., `js\u002Fd3.v6.min.js`, `vendor\u002Fd3.v7.9.0.min.js`).\n\n### File determinism\n- Stable SVG output:\n  - Avoid auto-generated IDs that may change.\n  - If you must use IDs (clipPath, gradients), derive them from stable strings (e.g., `\"clip-plot\"`).\n- Use LF line endings.\n- Keep numeric precision consistent (e.g., round to 2–4 decimals if needed).\n\n---\n\n## Serving the page & process hygiene (READ BEFORE FINISHING)\n\nD3 loaders like `d3.csv`, `d3.json`, `d3.tsv` use `fetch`, which browsers block on the `file:\u002F\u002F` scheme (CORS). Automated verifiers therefore usually spin up a **static HTTP server on a fixed port** (e.g., 8000, 8080, 8765) and drive a headless browser (Playwright\u002Fjsdom) against it.\n\nThat has two consequences for you:\n\n### 1. Design for HTTP serving, not file:\u002F\u002F\n\n- Use **relative** URLs in your HTML\u002FJS (`js\u002Fd3.v6.min.js`, `data\u002Fstock-descriptions.csv`), never absolute filesystem paths.\n- Do not hard-code `http:\u002F\u002Flocalhost:PORT`.\n- Preserve the case of data file names exactly as they appear on disk (case-sensitive on Linux).\n\n### 2. Do NOT leave background servers or browsers running\n\nIf you start a local HTTP server, jsdom instance, Playwright browser, or any long-lived process to self-verify your work, you **must fully tear it down before you finish**. A verifier that tries to `bind()` the same port will fail all browser-based tests with `OSError: [Errno 98] Address already in use`.\n\nSafe pattern:\n\n```bash\n# start\npython3 -m http.server 8000 --bind 127.0.0.1 > \u002Ftmp\u002Fhttpd.log 2>&1 &\nSERVER_PID=$!\n\n# ... run your check ...\n\n# stop — always run this before you finish, even on failure\nkill \"$SERVER_PID\" 2>\u002Fdev\u002Fnull || true\nwait \"$SERVER_PID\" 2>\u002Fdev\u002Fnull || true\n# belt-and-suspenders: kill any stragglers on that port\nfuser -k 8000\u002Ftcp 2>\u002Fdev\u002Fnull || true\n```\n\nBefore your final message, run a check equivalent to:\n\n```bash\nss -ltn 2>\u002Fdev\u002Fnull | awk '{print $4}' | grep -E ':(8000|8080|8765|3000|5000)$' && echo \"PORT STILL BOUND — kill it\" || echo \"ports clear\"\npgrep -af 'http.server|node .*jsdom|playwright|chromium' || echo \"no stray processes\"\n```\n\nIf anything is still bound, kill it. **Leaving a server bound to a common port is one of the most frequent causes of a 0.0 reward on browser-based verifiers even when the artifacts themselves are correct.**\n\n### 3. Prefer non-networked self-checks when possible\n\nIf you just want to sanity-check the JS, you can often skip the server entirely:\n\n- Parse the CSV in Node and re-run the transformation logic directly.\n- Or use jsdom with `runScripts: 'dangerously'` and inject the CSV text via `d3.csvParse` instead of `d3.csv` (no fetch needed).\n\nThis avoids opening any port at all.\n\n---\n\n## Recommended project layout (when task does not specify)\n\n```\ndist\u002F\n  chart.html        # standalone HTML with inline or linked JS\u002FCSS\n  chart.svg         # exported SVG (optional but nice)\n  chart.png         # rasterized (optional)\nvendor\u002F\n  d3.v7.9.0.min.js  # pinned D3 library\n```\n\n---\n\n## Interactive features (tooltips, click handlers, hover effects)\n\nWhen the task requires interactivity (e.g., tooltips on hover, click to highlight, linked views):\n\n### Tooltip pattern (recommended)\n\n1. **Create a tooltip element** in HTML:\n```html\n\u003Cdiv id=\"tooltip\" class=\"tooltip\">\u003C\u002Fdiv>\n```\n\n2. **Style with CSS** using `.visible` class for show\u002Fhide:\n```css\n.tooltip {\n    position: absolute;\n    padding: 10px;\n    background: rgba(0, 0, 0, 0.8);\n    color: white;\n    border-radius: 4px;\n    pointer-events: none;  \u002F* Prevent mouse interference *\u002F\n    opacity: 0;\n    transition: opacity 0.2s;\n    z-index: 1000;\n}\n\n.tooltip.visible {\n    opacity: 1;  \u002F* Show when .visible class is added *\u002F\n}\n```\n\n3. **Add event handlers** to SVG elements:\n```javascript\nsvg.selectAll('circle')\n    .on('mouseover', function(event, d) {\n        d3.select('#tooltip')\n            .classed('visible', true)\n            .html(`\u003Cstrong>${d.name}\u003C\u002Fstrong>\u003Cbr\u002F>${d.value}`)\n            .style('left', (event.pageX + 10) + 'px')\n            .style('top', (event.pageY - 10) + 'px');\n    })\n    .on('mouseout', function() {\n        d3.select('#tooltip').classed('visible', false);\n    });\n```\n\n**Key points:**\n- Use `opacity: 0` by default (not `display: none`) for smooth transitions.\n- Use `.classed('visible', true\u002Ffalse)` to toggle visibility.\n- `pointer-events: none` prevents tooltip from blocking mouse events.\n- Position tooltip relative to mouse with `event.pageX\u002FpageY`.\n\n### Click handlers for selection\u002Fhighlighting\n\n```javascript\nsvg.selectAll('.bar')\n    .on('click', function(event, d) {\n        d3.selectAll('.bar').classed('selected', false);\n        d3.select(this).classed('selected', true);\n    });\n```\n\nCSS for highlighting:\n```css\n.bar.selected {\n    stroke: #000;\n    stroke-width: 3px;\n}\n```\n\n### Linked views (chart ↔ table)\n\nWhen the task asks that clicking a mark highlights a row and vice versa, use a single **selection state** shared by both renderers:\n\n```javascript\nlet selectedKey = null;\nfunction select(key) {\n    selectedKey = (key === selectedKey) ? null : key;\n    updateChartHighlight(selectedKey);\n    updateTableHighlight(selectedKey);\n}\n\u002F\u002F both bubble click and row click call select(d.ticker)\n```\n\nExpose a stable class name (e.g., `.selected`) on both the SVG element and the `\u003Ctr>` so the verifier can detect the linkage.\n\n### Conditional interactivity\n\nSome marks should not be interactive (e.g., ETFs in a stock task have no tooltip data):\n```javascript\n.on('mouseover', function(event, d) {\n    if (d.sector === 'ETF' || d.marketCap == null) return;  \u002F\u002F no tooltip\n    showTooltip(event, d);\n});\n```\nRead the task carefully for these \"do not show for X\" carve-outs and implement the early return explicitly.\n\n---\n\n## Pre-finish checklist\n\nBefore returning to the user, verify each item:\n\n- [ ] All files listed in the task exist at the exact paths.\n- [ ] D3 file is the requested major version.\n- [ ] HTML uses **relative** paths; opening via a static HTTP server works.\n- [ ] Data files copied with original names and directory structure.\n- [ ] Required interactions implemented (tooltips, click-linking, legend, etc.).\n- [ ] Conditional carve-outs (e.g., no tooltip for ETFs) implemented as early returns.\n- [ ] **No background HTTP server, jsdom, Playwright, or headless browser is still running.** Common ports (8000\u002F8080\u002F8765\u002F3000\u002F5000) are free.\n- [ ] No stray processes: `pgrep -af 'http.server|playwright|chromium|node'` shows nothing you started.\n","# D3.js Visualization Skill\n\nUse this skill to turn structured data (CSV\u002FTSV\u002FJSON) into **clean, reproducible** visualizations using **D3.js**. The goal is to produce **stable outputs** that can be verified by diffing files, hashing, or by an automated browser-based test harness (e.g., Playwright\u002Fjsdom).\n\n## When to use\n\nActivate this skill when the user asks for any of the following:\n\n- \"Make a chart\u002Fplot\u002Fgraph\u002Fvisualization\"\n- bar\u002Fline\u002Fscatter\u002Fbubble\u002Farea\u002Fhistogram\u002Fbox\u002Fviolin\u002Fheatmap\n- timelines, small multiples, faceting\n- axis ticks, scales, legends, tooltips\n- data-driven SVG output for a report or web page\n- converting data to a static SVG or HTML visualization\n- interactive dashboards linking multiple views (e.g., chart + table, click-to-highlight)\n\nIf the user only needs a quick table or summary, **don't** use D3—use a spreadsheet or plain markdown instead.\n\n---\n\n## Inputs you should expect\n\n- One or more local data files: `*.csv`, `*.tsv`, `*.json`\n- A chart intent:\n  - chart type (or you infer the best type)\n  - x\u002Fy fields and aggregation rules\n  - sorting\u002Ffiltering rules\n  - dimensions (width\u002Fheight) and margins\n  - color rules (categorical \u002F sequential)\n  - any labeling requirements (title, axis labels, units)\n- Output constraints:\n  - \"static only\", \"no animation\", \"must be deterministic\", \"offline\", exact output paths, exact D3 major version, etc.\n\nIf details are missing, **make reasonable defaults** and document them in comments near the top of the output file.\n\n### Honor task-specified paths and versions\n\nWhen the task specifies **any** of the following, they override the defaults in this skill:\n\n- Output directory \u002F file names (e.g., `\u002Froot\u002Foutput\u002Findex.html`, `output\u002Fjs\u002Fvisualization.js`).\n- D3 **major version** (e.g., v6 vs v7). Download the matching minified bundle to the exact filename the task requests (e.g., `js\u002Fd3.v6.min.js`). Do **not** substitute a different major version.\n- Data-copy requirements (\"copy input data into `output\u002Fdata\u002F`\"). Copy the files exactly, preserving subdirectory structure and file names (including case) so relative paths in the HTML resolve.\n\nA quick self-check before you finish:\n\n- [ ] Every path listed in the task exists on disk.\n- [ ] The D3 file is the requested major version (grep the file for `d3.js v6` or `d3.js v7`).\n- [ ] Data files referenced by your JS exist under the copied `data\u002F` tree with matching case.\n\n---\n\n## Outputs you should produce\n\nWhen the task does not specify paths, prefer producing **all of** the following:\n\n1. `dist\u002Fchart.html` — standalone HTML that renders the visualization\n2. `dist\u002Fchart.svg` — exported SVG (stable and diff-friendly)\n3. (Optional) `dist\u002Fchart.png` — if the task explicitly needs a raster image\n\nWhen the task **does** specify paths (common for web-app tasks), follow them exactly. A typical layout requested by tasks:\n\n```\noutput\u002F\n  index.html\n  js\u002F\n    d3.v6.min.js         # pinned D3, exact filename from task\n    visualization.js     # your code\n  css\u002F\n    style.css\n  data\u002F                  # copies of input data, same structure as source\n```\n\n---\n\n## Determinism rules (non-negotiable)\n\nTo keep results stable across runs and machines:\n\n### Data determinism\n- **Sort** input rows deterministically before binding to marks (e.g., by x then by category).\n- Use stable grouping order (explicit `Array.from(grouped.keys()).sort()`).\n- Avoid locale-dependent formatting unless fixed (use `d3.format`, `d3.timeFormat` with explicit formats).\n\n### Rendering determinism\n- **No randomness**: do not use `Math.random()` or `d3-random`.\n- **No transitions\u002Fanimations** by default (transitions can introduce timing variance).\n- **Fixed** `width`, `height`, `margin`, `viewBox`.\n- Use **explicit tick counts** only when needed; otherwise rely on D3 defaults but keep domains fixed.\n- Avoid layout algorithms with non-deterministic iteration unless you control seeds\u002Fiterations (e.g., force simulation). If a force layout is required:\n  - fix the tick count (e.g., run 300 warm-up ticks with `simulation.tick()` then let it continue for user interaction),\n  - fix initial positions deterministically (e.g., sorted nodes placed on a grid or on per-cluster centers),\n  - use deterministic cluster\u002Fattractor centers (e.g., points on a circle around the chart center),\n  - always add `forceCollide` when circles must not overlap.\n\n### Offline + dependency determinism\n- Do **not** load D3 from a CDN.\n- Pin D3 to the **major version the task requests** (default when unspecified: **d3@7.9.0**). Common task requests: `d3.v6.min.js`, `d3.v7.min.js`.\n- Vendor the minified D3 bundle at the exact path the task asks for (e.g., `js\u002Fd3.v6.min.js`, `vendor\u002Fd3.v7.9.0.min.js`).\n\n### File determinism\n- Stable SVG output:\n  - Avoid auto-generated IDs that may change.\n  - If you must use IDs (clipPath, gradients), derive them from stable strings (e.g., `\"clip-plot\"`).\n- Use LF line endings.\n- Keep numeric precision consistent (e.g., round to 2–4 decimals if needed).\n\n---\n\n## Serving the page & process hygiene (READ BEFORE FINISHING)\n\nD3 loaders like `d3.csv`, `d3.json`, `d3.tsv` use `fetch`, which browsers block on the `file:\u002F\u002F` scheme (CORS). Automated verifiers therefore usually spin up a **static HTTP server on a fixed port** (e.g., 8000, 8080, 8765) and drive a headless browser (Playwright\u002Fjsdom) against it.\n\nThat has two consequences for you:\n\n### 1. Design for HTTP serving, not file:\u002F\u002F\n\n- Use **relative** URLs in your HTML\u002FJS (`js\u002Fd3.v6.min.js`, `data\u002Fstock-descriptions.csv`), never absolute filesystem paths.\n- Do not hard-code `http:\u002F\u002Flocalhost:PORT`.\n- Preserve the case of data file names exactly as they appear on disk (case-sensitive on Linux).\n\n### 2. Do NOT leave background servers or browsers running\n\nIf you start a local HTTP server, jsdom instance, Playwright browser, or any long-lived process to self-verify your work, you **must fully tear it down before you finish**. A verifier that tries to `bind()` the same port will fail all browser-based tests with `OSError: [Errno 98] Address already in use`.\n\nSafe pattern:\n\n```bash\n# start\npython3 -m http.server 8000 --bind 127.0.0.1 > \u002Ftmp\u002Fhttpd.log 2>&1 &\nSERVER_PID=$!\n\n# ... run your check ...\n\n# stop — always run this before you finish, even on failure\nkill \"$SERVER_PID\" 2>\u002Fdev\u002Fnull || true\nwait \"$SERVER_PID\" 2>\u002Fdev\u002Fnull || true\n# belt-and-suspenders: kill any stragglers on that port\nfuser -k 8000\u002Ftcp 2>\u002Fdev\u002Fnull || true\n```\n\nBefore your final message, run a check equivalent to:\n\n```bash\nss -ltn 2>\u002Fdev\u002Fnull | awk '{print $4}' | grep -E ':(8000|8080|8765|3000|5000)$' && echo \"PORT STILL BOUND — kill it\" || echo \"ports clear\"\npgrep -af 'http.server|node .*jsdom|playwright|chromium' || echo \"no stray processes\"\n```\n\nIf anything is still bound, kill it. **Leaving a server bound to a common port is one of the most frequent causes of a 0.0 reward on browser-based verifiers even when the artifacts themselves are correct.**\n\n### 3. Prefer non-networked self-checks when possible\n\nIf you just want to sanity-check the JS, you can often skip the server entirely:\n\n- Parse the CSV in Node and re-run the transformation logic directly.\n- Or use jsdom with `runScripts: 'dangerously'` and inject the CSV text via `d3.csvParse` instead of `d3.csv` (no fetch needed).\n\nThis avoids opening any port at all.\n\n---\n\n## Recommended project layout (when task does not specify)\n\n```\ndist\u002F\n  chart.html        # standalone HTML with inline or linked JS\u002FCSS\n  chart.svg         # exported SVG (optional but nice)\n  chart.png         # rasterized (optional)\nvendor\u002F\n  d3.v7.9.0.min.js  # pinned D3 library\n```\n\n---\n\n## Interactive features (tooltips, click handlers, hover effects)\n\nWhen the task requires interactivity (e.g., tooltips on hover, click to highlight, linked views):\n\n### Tooltip pattern (recommended)\n\n1. **Create a tooltip element** in HTML:\n```html\n\u003Cdiv id=\"tooltip\" class=\"tooltip\">\u003C\u002Fdiv>\n```\n\n2. **Style with CSS** using `.visible` class for show\u002Fhide:\n```css\n.tooltip {\n    position: absolute;\n    padding: 10px;\n    background: rgba(0, 0, 0, 0.8);\n    color: white;\n    border-radius: 4px;\n    pointer-events: none;  \u002F* Prevent mouse interference *\u002F\n    opacity: 0;\n    transition: opacity 0.2s;\n    z-index: 1000;\n}\n\n.tooltip.visible {\n    opacity: 1;  \u002F* Show when .visible class is added *\u002F\n}\n```\n\n3. **Add event handlers** to SVG elements:\n```javascript\nsvg.selectAll('circle')\n    .on('mouseover', function(event, d) {\n        d3.select('#tooltip')\n            .classed('visible', true)\n            .html(`\u003Cstrong>${d.name}\u003C\u002Fstrong>\u003Cbr\u002F>${d.value}`)\n            .style('left', (event.pageX + 10) + 'px')\n            .style('top', (event.pageY - 10) + 'px');\n    })\n    .on('mouseout', function() {\n        d3.select('#tooltip').classed('visible', false);\n    });\n```\n\n**Key points:**\n- Use `opacity: 0` by default (not `display: none`) for smooth transitions.\n- Use `.classed('visible', true\u002Ffalse)` to toggle visibility.\n- `pointer-events: none` prevents tooltip from blocking mouse events.\n- Position tooltip relative to mouse with `event.pageX\u002FpageY`.\n\n### Click handlers for selection\u002Fhighlighting\n\n```javascript\nsvg.selectAll('.bar')\n    .on('click', function(event, d) {\n        d3.selectAll('.bar').classed('selected', false);\n        d3.select(this).classed('selected', true);\n    });\n```\n\nCSS for highlighting:\n```css\n.bar.selected {\n    stroke: #000;\n    stroke-width: 3px;\n}\n```\n\n### Linked views (chart ↔ table)\n\nWhen the task asks that clicking a mark highlights a row and vice versa, use a single **selection state** shared by both renderers:\n\n```javascript\nlet selectedKey = null;\nfunction select(key) {\n    selectedKey = (key === selectedKey) ? null : key;\n    updateChartHighlight(selectedKey);\n    updateTableHighlight(selectedKey);\n}\n\u002F\u002F both bubble click and row click call select(d.ticker)\n```\n\nExpose a stable class name (e.g., `.selected`) on both the SVG element and the `\u003Ctr>` so the verifier can detect the linkage.\n\n### Conditional interactivity\n\nSome marks should not be interactive (e.g., ETFs in a stock task have no tooltip data):\n```javascript\n.on('mouseover', function(event, d) {\n    if (d.sector === 'ETF' || d.marketCap == null) return;  \u002F\u002F no tooltip\n    showTooltip(event, d);\n});\n```\nRead the task carefully for these \"do not show for X\" carve-outs and implement the early return explicitly.\n\n---\n\n## Pre-finish checklist\n\nBefore returning to the user, verify each item:\n\n- [ ] All files listed in the task exist at the exact paths.\n- [ ] D3 file is the requested major version.\n- [ ] HTML uses **relative** paths; opening via a static HTTP server works.\n- [ ] Data files copied with original names and directory structure.\n- [ ] Required interactions implemented (tooltips, click-linking, legend, etc.).\n- [ ] Conditional carve-outs (e.g., no tooltip for ETFs) implemented as early returns.\n- [ ] **No background HTTP server, jsdom, Playwright, or headless browser is still running.** Common ports (8000\u002F8080\u002F8765\u002F3000\u002F5000) are free.\n- [ ] No stray processes: `pgrep -af 'http.server|playwright|chromium|node'` shows nothing you started.\n",{"name":5,"description":7},"main","cdcb6d230f3b15c3c33f8a2bdd16439f43602cbe","evaluation\u002Fresults\u002FSkillAxe-Opus47-Gold15-20260921\u002Ftasks\u002Fdata-to-d3\u002Frepaired_run\u002Finputs\u002Fskills\u002Fd3-visualization",1,"https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark","https:\u002F\u002Fgithub.com\u002Flinyouxue","2026-11-14 20:28:35",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add linyouxue\u002Fskill-repair-benchmark --skill d3-visualization",{"tool":37,"command":38},"bunx","bunx skills add linyouxue\u002Fskill-repair-benchmark --skill d3-visualization",{"tool":40,"command":41},"pnpm","pnpm dlx skills add linyouxue\u002Fskill-repair-benchmark --skill d3-visualization","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fevaluation\u002Fresults\u002FSkillAxe-Opus47-Gold15-20260921\u002Ftasks\u002Fdata-to-d3\u002Frepaired_run\u002Finputs\u002Fskills\u002Fd3-visualization\u002FSKILL.md",true,[45,51,55,59],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"scripts\u002Fbubble_chart_example.js","SCRIPT","脚本",3679,"https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fevaluation\u002Fresults\u002FSkillAxe-Opus47-Gold15-20260921\u002Ftasks\u002Fdata-to-d3\u002Frepaired_run\u002Finputs\u002Fskills\u002Fd3-visualization\u002Fscripts\u002Fbubble_chart_example.js",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"scripts\u002Fcheck_tooltip.js",1752,"https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fevaluation\u002Fresults\u002FSkillAxe-Opus47-Gold15-20260921\u002Ftasks\u002Fdata-to-d3\u002Frepaired_run\u002Finputs\u002Fskills\u002Fd3-visualization\u002Fscripts\u002Fcheck_tooltip.js",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"scripts\u002Finteractive_table_example.js",4439,"https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fevaluation\u002Fresults\u002FSkillAxe-Opus47-Gold15-20260921\u002Ftasks\u002Fdata-to-d3\u002Frepaired_run\u002Finputs\u002Fskills\u002Fd3-visualization\u002Fscripts\u002Finteractive_table_example.js",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"scripts\u002Ftooltip_handler.js",5741,"https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fevaluation\u002Fresults\u002FSkillAxe-Opus47-Gold15-20260921\u002Ftasks\u002Fdata-to-d3\u002Frepaired_run\u002Finputs\u002Fskills\u002Fd3-visualization\u002Fscripts\u002Ftooltip_handler.js",[64,71,78,85,90,95],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7E1HGVRY73NBJ022CJG13X6","video-frame-extraction","Extract frames from video files and save them as images using OpenCV","https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fjpg-ocr-stat\u002Fresult\u002Fskilltta-claude4.7\u002Fgroup_03\u002Frun_03\u002Finputs\u002Fskills\u002Fvideo-frame-extraction\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7E1HAG5R7CJ9C8NYJS771MB","openai-vision","Analyze images and multi-frame sequences using OpenAI GPT vision models","https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fjpg-ocr-stat\u002Fresult\u002Fskilltta-claude4.7\u002Fgroup_03\u002Frun_03\u002Finputs\u002Fskills\u002Fopenai-vision\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7E1H7DADKB6QBWKC2KQ63SZ","image-ocr","Extract text content from images using Tesseract OCR via Python, including structured field extraction from receipts and forms","https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fjpg-ocr-stat\u002Fresult\u002Fskilltta-claude4.7\u002Fgroup_03\u002Frun_03\u002Finputs\u002Fskills\u002Fimage-ocr\u002FSKILL.md",[],[],{"skillNo":86,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7E1H0WBNT43TENGQY7AVZHD","https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fjpg-ocr-stat\u002Fresult\u002Fskilltta-claude4.7\u002Fgroup_03\u002Frun_02\u002Finputs\u002Fskills\u002Fvideo-frame-extraction\u002FSKILL.md",[],[],{"skillNo":91,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7E1GTC7D4N4Q2EF03875J9E","https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fjpg-ocr-stat\u002Fresult\u002Fskilltta-claude4.7\u002Fgroup_03\u002Frun_02\u002Finputs\u002Fskills\u002Fopenai-vision\u002FSKILL.md",[],[],{"skillNo":96,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7E1GQ92CWFMGH53KSSE4WER","https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fjpg-ocr-stat\u002Fresult\u002Fskilltta-claude4.7\u002Fgroup_03\u002Frun_02\u002Finputs\u002Fskills\u002Fimage-ocr\u002FSKILL.md",[],[]]