Skip to content
Back to skills

Trend Radar Heatmap Figures

ASecurity

"Build publication-ready trend panels, event-annotated cumulative

  • 247 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 8, 2026
testinggo

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned September 8, 2026

npx -y skills add VectorSpaceLab/AREX-Skill --skill trend-radar-heatmap-figures --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Trend Radar Heatmap Figures?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Trend Radar Heatmap Figures
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vectorspacelab-trend-radar-heatmap-figures/badge)](https://www.skillsdirectory.com/skills/vectorspacelab-trend-radar-heatmap-figures)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: trend-radar-heatmap-figures
description: "Build publication-ready trend panels, event-annotated cumulative
  time series, normalized radar comparisons, heatmaps, matrix panels, and shared
  legends."
disable-model-invocation: true
metadata:
  disco-role: operating
license: NO_LICENSE
---

# Trend, Radar, and Heatmap Figures

Use this sub-skill when a figures4papers task asks for publication-ready matplotlib figures involving line or sweep curves, cumulative time series, event annotations, radar/polar benchmark comparisons, seaborn or matplotlib heatmaps, matrix-style comparison panels, colorbars, per-cell labels, or shared/legend-only layouts.

## Route here for

- Line, sweep, post-training, or ablation curves with 2-4 readable series per axis.
- Cumulative time-series panels with parsed month/date labels, filled areas, hatch overlays, and event arrows.
- Radar or polar benchmark comparisons where each spoke has its own natural score scale and tick labels.
- Heatmaps with row/column totals, colorbars, annotations, per-cell text contrast, or summary/improvement rows.
- Wide comparison panels that mix trends, heatmaps, matrix blocks, and a dedicated shared-legend axis.

## Route elsewhere

- Grouped bars, horizontal ablation bars, log bars, or print-safe bar comparisons: use `bar-comparison-figures`.
- Conceptual manifolds, spheres, scatter clouds, KDE contours, Swiss-roll diagrams, or schematic arrows: use `concept-manifold-diagrams`.
- Cross-cutting palette, font, export, and environment helpers: use the root figures4papers references/scripts when they are available; this sub-skill does not require them.

## Read or run

- Read [references/trend-radar-heatmap-recipes.md](references/trend-radar-heatmap-recipes.md) before implementing any trend, radar, heatmap, matrix, colorbar, or shared-legend figure. It contains the data contracts, normalization formulas, date/event handling, layout recipes, and output validation checklist.
- Read [references/troubleshooting.md](references/troubleshooting.md) when the figure has shape mismatches, date/event problems, malformed radar polygons, bad tick labels, unreadable heatmap text, colorbar issues, optional TeX/seaborn failures, or missing output files.
- Run [scripts/trend_radar_heatmap_template.py](scripts/trend_radar_heatmap_template.py) to create safe built-in examples for `--example trend`, `--example radar`, or `--example heatmap`. Use it as a self-contained starting point when no project-specific plotting code exists.

## Operating checklist

1. Identify the figure family: trend/event, radar, heatmap, matrix panel, or mixed layout.
2. Validate the data contract from the recipes before plotting: array rank, label counts, method/order alignment, finite numeric values, and date coverage.
3. Keep figures self-contained and headless-friendly: no network, credentials, hidden global state, or dependence on external source checkouts.
4. Prefer non-TeX defaults. Enable TeX only when the runtime explicitly has a LaTeX installation and the target venue requires TeX-rendered labels.
5. Save with deterministic output names and verify that every requested file exists, is non-empty, and can be opened by matplotlib/Pillow or a simple file-size check.

Files in this skill

  • SKILL.md3.2 KB
  • references/trend-radar-heatmap-recipes.md9.1 KB
  • references/troubleshooting.md6.7 KB
  • scripts/trend_radar_heatmap_template.py20.3 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.