Skip to main content
Agent skill

Social Media Matrix Tracker Template

社媒矩阵数据追踪面板模板(Social Media Matrix Tracker)。 Use when users ask for a cinematic, data-dense social media analytics dashboard with multi-platform metrics, interactive charts, hover insights, range compare, and dark/light theme switching in a single HTML artifact.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Social Media Matrix Tracker Template when an AI agent needs a reusable SKILL.md workflow for this job: 社媒矩阵数据追踪面板模板(Social Media Matrix Tracker)。 Use when users ask for a cinematic, data-dense social media analytics dashboard with multi-platform metrics, interactive charts, hover insights, range compare, and dark/light theme switching in a single HTML artifact.

When not to use it

Skip Social Media Matrix Tracker Template when the task is outside the analysis category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/social-media-matrix-tracker-template
# Save SKILL.md to ~/.claude/skills/social-media-matrix-tracker-template/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/social-media-matrix-tracker-template/SKILL.md. For a shared project, commit the folder at .claude/skills/social-media-matrix-tracker-template/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Social Media Matrix Tracker Template skill for this task: Read active DESIGN.md first, map tokens to CSS variables, then adapt assets/template.html. Confirm any required inputs or files before making changes.

What supports this recommendation?

83/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
92/100
Practical detail
92/100
Source evidence
63/100
Source signals
72/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Social Media Matrix Tracker Template

Ship a premium, cinematic social-media analytics template with high data density and production-grade micro-interactions.

## Resource map

```text social-media-matrix-tracker-template/ ├── SKILL.md ├── assets/ │ └── template.html ├── references/ │ └── checklist.md └── example.html ```

## Workflow

1. Read active `DESIGN.md` first, map tokens to CSS variables, then adapt `assets/template.html`. 2. Keep the structural information architecture intact: hero + platform matrix + KPI strip + multi-chart deep sections. 3. Preserve interaction fidelity: - dark/light theme toggle - hover tooltip on charts (auto-clamps inside viewport) - click-to-pin chart point - drag interval analysis - Shift+drag multi-range compare - insights panel live updates on every chart (line / stack / donut / geo) - touch + keyboard arrow-key support for line charts (a11y) 4. Ensure template remains self-contained (single HTML with inline CSS/JS, no framework dependency). 5. Keep default sample data realistic and internally consistent across cards/charts. 6. Validate with `references/checklist.md` before emitting the artifact.

### Adapting the sample data safely

`assets/template.html` ships with hand-tuned sample arrays. When swapping in real data, follow this contract so charts and insights stay coherent:

- Replace **whole arrays at once**, not individual indices — line charts assume `values[]` and `xLabels[]` are the same length and aligned by index. - Match the existing **unit + decimals**: `hourChart` (engagements / `decimals: 0`), `slaChart` (minutes / `decimals: 0`), `roiChart` (multiplier x / `decimals: 1`), `cohortChart` (% / `decimals: 0`). Mismatched units break tooltip + A/B insight copy. - Keep all four line series the **same length** (default 7 points). Different lengths leak into the A/B compare which expects shared indices. - For `mixChart`, every `bars[i].stack` must remain a 3-element array (`[Video, Thread, Carousel]`). For `sentimentChart`, `arcs[]` percentages should sum to 100. - Update KPI strip + platform card metrics in lock-step — the artifact's "Live overview" insight derives from the same numbers. - Single-data-point datasets are guarded (drawn as a labelled dot) but degrade UX; prefer ≥ 3 points per chart when adapting.

## Output contract

Emit one short sentence before the artifact (e.g. *"Cinematic social media matrix tracker — dark theme by default, all interactions live."*) and then a single self-contained HTML artifact.

- The artifact **must** use the `<artifact>` wrapper exactly as shown below — the daemon parser keys on the wrapper element. - `identifier="social-media-matrix-tracker"` is the canonical id (don't suffix with project name). - `type="text/html"` and `title` are required. - Inline CSS + JS only. No external framework / CDN. No external font imports beyond what `template.html` already declares. - The final document is the **adapted** `template.html` (with DESIGN.md tokens applied), not a verbatim copy and not a separate `index.html`. Do not emit both.

```xml <artifact identifier="social-media-matrix-tracker" type="text/html" title="Social Media Matrix Tracker"> <!doctype html> <html>...</html> </artifact> ```

Intended uses

  • Read active DESIGN.md first, map tokens to CSS variables, then adapt assets/template.html.
  • Keep the structural information architecture intact: hero + platform matrix + KPI strip + multi-chart deep sections.
  • Preserve interaction fidelity:
  • dark/light theme toggle
  • hover tooltip on charts (auto-clamps inside viewport)
  • click-to-pin chart point
  • drag interval analysis
  • Shift+drag multi-range compare
  • insights panel live updates on every chart (line / stack / donut / geo)
  • touch + keyboard arrow-key support for line charts (a11y)
  • Ensure template remains self-contained (single HTML with inline CSS/JS, no framework dependency).
  • Keep default sample data realistic and internally consistent across cards/charts.
  • Validate with references/checklist.md before emitting the artifact.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.