designing-architecture

Designs software architecture and selects appropriate patterns for projects. Use when designing systems, choosing architecture patterns, structuring projects, making technical decisions, or when asked about microservices, monoliths, or architectural approaches.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/designing-architecture/SKILL.md

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, actionable architecture-design reference with concrete templates, selection tables, and a validation feedback loop. Its main weakness is token spend on ASCII diagrams of well-known patterns that assume too little of Claude's existing knowledge.

Suggestions

Trim or collapse the five ASCII pattern diagrams (Layered, Clean, Hexagonal, Event-Driven, CQRS) to one-line summaries, since Claude already knows these patterns; keep only the 'Use when' guidance.

Move the detailed pattern reference and the trade-off/template material into separate reference files (e.g. PATTERNS.md, TEMPLATES.md) and surface them as one-level-deep links from a leaner SKILL.md overview.

Interleave explicit validation checkpoints within the 6-step workflow rather than only at the end, so each step gates the next.

Dimension	Reasoning	Score
Conciseness	Mostly organized as tables, checklists, and templates rather than padded prose, but it spends substantial tokens on large ASCII diagrams of patterns Claude already knows (Layered, Clean, Hexagonal, Event-Driven, CQRS), which could be tightened.	3 / 5
Actionability	Provides concrete, usable artifacts — pattern selection tables keyed to project/team size, copyable directory-structure templates, a trade-off analysis template, and validation checklists — with only minor gaps, appropriate for an instruction-only design skill.	4 / 5
Workflow Clarity	A clear 6-step Architecture Decision Workflow is sequenced, and a separate Validation Checklist with a feedback instruction ('If validation fails, reconsider...') provides error-recovery guidance; checkpoints are not fully interleaved within the steps, keeping it just below the top anchor.	4 / 5
Progressive Disclosure	Well-structured with clear section headers and appropriately sectioned content in a single self-contained file; since no bundle files exist there is no reference navigation, and some detailed reference material (pattern diagrams, templates) is inlined that could theoretically be split out.	4 / 5
	Total	15 / 20 Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-formed description with explicit what/when structure and natural trigger terms including key pattern synonyms. It is slightly held back by high-level rather than comprehensive concrete actions and minor trigger-term gaps.

Dimension	Reasoning	Score
Specificity	Names the domain ('software architecture') and two concrete actions ('Designs software architecture and selects appropriate patterns'), but the actions are high-level and not a comprehensive list, matching the 1-2 concrete actions anchor.	3 / 5
Completeness	Explicitly answers both what ('Designs software architecture and selects appropriate patterns for projects') and when ('Use when designing systems, choosing architecture patterns...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Good natural keyword coverage — 'designing systems', 'choosing architecture patterns', 'structing projects', 'microservices', 'monoliths', 'architectural approaches' — with synonyms, though a few common variations (e.g. 'system design', 'design patterns', 'scalability') are absent.	4 / 5
Distinctiveness Conflict Risk	Clear architecture niche with distinct triggers (microservices, monoliths, architecture patterns); mostly distinct with only minor overlap risk against general project-scaffolding or coding skills.	4 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: CloudAI-X/claude-workflow-v2
Path: skills/designing-architecture/SKILL.md
Commit: 4c242af

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.