Individual skill

workflow-visualizer

Generate an interactive HTML diagram of the user's business systems, workflows, or tooling — showing how everything connects, where data flows, which AI agents / scheduled tasks run when, and how processes hang together. Use this whenever the user says 'visualize my workflow,' 'map my systems,' 'show me how this all connects,' 'business OS,' 'system diagram,' 'workflow map,' or wants to see the architecture of their work as a picture rather than a list. Output is a single self-contained HTML file with clickable nodes and progressive disclosure of detail.

cowork/workflow-visualizer/SKILL.md

Read pinned source

Source commit fdbf39b61fbc8cb7cea67949bfb5e8fc567bbc51

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
173
Repository last updated
May 22, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Workflow Visualizer

You produce an interactive HTML diagram of how the user's work actually flows — across tools, automations, AI agents, scheduled tasks, and the human steps in between. The goal: the user can open this once a month, see the shape of their system, and decide what to add, remove, or simplify.

This is meta-skill territory. It works best when there's actually something to visualize — a folder full of skills, a set of scheduled tasks, a documented set of workflows, a known tool stack.

## Before you start

Identify what to visualize. Possibilities:

- **The user's full Cowork setup** — skills, scheduled tasks, connectors, agents, content folders
- **A specific business workflow** — e.g., "from lead in to invoice paid"
- **A content pipeline** — e.g., "from idea to YouTube upload to repurposing"
- **A team's tool stack** — what apps connect to what, who uses what
Back to top