Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Draw.io Logical Diagrams Creation · giuseppe-trisciuoglio | DecimalAI

giuseppe-trisciuoglio/drawio-logical-diagrams

SkillScore73Maintained

Creates professional logical flow diagrams and logical system architecture diagrams using draw.io XML format (.drawio files). Use when creating: (1) logical flow diagrams showing data/process flow between system components, (2) logical architecture diagrams representing system structure without cloud provider specifics, (3) BPMN process diagrams, (4) UML diagrams (class, sequence, activity), (5) data flow diagrams (DFD), (6) decision flowcharts, or (7) system interaction diagrams. This skill foc

Documentationby giuseppe-trisciuoglio

Links this skill to your agents and keeps it current with the author’s updates.

Automatic

Doc Ops pack

1 · One-time — install the CLI (docs ↗)

pip install decimalai

2 · Get the skill — writes .claude/skills/giuseppe-trisciuoglio-drawio-logical-diagrams/SKILL.md

decimalai skills pull giuseppe-trisciuoglio-drawio-logical-diagrams --out .claude/skills/

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/giuseppe-trisciuoglio-drawio-logical-diagrams/SKILL.md https://app.decimal.ai/s/giuseppe-trisciuoglio-drawio-logical-diagrams/SKILL.md

Raw file: /s/giuseppe-trisciuoglio-drawio-logical-diagrams/SKILL.md ↗ · machine-readable summary at /s/giuseppe-trisciuoglio-drawio-logical-diagrams.json ↗

In productionGlobal

how this skill behaves on real traffic · last 30 days

No production data for this skill yet — usage numbers appear here once agents start running it.

Anonymized aggregate across every org using this skill — proof from real production use, not a demo.

Does this skill help? · Benchmark: with vs. withoutsign in to run this on your agents

22 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 8d ago

Yes — +32% lift · at higher cost+134% tokens0% turns73% of whole cases pass with skill (16/22)

Test case	Without → With	Effect	Δ tokens	Δ turns
case-14	✗→✓	▲ Improved	188%	0%
case-01	✗→✓	▲ Improved	67%	0%
case-15	✗→✓	▲ Improved	158%	0%
case-09	✗→✓	▲ Improved	217%	0%
case-12	✗→✓	▲ Improved	234%	0%

Showing 5 of 22 cases

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 8/3/2026

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

giuseppe-trisciuoglio / developer-kit

plugins/developer-kit-core/skills/drawio-logical-diagrams/SKILL.md

View on GitHub ↗

License MITImported 8/3/2026Version v1Bundled 7 files

Skill contents

references/

SKILL.md

Draw.io Logical Diagrams Creation

Overview

Create professional logical diagrams in draw.io's native XML format for logical flow diagrams, system architecture visualizations, and abstract process representations using generic shapes and symbols.

When to Use

Creating logical flow diagrams showing data flow between system components
Designing logical architecture diagrams (abstract system structure)
Building BPMN process diagrams for business processes
Drawing UML diagrams (class, sequence, activity, state)
Creating data flow diagrams (DFD) for system analysis
Making decision flowcharts with branching logic
Visualizing system interactions and sequences
Documenting logical system design without cloud specifics

Do NOT use for: AWS/Azure/GCP architecture diagrams (use aws-drawio-architecture-diagrams).

Instructions

Creating a Logical Diagram

Analyze the request: Understand the system/process to diagram
Choose diagram type: Flowchart, architecture, BPMN, UML, DFD, etc.
Identify elements: Determine actors, processes, data stores, connectors
Draft XML structure: Create the mxGraphModel with proper root cells
Add shapes: Create mxCell elements with appropriate styles
Add connectors: Link elements with edge elements
Validate XML: Verify XML is well-formed and all IDs are unique (see validation checklist below)
Output: Write the .drawio file for the user

XML Validation Checklist

Before outputting the file, verify:

] All tags are properly closed (no unclosed <mxCell>, </mxGeometry>, etc.)
] All cell IDs are unique (0 and 1 are reserved root cells, use sequential integers starting from 2)
] All source and target attributes reference existing cell IDs
] All parent attributes reference existing cell IDs
] All coordinates (x, y, width, height) are positive numbers
] Special characters are escaped (< → <, > → >, & → &)
] Multi-line labels use 
 or <br> with html=1 in style

Key XML Components

