skills/marketing/viz/SKILL.md
Transforms content (URLs, uploaded documents, pasted text, meeting transcripts) into professional visualizations across four output modes. Accepts a mode argument or a keyword trigger in the user message. Mode "diagram" produces an Excalidraw diagram via Excalidraw:create_view. Mode "infographic" generates a Swiss Pulse PNG via the Gemini image-generation API. Mode "visualize" renders an inline Visualizer widget (SVG or HTML) via visualize:show_widget. Mode "publish" ships an interactive Swiss Pulse HTML visual to HeyGenverse via HeyGenverse:create_app and returns a shareable link. Keywords that activate the skill: "diagram it", "excalidraw this", "draw a diagram of this", "nano this", "vis it", "ver it", "hey it", "heygenverse this". Do not use for plain-text summaries, code explanations, prose responses, or generic chat visualizations without a chosen output format.
npx skillsauth add pedronauck/skills vizInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Transform any content into a professional visualization via one of four output modes. This skill is a dispatcher: it resolves the active mode, loads the mode-specific workflow from references/, and executes it.
Inspect the invocation in this priority order:
Positional argument. The first positional argument is $0. If $0 matches diagram, infographic, visualize, or publish, use it as the mode. Remaining arguments ($ARGUMENTS after the mode token) are the optional content reference (URL, file path, or inline text).
Keyword trigger. If $0 is empty or not a valid mode, scan the most recent user message for a trigger keyword and map it to a mode:
| Trigger keyword(s) | Mode |
| ----------------------------------------------------------------------------- | ------------- |
| "diagram it", "excalidraw this", "draw a diagram of this" | diagram |
| "nano this" | infographic |
| "vis it" | visualize |
| "ver it", "hey it", "heygenverse this", "put this on heygenverse as a visual" | publish |
Ask the user. If neither signal yields a mode, stop and ask which output to produce — diagram (Excalidraw), infographic (Swiss Pulse PNG via Gemini), visualize (inline Visualizer widget), or publish (interactive Swiss Pulse app on HeyGenverse). Do not guess.
Invocation context injected at render time: mode token is $0, content reference is $ARGUMENTS.
Read the reference file for the resolved mode and follow its workflow end-to-end:
| Mode | Workflow file |
| ------------- | -------------------------------- |
| diagram | references/mode-diagram.md |
| infographic | references/mode-infographic.md |
| visualize | references/mode-visualize.md |
| publish | references/mode-publish.md |
Read the file on every invocation — do not execute from memory — so any updates to the workflow are applied.
All four modes accept content from the same sources. Resolve the content target in this priority order:
$ARGUMENTS contains a URL → retrieve via web_fetch. If blocked (429/403), fall back to web_search with key phrases to get the content from search snippets.$ARGUMENTS points to an uploaded file → read from /mnt/user-data/uploads/ using pdfplumber for PDF, python-docx for DOCX, pandas for CSV/TSV, direct read for TXT/MD/HTML.$ARGUMENTS is inline text → use it directly./mnt/transcripts/, pasted text) and use that.Summarize to core structure if the content exceeds 3,000 words for modes that pipe text into an LLM (infographic) or 5,000 words for modes that assemble visuals client-side (diagram, visualize, publish).
Follow the steps in the loaded workflow file exactly. Do not substitute tools, colors, typography, or output formats across modes.
mode=publish was requested).references/mode-<mode>.md).Excalidraw:*, visualize:*, HeyGenverse:*) → report the specific missing integration and ask whether to proceed with an alternative mode.GEMINI_API_KEY (mode infographic only) → stop and ask for the key before continuing.testing
Assess DDD fit; discover domains with EventStorming, define language and bounded contexts, and design aggregates, value objects, events, and repositories. Excludes architecture-only audits, product specs, and CQRS/Event Sourcing catalogs.
development
Build terminal UIs with ratatui following 2026 Rust best practices. Use when: (1) Creating new TUI apps, (2) Adding widgets/layouts, (3) Keyboard navigation/state management, (4) Image integration via ratatui-image, (5) Async event handling, (6) Release optimization. Covers v0.30.0+ API, Elm Architecture, StatefulWidget, color-eyre.
development
Find 10x product opportunities and high-leverage improvements. Use when user wants strategic product thinking, mentions '10x', wants to find high-impact features, or says 'what would make this 10x better', 'product strategy', or 'what should we build next'.
development
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.