Who it is forA writer or presenter who has a finished diagram and needs an image file for a slide deck, doc or web page.
The problemAn HTML diagram is not always accepted by slide tools or image uploads, so it needs an image export.
The outcomeA PNG or SVG copy of the diagram saved next to the original HTML file.
What you need first
- An agent host that reads Agent Skills, such as Claude Code, Codex, Cursor or GitHub Copilot
- A terminal that can run `npx skills add` or the host's plugin commands
- A web browser to open the generated .html file
Steps
- Install the skill with
npx skills add cathrynlavery/diagram-design. - Generate the diagram with a plain-words request and open the .html file to confirm it.
- Ask your agent to export it to PNG or SVG, or run the export command in hosts that offer it.
- Open the exported file to check text and lines.
- Store the .html file with the image as the source copy.
Prompt for your agent
Using the diagram-design skill from cathrynlavery/diagram-design, export the diagram at <path to .html file> to PNG and to SVG. Verify that both files open and that text and lines are not clipped.
Caveat. The export details are described in the README's Export section, so read that section for the exact export method on your host before relying on it.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page