| Component | Description | |-----------|-------------| | mxfile | Root element with host and version | | diagram | Contains the diagram definition | | mxGraphModel | Canvas settings (grid, page size) | | root | Container for all cells (must include id="0" and id="1") | | mxCell | Individual shapes (vertices) or connectors (edges) |

Draw.io XML Structure

xml
<mxfile host="app.diagrams.net" agent="Claude" version="24.7.17">
  <diagram id="logical-flow-1" name="Logical Flow">
    <mxGraphModel dx="1200" dy="800" grid="1" gridSize="10" guides="1"
      tooltips="1" connect="1" arrows="1" fold="1" page="1"
      pageScale="1" pageWidth="1169" pageHeight="827" math="0" shadow="0">
      <root>
        <mxCell id="0" />
        <mxCell id="1" parent="0" />
        <!-- Shapes and connectors here -->
      </root>
    </mxGraphModel>
  </diagram>
</mxfile>

Key rules:

IDs "0" and "1" are reserved for root cells
Use sequential integer IDs starting from "2"
Use landscape orientation for architecture diagrams
All coordinates must be positive and aligned to grid (multiples of 10)

Generic Shapes and Styles

Basic Shape Types

| Shape | Style | |-------|-------| | Rectangle | rounded=0;whiteSpace=wrap;html=1; | | Rounded Rectangle | rounded=1;whiteSpace=wrap;html=1; | | Ellipse/Circle | ellipse;whiteSpace=wrap;html=1; | | Diamond | rhombus;whiteSpace=wrap;html=1; | | Cylinder | shape=cylinder3;whiteSpace=wrap;html=1;boundedLbl=1; | | Hexagon | shape=hexagon;perimeter=hexagonPerimeter2;whiteSpace=wrap;html=1; | | Parallelogram | shape=ext;double=1;rounded=0;whiteSpace=wrap;html=1; |

Standard Color Palette

| Element Type | Fill Color | Border Color | Usage | |--------------|------------|--------------|-------| | Process | #dae8fc | #6c8ebf | Operations/actions | | Decision | #fff2cc | #d6b656 | Conditional branches | | Start/End | #d5e8d4 | #82b366 | Terminal states | | Data/Store | #e1f5fe | #0277bd | Databases/files | | Entity | #f3e5f5 | #7b1fa2 | External systems | | Error/Stop | #f8cecc | #b85450 | Error states | | Actor/User | #ffe0b2 | #f57c00 | Users/actors | | Container | #f5f5f5 | #666666 | Grouping areas |

Connector Styles

Standard flow:

edgeStyle=orthogonalEdgeStyle;rounded=0;orthogonalLoop=1;jettySize=auto;html=1;endArrow=classic;endFill=1;strokeColor=#666666;strokeWidth=2;

Dashed (alternative/optional):

edgeStyle=orthogonalEdgeStyle;dashed=1;dashPattern=5 5;strokeColor=#666666;

Arrow head styles:

endArrow=classic;endFill=1 - Filled triangle
endArrow=open;endFill=0 - Open arrow
endArrow=blockThin;endFill=1 - Block arrow

Diagram Types

| Type | Key Elements | |------|--------------| | Logical Flow | Actors (orange), Services (blue), Data Stores (cyan), External Systems (purple) | | Logical Architecture | Layered containers with nested components | | BPMN | Circle (Start/End), Rounded Rectangle (Activity), Diamond (Gateway) | | UML Sequence | Vertical lifelines with message arrows | | DFD | Square (Entity), Circle (Process), Open Rectangle (Data Store) |

Reference Files

For detailed shape examples and style references, see:

shape-styles.md - Complete shape examples and style reference
diagram-templates.md - Ready-to-use templates

Examples

Example 1: Order Processing Flow

Request: "Create a logical flow diagram showing order processing: customer submits order, system validates, if valid then processes payment and ships, if invalid notifies customer."

