Skip to content
TrustedSkillsbeta
Back to all skills

architecture-diagram-creator

Checked
mhattingpete·v1.0.0·backend·Apache-2.0

Create comprehensive HTML architecture diagrams showing data flows, business objectives, features, technical architecture, and deployment. Use when users request system architecture, project documenta

Install on your platform

Showing OpenClaw.

  1. 1

    Run this in your terminal

    terminal
    $ 

What we know about this skill

Publisher

mhattingpete

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

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    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 mhattingpete/claude-skills-marketplace at b5b34bcf4c.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
4 files, 79 lines
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 detailed HTML architecture diagrams based on textual descriptions. It can visualize complex systems by illustrating data flows, connecting business objectives to specific features, outlining the underlying technical architecture, and depicting deployment strategies. The resulting diagrams provide a clear and comprehensive overview of system design for stakeholders and development teams.

When to use it

  • System Documentation: Generate visual documentation for existing software architectures.
  • Project Onboarding: Quickly onboard new team members by providing a readily understandable architectural overview.
  • Technical Presentations: Create compelling visuals for presentations explaining complex systems to both technical and non-technical audiences.
  • Design Proposals: Illustrate proposed system designs during planning or pitch meetings.

Key capabilities

  • Generates HTML architecture diagrams
  • Visualizes data flows within a system
  • Connects business objectives to features
  • Illustrates technical architecture components
  • Depicts deployment strategies

Example prompts

  • "Create an architecture diagram for our e-commerce platform, showing the flow of orders from website to fulfillment center."
  • "Generate a visual representation of the data pipeline for our analytics dashboard, including sources, transformations, and storage."
  • “Diagram the technical architecture of our microservices application, highlighting key components like API gateway, databases, and message queues.”

Tips & gotchas

The quality of the diagram heavily relies on the clarity and detail provided in the input description. Be as specific as possible when describing system components and their relationships for best results.