Skip to content
Back to skills

Diagram Taxonomy

ASecurity

Use when the task needs the right diagram type selected explicitly before architecture, integration, runtime, data-model, workflow, or UX reasoning.

  • 3 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 8, 2026
development

Security analysis

A100/100

Scanned September 8, 2026

npx -y skills add agisota/old-one --skill diagram-taxonomy --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Diagram Taxonomy?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Diagram Taxonomy
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/agisota-diagram-taxonomy/badge)](https://www.skillsdirectory.com/skills/agisota-diagram-taxonomy)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: diagram-taxonomy
description: Use when the task needs the right diagram type selected explicitly before architecture, integration, runtime, data-model, workflow, or UX reasoning.
---

# Diagram Taxonomy

Choose the lightest diagram that answers the question:
- ASCII architecture -> boundaries, modules, ownership, blast radius
- sequence -> who calls whom and in what order
- data-flow -> where data moves and transforms
- ERD -> how data is shaped
- state machine -> how status/lifecycle changes over time
- component/screen map -> what the workflow surface looks like

Reference:
- `~/.ai-agent-hub/knowledge/rules/operator-pack-v3/DIAGRAM_TAXONOMY.md`

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in development →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.