xml
<mxfile host="app.diagrams.net" agent="Claude" version="24.7.17">
  <diagram id="order-flow-1" name="Order Processing">
    <mxGraphModel dx="1200" dy="800" grid="1" gridSize="10" guides="1" tooltips="1" connect="1" arrows="1" fold="1" page="1" pageScale="1" pageWidth="1169" pageHeight="827" math="0" shadow="0">
      <root>
        <mxCell id="0"/><mxCell id="1" parent="0"/>
        <mxCell id="2" value="Start" style="ellipse;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=#82b366;fontSize=12;" vertex="1" parent="1"><mxGeometry x="80" y="50" width="80" height="40" as="geometry"/></mxCell>
        <mxCell id="3" value="Submit Order" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#dae8fc;strokeColor=#6c8ebf;fontSize=12;" vertex="1" parent="1"><mxGeometry x="60" y="130" width="120" height="60" as="geometry"/></mxCell>
        <mxCell id="4" value="Validate&#xa;Order?" style="rhombus;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=#d6b656;fontSize=12;" vertex="1" parent="1"><mxGeometry x="80" y="230" width="80" height="80" as="geometry"/></mxCell>
        <mxCell id="5" value="Notify&#xa;Customer" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#f8cecc;strokeColor=#b85450;fontSize=12;" vertex="1" parent="1"><mxGeometry x="220" y="240" width="100" height="50" as="geometry"/></mxCell>
        <mxCell id="6" value="Process&#xa;Payment" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#dae8fc;strokeColor=#6c8ebf;fontSize=12;" vertex="1" parent="1"><mxGeometry x="60" y="350" width="120" height="60" as="geometry"/></mxCell>
        <mxCell id="7" value="Ship Order" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#dae8fc;strokeColor=#6c8ebf;fontSize=12;" vertex="1" parent="1"><mxGeometry x="60" y="450" width="120" height="60" as="geometry"/></mxCell>
        <mxCell id="8" value="End" style="ellipse;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=#82b366;fontSize=12;" vertex="1" parent="1"><mxGeometry x="80" y="550" width="80" height="40" as="geometry"/></mxCell>
        <mxCell id="10" style="edgeStyle=orthogonalEdgeStyle;rounded=0;endArrow=classic;endFill=1;strokeColor=#666666;strokeWidth=2;" edge="1" parent="1" source="2" target="3"><mxGeometry relative="1" as="geometry"/></mxCell>
        <mxCell id="11" style="edgeStyle=orthogonalEdgeStyle;rounded=0;endArrow=classic;endFill=1;strokeColor=#666666;strokeWidth=2;" edge="1" parent="1" source="3" target="4"><mxGeometry relative="1" as="geometry"/></mxCell>
        <mxCell id="12" value="No" style="edgeStyle=orthogonalEdgeStyle;rounded=0;endArrow=classic;endFill=1;strokeColor=#b85450;strokeWidth=2;fontSize=11;" edge="1" parent="1" source="4" target="5"><mxGeometry relative="1" as="geometry"/></mxCell>
        <mxCell id="13" value="Yes" style="edgeStyle=orthogonalEdgeStyle;rounded=0;endArrow=classic;endFill=1;strokeColor=#82b366;strokeWidth=2;fontSize=11;" edge="1" parent="1" source="4" target="6"><mxGeometry relative="1" as="geometry"/></mxCell>
        <mxCell id="14" style="edgeStyle=orthogonalEdgeStyle;rounded=0;endArrow=classic;endFill=1;strokeColor=#666666;strokeWidth=2;" edge="1" parent="1" source="6" target="7"><mxGeometry relative="1" as="geometry"/></mxCell>
        <mxCell id="15" style="edgeStyle=orthogonalEdgeStyle;rounded=0;endArrow=classic;endFill=1;strokeColor=#666666;strokeWidth=2;" edge="1" parent="1" source="7" target="8"><mxGeometry relative="1" as="geometry"/></mxCell>
        <mxCell id="16" style="edgeStyle=orthogonalEdgeStyle;rounded=0;endArrow=classic;endFill=1;strokeColor=#b85450;strokeWidth=2;" edge="1" parent="1" source="5" target="8"><mxGeometry relative="1" as="geometry"/></mxCell>
      </root>
    </mxGraphModel>
  </diagram>
</mxfile>

Example 2: Three-Tier Logical Architecture

Request: "Create a logical architecture diagram for a web application with presentation, business logic, and data tiers."

