Agent skill for arch-system-design - invoke with $agent-arch-system-design
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill agent-arch-system-design28
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Full architecture deliverables with C4 model and ADRs
Architecture overview doc
100%
100%
Component interaction doc
100%
100%
Data flow doc
100%
100%
ADR present
100%
100%
Technology evaluation matrix
100%
100%
PlantUML diagram file
0%
0%
C4 model notation used
0%
0%
No code snippets in docs
100%
100%
NFRs addressed
100%
100%
Future extensibility
100%
100%
Operational aspects
100%
100%
Minimal emoji usage
100%
100%
Without context: $0.8956 · 5m 38s · 25 turns · 29 in / 19,123 out tokens
With context: $1.1645 · 6m 57s · 29 turns · 37 in / 23,218 out tokens
Decision framework application with trade-off analysis
Quality attributes section
100%
100%
Constraints and assumptions
100%
100%
Trade-off comparison
100%
100%
Business alignment
100%
100%
Risks identified
100%
100%
Mitigations provided
100%
100%
ADR present and structured
100%
100%
No code snippets
100%
100%
Technical communication style
100%
100%
Minimal emoji
100%
100%
NFRs addressed
100%
100%
Without context: $0.4549 · 3m 17s · 19 turns · 25 in / 8,843 out tokens
With context: $0.5615 · 3m 3s · 23 turns · 31 in / 8,731 out tokens
Output path constraints and allowed file types
No output in src/
100%
100%
Docs in architecture/design dir
100%
100%
Diagram in allowed format
66%
100%
Diagram in diagrams/ dir
0%
100%
C4 model used in diagram
100%
0%
Decomposition strategy doc
100%
100%
Migration sequence doc
100%
100%
No code snippets in docs
100%
100%
NFRs addressed
100%
100%
Minimal emoji
100%
100%
Without context: $0.6712 · 3m 56s · 23 turns · 30 in / 13,366 out tokens
With context: $0.8139 · 4m 36s · 32 turns · 98 in / 14,045 out tokens
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.