Generate Workflow Diagram

Name: Generate Workflow Diagram
Author: pjt222

Listed

pjt222·vlatest·other·MIT

Visually represent complex processes as clear workflow diagrams from text descriptions, streamlining understanding and collaboration.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Run this in your project

terminal

$ npx skills add pjt222/agent-almanac --skill generate-workflow-diagram -a claude-code

Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

pjt222

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned 30 Sept 2026

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

Declares what it does: failed
No SKILL.md was found in the skill's directory.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned pjt222/development-guides at bcca822c1c.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit: bcca822c1c
Manifest: skills/generate-workflow-diagram/SKILL.md
Scanned: 0 files
Copies in repo: 3 — all of them scanned

This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.

What each check looks for →

About this skill

What it does

This skill generates workflow diagrams based on textual descriptions. It can take a description of a process, steps, or sequence and output a visual representation in a standard diagram format. The generated diagrams are intended to clarify complex processes and improve understanding among stakeholders.

When to use it

Documenting development pipelines: Visualize the stages involved in building and deploying software.
Mapping business processes: Create clear diagrams of operational workflows for analysis or training.
Explaining technical procedures: Simplify intricate steps into an easy-to-follow visual guide.
Designing new systems: Outline the flow of data and actions within a proposed system.

Key capabilities

Diagram generation from text descriptions
Standard diagram format output (specific format not specified)

Example prompts

"Create a workflow diagram for deploying a containerized application to Kubernetes."
"Generate a diagram outlining the steps in our customer onboarding process."
"Can you visualize the data flow in our ETL pipeline?"

Tips & gotchas

The quality of the generated diagram heavily depends on the clarity and detail provided in the input text description. Be specific about the sequence of actions and any decision points involved for best results.