xml
<mxfile host="app.diagrams.net" agent="Claude" version="24.7.17">
  <diagram id="three-tier-1" name="Three-Tier Architecture">
    <mxGraphModel dx="1200" dy="800" grid="1" gridSize="10" guides="1" tooltips="1" connect="1" arrows="1" fold="1" page="1" pageScale="1" pageWidth="1169" pageHeight="827" math="0" shadow="0">
      <root>
        <mxCell id="0"/><mxCell id="1" parent="0"/>
        <mxCell id="2" value="User" style="ellipse;whiteSpace=wrap;html=1;fillColor=#ffe0b2;strokeColor=#f57c00;fontSize=12;" vertex="1" parent="1"><mxGeometry x="40" y="340" width="60" height="40" as="geometry"/></mxCell>
        <mxCell id="3" value="Presentation Layer" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#f5f5f5;strokeColor=#666666;fontSize=14;fontStyle=1;" vertex="1" parent="1"><mxGeometry x="160" y="40" width="300" height="180" as="geometry"/></mxCell>
        <mxCell id="4" value="Web&#xa;Browser" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#dae8fc;strokeColor=#6c8ebf;fontSize=12;" vertex="1" parent="3"><mxGeometry x="20" y="30" width="80" height="50" as="geometry"/></mxCell>
        <mxCell id="5" value="Mobile&#xa;App" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#dae8fc;strokeColor=#6c8ebf;fontSize=12;" vertex="1" parent="3"><mxGeometry x="120" y="30" width="80" height="50" as="geometry"/></mxCell>
        <mxCell id="7" value="Application Layer" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#f5f5f5;strokeColor=#666666;fontSize=14;fontStyle=1;" vertex="1" parent="1"><mxGeometry x="160" y="260" width="300" height="180" as="geometry"/></mxCell>
        <mxCell id="8" value="API&#xa;Gateway" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=#d6b656;fontSize=12;" vertex="1" parent="7"><mxGeometry x="20" y="30" width="80" height="50" as="geometry"/></mxCell>
        <mxCell id="9" value="Business&#xa;Logic" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#dae8fc;strokeColor=#6c8ebf;fontSize=12;" vertex="1" parent="7"><mxGeometry x="110" y="30" width="80" height="50" as="geometry"/></mxCell>
        <mxCell id="11" value="Data Layer" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#f5f5f5;strokeColor=#666666;fontSize=14;fontStyle=1;" vertex="1" parent="1"><mxGeometry x="160" y="480" width="300" height="180" as="geometry"/></mxCell>
        <mxCell id="12" value="Primary&#xa;Database" style="shape=cylinder3;whiteSpace=wrap;html=1;boundedLbl=1;fillColor=#e1f5fe;strokeColor=#0277bd;fontSize=12;" vertex="1" parent="11"><mxGeometry x="20" y="30" width="60" height="80" as="geometry"/></mxCell>
        <mxCell id="13" value="Cache" style="shape=cylinder3;whiteSpace=wrap;html=1;boundedLbl=1;fillColor=#fff3e0;strokeColor=#e65100;fontSize=12;" vertex="1" parent="11"><mxGeometry x="100" y="30" width="60" height="80" as="geometry"/></mxCell>
        <mxCell id="20" style="edgeStyle=orthogonalEdgeStyle;rounded=0;endArrow=classic;endFill=1;strokeColor=#666666;strokeWidth=2;" edge="1" parent="1" source="2" target="4"><mxGeometry relative="1" as="geometry"/></mxCell>
        <mxCell id="21" style="edgeStyle=orthogonalEdgeStyle;rounded=0;endArrow=classic;endFill=1;strokeColor=#666666;strokeWidth=2;" edge="1" parent="1" source="4" target="8"><mxGeometry relative="1" as="geometry"/></mxCell>
        <mxCell id="22" style="edgeStyle=orthogonalEdgeStyle;rounded=0;endArrow=classic;endFill=1;strokeColor=#666666;strokeWidth=2;" edge="1" parent="1" source="8" target="9"><mxGeometry relative="1" as="geometry"/></mxCell>
        <mxCell id="23" style="edgeStyle=orthogonalEdgeStyle;rounded=0;endArrow=classic;endFill=1;strokeColor=#666666;strokeWidth=2;" edge="1" parent="1" source="9" target="12"><mxGeometry relative="1" as="geometry"/></mxCell>
        <mxCell id="24" value="query" style="edgeStyle=orthogonalEdgeStyle;rounded=0;endArrow=open;endFill=0;strokeColor=#666666;strokeWidth=1;fontSize=10;dashed=1;" edge="1" parent="1" source="9" target="13"><mxGeometry relative="1" as="geometry"/></mxCell>
      </root>
    </mxGraphModel>
  </diagram>
</mxfile>

For additional templates (microservice architecture, event-driven, decision tree, sequence, DFD), see diagram-templates.md.

