Schedule
TinyAGI/tinyagi
Create, list, and delete scheduled tasks (recurring or one-time) that send messages to agents.
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…
Install Workflow Visualizer
$ npx skills add TheCraigHewitt/skills --skill workflow-visualizer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install TheCraigHewitt/skills workflow-visualizer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cowork/workflow-visualizer .claude/skills/workflow-visualizer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "workflow-visualizer" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/cowork/workflow-visualizer into .claude/skills/workflow-visualizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-visualizer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/TheCraigHewitt/skills/tree/main/cowork/workflow-visualizerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add TheCraigHewitt/skills --skill workflow-visualizer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install TheCraigHewitt/skills workflow-visualizer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cowork/workflow-visualizer .agents/skills/workflow-visualizer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "workflow-visualizer" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/cowork/workflow-visualizer into .agents/skills/workflow-visualizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-visualizer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add TheCraigHewitt/skills --skill workflow-visualizer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install TheCraigHewitt/skills workflow-visualizer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cowork/workflow-visualizer .cursor/skills/workflow-visualizer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "workflow-visualizer" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/cowork/workflow-visualizer into .cursor/skills/workflow-visualizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-visualizer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/TheCraigHewitt/skills.git --path cowork/workflow-visualizer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add TheCraigHewitt/skills --skill workflow-visualizer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install TheCraigHewitt/skills workflow-visualizer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cowork/workflow-visualizer .gemini/skills/workflow-visualizer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "workflow-visualizer" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/cowork/workflow-visualizer into .gemini/skills/workflow-visualizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-visualizer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install TheCraigHewitt/skills workflow-visualizerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add TheCraigHewitt/skills --skill workflow-visualizer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/cowork/workflow-visualizer .github/skills/workflow-visualizer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "workflow-visualizer" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/cowork/workflow-visualizer into .github/skills/workflow-visualizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-visualizer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add TheCraigHewitt/skills --skill workflow-visualizer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install TheCraigHewitt/skills workflow-visualizer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cowork/workflow-visualizer .opencode/skills/workflow-visualizer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "workflow-visualizer" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/cowork/workflow-visualizer into .opencode/skills/workflow-visualizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-visualizer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
workflow-visualizer- GitHub stars
- 157
- Token cost
- ~1.6k tokens
- SKILL.md length
- 717 words
- Files
- 2
- Skills in repo
- 65
- Repo updated
- First seen
- Licence
- MIT
At a glance
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…
- Works in 5 steps: Don't visualize the imaginary. Map what… → Less is more. A diagram with 60 nodes is… → Naming matters. Use the user's actual… → …
- Says visualize my workflow
- SKILL.md covers Before you start, Gather the inputs, The diagram structure and Interactivity, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Workflow Visualizer is an agent skill from TheCraigHewitt/skills. 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…
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `evals/evals.json`).
It sits in Productivity & Automation, covering Scheduled and recurring tasks and HTML artifacts. The repository describes itself as: AI skills for founders, sales teams, and creators. 47 skills across CEO, Sales, YouTube, and General categories. Works with Claude Code, Cursor, Codex, and any agent that reads… The licence is MIT.
When your agent uses it
- Says visualize my workflow
- Show me how this all connects
- Wants to see the architecture of their work as a picture rather than a list
Example prompts
- “visualize my workflow,”
- “map my systems,”
- “show me how this all connects,”
- “/workflow-visualizer”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Don't visualize the imaginary. Map what actually exists, not what's planned. Aspirational nodes (clearly labeled) are fine for a separate…
- Less is more. A diagram with 60 nodes is unreadable. If the system is genuinely complex, break it into 3-4 sub-diagrams and link between…
- Naming matters. Use the user's actual names for things. If their skill is called morning-briefing, that's the node label — not "AI-powered…
- Surface the zombies. The most valuable insight from a workflow map is usually "you built this thing 4 months ago and haven't used it…
- Regenerate, don't patch. When the user adds new skills or tasks, regenerate the whole map. Trying to keep a diagram in sync incrementally…
What it can do on your machine
Read from SKILL.md and the folder at commit fdbf39b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Workflow Visualizer loads about 1.6k tokens when it runs. Until then it costs about 145 tokens; SKILL.md has 717 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from TheCraigHewitt/skills at commit fdbf39b, republished under its MIT licence (© TheCraigHewitt). 717 words, ~1,558 tokens.
Download SKILL.mdSave it as
.claude/skills/workflow-visualizer/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- workflow-visualizer
- description
- 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.
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
Ask: "What are we mapping?" If the user just says "my workflow" without scope, default to: their current Cowork folder + a scan of ~/Coding/skills/ + scheduled tasks.
Gather the inputs
Scan the relevant folders. For Cowork-wide visualization, that's:
- All installed skills (and what they trigger on)
- Scheduled tasks (and when they run)
- Connector list (Gmail, Calendar, Slack, etc.)
- Recent task / chat history if accessible (what the user actually uses)
- Any
BUSINESS_CONTEXT.md,README.md, or system documentation in the folder
For a specific workflow, ask the user to walk through it once — capture the steps, the tools used, the inputs and outputs of each step, the decision points.
The diagram structure
Use a node-and-edge interactive diagram. Each node is a discrete thing — a skill, an app, a person, a scheduled task, a data store. Each edge is a relationship — data flow, trigger, dependency.
Group nodes by phase or domain. Common groupings:
- Triggers (scheduled tasks, manual prompts, incoming emails, etc.)
- Inputs (data sources, connectors, file folders)
- Processing (skills, agents, scripts)
- Outputs (artifacts produced — dashboards, emails, content)
- Storage (where things end up)
Use clear visual differentiation:
- Color by type — triggers one color, skills another, data stores a third
- Shape by category — circles for triggers, rectangles for processes, cylinders for storage
- Edge style — solid for explicit flow, dashed for optional, arrows showing direction
Interactivity
The diagram should let the user:
- Click a node — open a detail panel with: what this is, what triggers it, what it does, what it produces, related files
- Hover an edge — show what data/event flows between the nodes
- Filter by domain — show only the content pipeline, only the financial workflows, etc.
- Zoom / pan — for larger diagrams
- Search — find a node by name
Optional but powerful:
- Activity overlay — if usage data is available, color or size nodes by how often they're actually used. Surface the "I installed this 6 months ago and never used it" zombies.
- Toggle planned vs. live — if the user has aspirational nodes (something they're planning to add), let them toggle visibility.
Show full SKILL.md (247 more words)Show less
Technical implementation
Single self-contained .html file saved as workflow-map-YYYY-MM-DD.html.
Use a force-directed graph library (Mermaid for simple cases, or Cytoscape.js / vis-network for richer interaction). Embed the data as a JS object. No external dependencies that require network access at view time.
Layout tips:
- Allow manual layout — auto-layouts get cluttered fast
- Save layout positions back into the file so re-opens are consistent
- Keep the diagram navigable on a laptop screen; complex maps need pan/zoom
The companion summary
Alongside the HTML, produce a workflow-summary.md that explains the map in prose:
# Workflow map — [date]
## What this is
One paragraph: what this diagram represents.
## The shape
3-5 paragraphs walking through the system from triggers to outputs. Not a list — a narrative. "Every morning at 7am, the morning-briefing skill fires, which pulls from Gmail and Calendar connectors, and writes both to chat (for me) and to Slack. By 9am I've usually responded to a few flagged emails, which feeds into..."
## What's working
The pieces of the system that are humming.
## What's stale
Nodes that exist but aren't used. Candidates for removal.
## What's missing
Gaps you noticed — workflows the user has alluded to but no clear node handles, or obvious next-step automations.
## Suggestions
Specific moves: add this scheduled task, retire this skill, reorganize this folder.The summary is what the user actually reads. The diagram is what makes them want to read it.
Rules
- Don't visualize the imaginary. Map what actually exists, not what's planned. Aspirational nodes (clearly labeled) are fine for a separate "planned" overlay but shouldn't be mixed in by default.
- Less is more. A diagram with 60 nodes is unreadable. If the system is genuinely complex, break it into 3-4 sub-diagrams and link between them.
- Naming matters. Use the user's actual names for things. If their skill is called
morning-briefing, that's the node label — not "AI-powered daily summary generator." - Surface the zombies. The most valuable insight from a workflow map is usually "you built this thing 4 months ago and haven't used it since." Don't be polite — flag them.
- Regenerate, don't patch. When the user adds new skills or tasks, regenerate the whole map. Trying to keep a diagram in sync incrementally is a losing battle.
© TheCraigHewitt, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in cowork/workflow-visualizer of TheCraigHewitt/skills.
- SKILL.md
- evals/evals.json
Open the folder on GitHubat commit fdbf39b
Compare with similar skills
Workflow Visualizer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Workflow Visualizer this skillTheCraigHewitt/skills | 157 | — | ~1.6k | Automated safety check: Pass | MIT | |
| ScheduleTinyAGI/tinyagi | 3.6k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Send User MessageTinyAGI/tinyagi | 3.6k | — | ~829 | Automated safety check: Pass | MIT | |
| Cron Opsczl9707/build-your-own-openclaw | 1.9k | — | ~593 | Automated safety check: Pass | MIT | |
| X Bookmarkssharbelxyz/x-bookmarks | 289 | — | ~2k | Automated safety check: Notes | None | |
| Jobsphysiclaw/PhysiClaw | 386 | 1 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Send User Message
TinyAGI/tinyagi
Send a proactive message to a paired user via their channel (Discord, Telegram, or WhatsApp).
Cron Ops
czl9707/build-your-own-openclaw
Create, list, and delete scheduled cron jobs. An agent skill from czl9707/build-your-own-openclaw.
X Bookmarks
sharbelxyz/x-bookmarks
Fetch, summarize, and manage X/Twitter bookmarks via bird CLI or X API v2.
Jobs
physiclaw/PhysiClaw
A skill your agent uses when the task involves scheduling future work — any "remind me at …", "every weekday …", "check again in 30 min", or closing a fired cron job.
Wp Wpcli And Ops
Automattic/agent-skills
A skill your agent uses when working with WP-CLI (wp) for WordPress operations: safe search-replace, db export/import, plugin/theme/user/content management, cron, cache flushing, multisite, and…
More from TheCraigHewitt/skills
All 65 skills in this repoCarousels
TheCraigHewitt/skills
Turns a piece of Craig's content (an email, a YouTube script, an essay, or pasted text) into a polished image carousel publishable to both LinkedIn and Instagram from one set of 1080x1350 slides.
Audience Research
TheCraigHewitt/skills
When the user wants to understand their YouTube audience, mine viewer psychology, analyze demographics, or find content-market fit signals.
Brain Dump
TheCraigHewitt/skills
Take a messy stream-of-consciousness dump from the user (typed or transcribed from voice) and turn it into a structured set of projects, tasks, and connections to existing work.
Channel Audit
TheCraigHewitt/skills
When the user wants a full YouTube channel health check, growth diagnosis, strategic review, or wants to identify why their channel is stalling.
Channel Strategy
TheCraigHewitt/skills
When the user wants to define or refine their YouTube channel strategy, niche positioning, content pillars, or growth plan.
Cold Call
TheCraigHewitt/skills
When the user wants to write cold call scripts, handle phone objections, plan dial blocks, or craft voicemails.
Related
Categories
Questions about Workflow Visualizer
What does Workflow Visualizer do?
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…. Workflow Visualizer is an agent skill from TheCraigHewitt/skills. 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.
When should I use Workflow Visualizer?
Workflow Visualizer fits situations like: says visualize my workflow; show me how this all connects; wants to see the architecture of their work as a picture rather than a list.
How do I install Workflow Visualizer in Claude Code?
Run `npx skills add TheCraigHewitt/skills --skill workflow-visualizer -a claude-code`. Or copy the skill folder (cowork/workflow-visualizer in TheCraigHewitt/skills) into .claude/skills/workflow-visualizer in your project. Claude Code loads it when a task matches its description.
How do I install Workflow Visualizer in Codex?
Run `npx skills add TheCraigHewitt/skills --skill workflow-visualizer -a codex`. Or copy the skill folder (cowork/workflow-visualizer in TheCraigHewitt/skills) into .agents/skills/workflow-visualizer in your project. Codex loads it when a task matches its description.
Can I use Workflow Visualizer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add TheCraigHewitt/skills --skill workflow-visualizer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workflow-visualizer, .gemini/skills/workflow-visualizer, .github/skills/workflow-visualizer and .opencode/skills/workflow-visualizer in your project.
What does Workflow Visualizer need to run?
SKILL.md names no scripts, command-line tools or credentials: Workflow Visualizer is instructions for the agent only.
Does Workflow Visualizer access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Workflow Visualizer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Workflow Visualizer use?
Workflow Visualizer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Workflow Visualizer use?
About 1.6k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Workflow Visualizer?
Skills that share tags, products or a category with Workflow Visualizer: Schedule (TinyAGI/tinyagi, 3.6k stars), Send User Message (TinyAGI/tinyagi, 3.6k stars), Cron Ops (czl9707/build-your-own-openclaw, 1.9k stars) and X Bookmarks (sharbelxyz/x-bookmarks, 289 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Workflow Visualizer?
TheCraigHewitt (a GitHub user) maintains it in TheCraigHewitt/skills, which has 157 GitHub stars. The repository holds 65 skills in this directory. The repository was last updated on May 22, 2026.
Source: TheCraigHewitt/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.