domains / families / data / plotly

plotly

combined

Interactive visualization library for Python. Use it when you need hover tooltips, zoom/pan, selection, animations, or charts embeddable in web pages (e.g., dashboards, exploratory analysis, presentations). Plotly interactive visualization. Express and Graph Objects: scatter, line, bar, heatmap, 3D, geographic charts; subplots; styling; export. Use when interactivity (hover/zoom) is needed. For static figures use plotnine; for GIS use geopandas.

When to use

• Use this skill when the request matches its documented task boundary.
• Use it when the user can provide the required inputs and expects a structured deliverable.
• Prefer this skill for repeatable, checklist-driven execution rather than open-ended brainstorming.
• You need interactive charts with hover, zoom, pan, or web embedding.
• You are building dashboards, exploratory analysis notebooks, or presentations that benefit from rich interaction.
• You want to choose between Plotly Express and Graph Objects for the same visualization task.

When not to use

• Do not use this skill when the required source data, identifiers, files, or credentials are missing.
• Do not use this skill when the user asks for fabricated results, unsupported claims, or out-of-scope conclusions.
• Do not use this skill when a simpler direct answer is more appropriate than the documented workflow.
• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The first two copies (Vibe-Skills and agentic-awesome-skills) are nearly identical, providing a standard, general-purpose guide to Plotly with code examples for Express and Graph Objects. The third copy (medical-research-skills) adds specific version constraints and a generic 'checklist-driven' execution model. The fourth copy (Auto-Empirical-Research-Skills) is distinct: it mandates a 'file-first' execution protocol for research pipelines (writing scripts to specific directories before execution) and explicitly forbids the use of Kaleido for static image export due to environment constraints, recommending plotnine instead. This creates a conflict with the other copies, which recommend installing Kaleido for static exports. Because the fourth copy contains a critical environmental constraint and workflow protocol that the others lack, and the others contain general code examples the fourth copy omits in favor of reference files, they must be combined to provide a complete and non-contradictory instruction set.