Constraints and Warnings

Critical Constraints

XML validity: Always close tags properly and escape special characters
Unique IDs: All cell IDs must be unique (except parent "0" and "1")
Valid references: Source/target must reference existing cell IDs
Positive coordinates: All x, y values must be >= 0

Warnings

XML files must be well-formed or will fail to open in draw.io
Invalid parent references cause elements to disappear
Negative coordinates place elements outside visible canvas

Best Practices

Use consistent colors per element type across all diagrams
Keep arrows straight with minimal bends
Place labels at least 20px from arrow lines
Group related elements in containers
Use 12-14px font for labels, 10-11px for annotations
Align all coordinates to grid (multiples of 10)
Use high contrast colors and don't rely solely on color for meaning

Want to see if giuseppe-trisciuoglio/drawio-logical-diagrams would activate on your phrasing? Try it before you install — no LLM call, no signup.

Latest benchmark · publisher runVerified

8/21/2026, 13:19 UTC · 22 cases

Lift

+32%

73% vs 41%

Agent turns

1.0 vs 1.0

Tokens

+134%

7,042.59 vs 3,016.41

fail → pass · 7pass → pass · 9fail → fail · 6

Per-case results (22)

Case	Status	Duration (ms)			Turns			Tokens			Tool calls
Case	Status	Without	With	Δ	Without	With	Δ	Without	With	Δ	Without	With	Δ
case-14 In a logical diagram depicting user interactions, what standard fill and border colors should be applied to Actor or User nodes?	fail→pass	11,030	2,164	-80%	1	1	0%	1,767	5,095	+188%	0	0	—
case-01 Can you design a logical flowchart for a loan application processing workflow? The workflow begins when an applicant submits details, moves through an automated credit check decision step, routes to manual underwriting if flagged, and concludes at approval or rejection. Please provide the output as a valid native draw.io XML document that I can save as a .drawio file.	fail→pass	29,201	25,185	-14%	1	1	0%	6,210	10,368	+67%	0	0	—
case-07 I am writing a script to generate draw.io XML. What are the reserved root cell IDs and initial container relationships required inside the `<root>` tag of an `<mxGraphModel>`?	pass→pass	9,097	7,602	-16%	1	1	0%	1,656	5,905	+257%	0	0	—
case-15 When grouping related components into a system boundary container (such as an 'Application Layer' container), what style properties and fill color should be assigned to the container `mxCell`?	fail→pass	14,844	7,607	-49%	1	1	0%	2,405	6,214	+158%	0	0	—
case-08 When adding a decision node into a draw.io logical flowchart XML, what specific shape style string and standard fill color should be applied?	pass→pass	7,483	3,387	-55%	1	1	0%	1,322	5,336	+304%	0	0	—
case-02 I need a logical architecture diagram representing an e-commerce platform. It should illustrate a client layer, an API gateway layer, decoupled microservices for user accounts and inventory, and a persistent storage layer. Please generate the complete draw.io XML markup for this abstract system layout.	fail→fail	28,347	26,460	-7%	1	1	0%	6,196	10,952	+77%	0	0	—
case-03 Could you build a Data Flow Diagram (DFD) for an online hospital appointment booking system showing the patient entity, booking process, schedule database, and notification service? Please deliver the raw XML structure formatted specifically for draw.io import.	fail→fail	22,426	18,863	-16%	1	1	0%	4,901	9,161	+87%	0	0	—
case-04 I need an AWS cloud architecture diagram in draw.io format featuring AWS EC2, AWS Lambda, Amazon S3, and AWS DynamoDB components using official AWS architecture icons and stencils. Can you build the AWS draw.io XML for this infrastructure?	fail→fail	29,872	31,727	+6%	1	1	0%	6,192	8,948	+45%	0	0	—
case-05 Please generate a draw.io XML diagram showing an Azure Cloud infrastructure layout with Azure App Service, Azure SQL Database, and Azure Key Vault using native Azure service icons.	fail→fail	32,850	24,827	-24%	1	1	0%	4,428	10,194	+130%	0	0	—
case-06 Create a GCP cloud deployment diagram in draw.io XML format using Google Cloud Platform official resource shapes for GKE, Cloud Pub/Sub, and BigQuery.	fail→fail	30,037	29,550	-2%	1	1	0%	6,173	10,929	+77%	0	0	—
case-09 I need to represent a SQL database in a draw.io XML logical diagram. Which shape value and standard fill/border color combination should be assigned to the `mxCell` style?	fail→pass	9,421	3,295	-65%	1	1	0%	1,696	5,376	+217%	0	0	—
case-10 In draw.io XML cells, how should line breaks in node labels be encoded when `html=1` is not set versus when `html=1` is enabled in the style string?	pass→pass	10,863	5,119	-53%	1	1	0%	1,878	5,673	+202%	0	0	—
case-11 If a shape label in draw.io XML contains conditional comparison text like `Amount > 1000 & Valid < True`, how must those special characters be escaped within the `value` attribute of the `mxCell`?	pass→pass	11,439	5,736	-50%	1	1	0%	2,137	5,800	+171%	0	0	—
case-12 In a logical system diagram, an external third-party payment gateway needs to be represented as an External Entity shape. What standard fill and border colors should be used according to standard logical diagram conventions?	fail→pass	10,177	3,305	-68%	1	1	0%	1,613	5,388	+234%	0	0	—
case-13 What shape and standard color scheme should be used for Start and End terminal nodes in a logical process flowchart draw.io XML?	pass→pass	12,984	4,004	-69%	1	1	0%	2,387	5,517	+131%	0	0	—
case-16 Create a draw.io XML snippet for a standard orthogonal connector arrow pointing from source cell 3 to target cell 4 with a solid head.	pass→pass	7,345	3,563	-51%	1	1	0%	1,295	5,387	+316%	0	0	—
case-17 What connector style configuration produces a dashed orthogonal line for optional or alternative paths in a draw.io logical flow XML?	fail→pass	8,753	4,240	-52%	1	1	0%	1,423	5,495	+286%	0	0	—
case-18 When marking an error state or exception stop node in a logical process diagram, what standard fill and border colors should be assigned to the cell?	fail→pass	9,582	2,991	-69%	1	1	0%	1,483	5,179	+249%	0	0	—
case-19 In a business process diagram rendered in draw.io XML, which generic shape is used for gateways and which shape for activities?	pass→pass	4,978	4,289	-14%	1	1	0%	810	5,550	+585%	0	0	—
case-20 When placing vertices and edges inside a draw.io `<mxGeometry>` tag, what rule governs coordinate positioning and grid alignment?	fail→fail	12,221	5,083	-58%	1	1	0%	1,919	5,561	+190%	0	0	—
case-21 Generate a draw.io XML diagram representing a user authentication process: User enters credentials, Authentication Service validates, if valid issue JWT token and redirect to dashboard, if invalid show error message.	pass→pass	24,771	15,300	-38%	1	1	0%	5,351	8,253	+54%	0	0	—
case-22 Construct a simple draw.io XML representation of a sequence diagram interaction between a Web Client and an Auth Server, showing request and response message arrows.	pass→pass	14,672	27,875	+90%	1	1	0%	3,119	8,656	+178%	0	0	—

