markdown-viewer/skills

archimate

Create ArchiMate enterprise architecture diagrams using PlantUML stdlib macros. Best for TOGAF viewpoints, layered EA modeling (Business/Application/Technology), motivation analysis, and migration planning.

All-time #4172 Trending #8563 Hot #482 First seen Apr 11, 2026
8-week activity · all time api

Installation

$ npx skills add markdown-viewer/skills --skill archimate

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from markdown-viewer/skills · top by installs.

npx skills add markdown-viewer/skills

Browse all from markdown-viewer/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 3.3K
License GPL-3.0
Default branch main
Open issues 2
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

More metadata
author
ArchiMate diagrams are powered by Markdown Viewer — the best multi-platform Markdown extension (Chrome/Edge/Firefox/VS Code) with diagrams, formulas, and one-click Word export. Learn more at https://docu.md

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 7,706 B
  • docs SUMMARY.md 223 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3,131 installs

SKILL.md

Enterprise Architecture Diagram Generator (ArchiMate)

Quick Start: Add !include <archimate/Archimate> → Declare typed elements → Connect with Rel_* macros → Group into layers with rectangle → Wrap in `plantuml fence.

⚠️ IMPORTANT: Always use `plantuml or `puml code fence. NEVER use `text — it will NOT render as a diagram.

Critical Rules

  • Every diagram starts with @startuml and ends with @enduml
  • Must include !include <archimate/Archimate> before using any macros
  • Element syntax: Layer_Type(alias, "Label")
  • Relationship syntax: Rel_Type(fromAlias, toAlias, "label")
  • Use rectangle "Layer" { ... } to group elements into ArchiMate layers
  • Directional suffixes Up, Down, Left, Right control relationship direction

Element Macros

Business Layer

Macro ArchiMate Element
Business_Actor(id, "Label") Business Actor
Business_Role(id, "Label") Business Role
Business_Process(id, "Label") Business Process
Business_Function(id, "Label") Business Function
Business_Service(id, "Label") Business Service
Business_Event(id, "Label") Business Event
Business_Interface(id, "Label") Business Interface
Business_Collaboration(id, "Label") Business Collaboration
Business_Object(id, "Label") Business Object
Business_Product(id, "Label") Business Product
Business_Contract(id, "Label") Business Contract
Business_Representation(id, "Label") Business Representation

Application Layer

Macro ArchiMate Element
Application_Component(id, "Label") Application Component
Application_Service(id, "Label") Application Service
Application_Function(id, "Label") Application Function
Application_Interface(id, "Label") Application Interface
Application_Process(id, "Label") Application Process
Application_Interaction(id, "Label") Application Interaction
Application_Event(id, "Label") Application Event
Application_Collaboration(id, "Label") Application Collaboration
Application_DataObject(id, "Label") Application Data Object

Technology Layer

Macro ArchiMate Element
Technology_Device(id, "Label") Technology Device
Technology_Node(id, "Label") Technology Node
Technology_SystemSoftware(id, "Label") System Software
Technology_Artifact(id, "Label") Technology Artifact
Technology_CommunicationNetwork(id, "Label") Communication Network
Technology_Path(id, "Label") Technology Path
Technology_Service(id, "Label") Technology Service
Technology_Process(id, "Label") Technology Process
Technology_Function(id, "Label") Technology Function
Technology_Interface(id, "Label") Technology Interface

Motivation Layer

Macro ArchiMate Element
Motivation_Stakeholder(id, "Label") Stakeholder
Motivation_Driver(id, "Label") Driver
Motivation_Assessment(id, "Label") Assessment
Motivation_Goal(id, "Label") Goal
Motivation_Outcome(id, "Label") Outcome
Motivation_Principle(id, "Label") Principle
Motivation_Requirement(id, "Label") Requirement
Motivation_Constraint(id, "Label") Constraint
Motivation_Value(id, "Label") Value

Strategy Layer

Macro ArchiMate Element
Strategy_Capability(id, "Label") Capability
Strategy_Resource(id, "Label") Resource
Strategy_CourseOfAction(id, "Label") Course of Action
Strategy_ValueStream(id, "Label") Value Stream

Implementation Layer

Macro ArchiMate Element
Implementation_WorkPackage(id, "Label") Work Package
Implementation_Deliverable(id, "Label") Deliverable
Implementation_Plateau(id, "Label") Plateau
Implementation_Gap(id, "Label") Gap
Implementation_Event(id, "Label") Implementation Event

Relationship Macros

All relationships support directional suffixes: Up, Down, Left, Right.

Macro ArchiMate Relationship Line Style
Rel_Composition(from, to, "label") Composition Solid + filled diamond
Rel_Aggregation(from, to, "label") Aggregation Solid + open diamond
Rel_Assignment(from, to, "label") Assignment Solid + circle→triangle
Rel_Realization(from, to, "label") Realization Dotted + hollow triangle
Rel_Serving(from, to, "label") Serving Solid + arrow
Rel_Triggering(from, to, "label") Triggering Solid + filled triangle
Rel_Flow(from, to, "label") Flow Dashed + filled triangle
Rel_Access(from, to, "label") Access Dotted line
RelAccessr(from, to, "label") Access (read) Dotted + arrow
RelAccessw(from, to, "label") Access (write) Dotted + reverse arrow
Rel_Influence(from, to, "label") Influence Dashed + arrow
Rel_Association(from, to, "label") Association Solid line
Rel_Specialization(from, to, "label") Specialization Solid + hollow triangle

Quick Example

@startuml
!include <archimate/Archimate>

rectangle "Business" {
  Business_Actor(customer, "Customer")
  Business_Process(order, "Order Process")
  Business_Service(orderSvc, "Order Service")
}

rectangle "Application" {
  Application_Component(orderApp, "Order System")
  Application_Service(orderAPI, "Order API")
}

rectangle "Technology" {
  Technology_Node(server, "App Server")
  Technology_Device(db, "Database Server")
}

Rel_Triggering(customer, order, "places order")
Rel_Realization(order, orderSvc, "realizes")
Rel_Serving(orderAPI, orderSvc, "serves")
Rel_Realization(orderApp, orderAPI, "realizes")
Rel_Assignment(server, orderApp, "runs on")
Rel_Serving(db, server, "stores data")
@enduml

Diagram Types

Type Purpose Key Macros Example
Enterprise Landscape Full B/A/T layered view All layers [enterprise-landscape.md](examples/enterprise-landscape.md)
Application Integration App-to-app data flows Application_* [application-integration.md](examples/application-integration.md)
Technology Infrastructure Infrastructure stack Technology_* [technology-infrastructure.md](examples/technology-infrastructure.md)
Business Capability Capability map Strategy, Business [business-capability.md](examples/business-capability.md)
Migration Planning Plateau-based roadmap Implementation_* [migration-planning.md](examples/migration-planning.md)
Security Architecture Security controls Technology, Motivation [security-architecture.md](examples/security-architecture.md)
Data Architecture Data flow & ownership ApplicationDataObject, RelAccess_* [data-architecture.md](examples/data-architecture.md)
DevOps Pipeline CI/CD delivery chain Technology, Application [devops-pipeline.md](examples/devops-pipeline.md)