graph-easy

Create ASCII diagrams for GitHub Flavored Markdown documents using Graph-Easy.

62|10|Updated Dec 4, 2025
One-click install
npx skills add https://github.com/terrylica/cc-skills --skill graph-easy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: graph-easy
Source: https://github.com/terrylica/cc-skills/tree/main/plugins/itp/skills/graph-easy
Command: npx skills add https://github.com/terrylica/cc-skills --skill graph-easy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating visual diagrams for documentation often involves external tools, image files, and complex embedding, making maintenance difficult. This skill provides a simple, text-based solution for embedding diagrams directly into any GitHub Flavored Markdown file.

Core Features & Use Cases

  • Universal ASCII Diagramming: Create flowcharts, pipelines, and system diagrams for READMEs, design docs, and specifications using pure text.
  • Automatic Layout: Define relationships, and graph-easy handles the visual arrangement, saving design time.
  • Markdown-Native Embedding: Diagrams are rendered as text, eliminating external image dependencies and simplifying version control.
  • Use Case: When explaining a complex system flow in a README or a design document, use this skill to quickly generate a clear, self-contained diagram that is easy to update and review in plain text.

Quick Start

Create an ASCII diagram for the README.md file. Show a pipeline with 'Input' flowing to 'Process' and then to 'Output'.

Frequently Asked Questions about graph-easy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create ASCII diagrams for Markdown documentation?

ASCII diagrams embed directly into Markdown files using graph-easy, which converts text-based graph definitions into formatted ASCII output. No external image files or rendering tools are needed—diagrams render as plain text suitable for READMEs, design docs, and specifications.

Can I use ASCII diagrams in GitHub Flavored Markdown without external dependencies?

Yes. Graph-easy generates pure ASCII diagrams that render natively in GFM without image dependencies or external rendering. Diagrams stay as text in version control, simplifying updates and reviews.

How do I generate flowcharts and pipeline diagrams for architecture documentation?

Define relationships between nodes—Input, Process, Output—and graph-easy automatically arranges them into clear ASCII flowcharts and pipelines. The skill handles layout, letting you focus on documenting system flow in plain text.

What's the best way to embed system diagrams in a README without maintaining separate image files?

Embed ASCII diagrams directly in Markdown as text. Graph-easy eliminates image file maintenance by rendering diagrams as ASCII art inline, keeping documentation self-contained and version-controllable.

Do I need to install graph-easy separately, or is it included?

Graph-easy relies on the Graph::Easy Perl module, installed via mise or cpanm. The skill includes a preflight check to validate graph-easy availability in PATH before diagram generation.

When should I use ASCII diagrams instead of image-based visualizations?

Use ASCII diagrams for documentation that prioritizes version control, text-based collaboration, and low-friction updates. They work best in Markdown-heavy workflows where visual clarity and plain-text maintainability matter equally.