These cases were also screened by the skill’s intent / safety pass.See the Trust review ↗Reproduce this benchmark in Colab ↗

How this skill was measured

DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of +32 percentage points is the difference between those two pass rates over the 22 comparable cases. 1 case got worse with the skill loaded, and it is included in that figure.

Model measured: gemini-3.6-flash
Graded by: gemini-3.6-flash
Grading method: judged
Verification: verified
Pass rate without the skill: 40.9%
Pass rate with the skill: 72.7%
Cases attempted: 22
Cases counted toward lift: 22
Cases that regressed: 1
Skill version measured: v1
Run completed: 8/21/2026, 13:19 UTC

Measured example — same prompt, with vs. without the skill · from the benchmark run · case case-14

Prompt

In a logical diagram depicting user interactions, what standard fill and border colors should be applied to Actor or User nodes?

Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.

Show both answers

SkillScore blends 4 signals1 of 4 complete

BenchmarkPass rate WITH skill on a verified run73

Live evalNeeds ≥20 evaluated traces in 30 days

AI ratingNeeds ≥10 rated traces

AdoptionNeeds ≥10 serves across ≥2 orgs in 30 days

Efficiency · separate axis (at equal correctness)+0% turns+181% tokens

Shown for transparency; not credited unless a verified run shows no correctness regression.

Backed by 1 of 4 signals — each added signal makes the score more robust.

Verified on gemini-3.6-flash · re-tested 7 days ago

Other measured skills in the registry, with their headline benchmark lift.