senior-architect
This skill should be used when the user asks to "design system architecture", "evaluate microservices vs monolith", "create architecture diagrams", "analyze dependencies", "choose a database", "plan for scalability", "make technical decisions", or "review system design". Use for architecture decision records (ADRs), tech stack evaluation, system design reviews, dependency analysis, and generating architecture diagrams in Mermaid, PlantUML, or ASCII format.
Install with Tessl CLI
npx tessl i github:alirezarezvani/claude-skills --skill senior-architectOverall
score
92%
Does it follow best practices?
Validation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its scope around system architecture and design decisions. It excels at providing explicit trigger phrases users would naturally say, lists concrete deliverables (ADRs, diagrams in specific formats), and clearly distinguishes itself from general development skills. The description effectively answers both what the skill does and when to use it.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'design system architecture', 'evaluate microservices vs monolith', 'create architecture diagrams', 'analyze dependencies', 'choose a database', 'plan for scalability', 'make technical decisions', 'review system design', plus specific outputs like ADRs and diagram formats. | 3 / 3 |
Completeness | Explicitly answers both what (architecture decision records, tech stack evaluation, system design reviews, dependency analysis, generating diagrams) and when ('should be used when the user asks to...' with explicit trigger phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'design system architecture', 'microservices vs monolith', 'architecture diagrams', 'choose a database', 'scalability', 'technical decisions', 'system design', 'ADRs', 'tech stack', plus specific formats like Mermaid, PlantUML, ASCII. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on system architecture and design decisions with distinct triggers like 'ADRs', 'microservices vs monolith', 'architecture diagrams', and specific diagram formats that are unlikely to conflict with general coding or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent actionability and workflow clarity. The decision workflows are particularly strong with clear steps and decision matrices. The main weakness is some verbosity and redundancy that could be trimmed, particularly the repeated command examples and sections that don't add unique value for Claude.
Suggestions
Remove the 'Common Commands' section as it duplicates commands already shown in each tool's usage section
Trim or remove 'Tech Stack Coverage' and 'Getting Help' sections which provide minimal actionable value for Claude
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy (e.g., repeated command examples in both tool sections and 'Common Commands', verbose table of contents). Some sections like 'Tech Stack Coverage' and 'Getting Help' add limited value for Claude. | 2 / 3 |
Actionability | Provides fully executable commands with clear flags, concrete example outputs, and copy-paste ready code blocks. The decision workflows include specific checklists and tables that are immediately actionable. | 3 / 3 |
Workflow Clarity | Decision workflows are clearly sequenced with numbered steps, decision tables, and explicit checkpoints. The database selection and architecture pattern workflows guide through evaluation criteria systematically with clear decision points. | 3 / 3 |
Progressive Disclosure | Excellent structure with a clear table of contents, well-organized sections, and explicit one-level-deep references to detailed documentation (references/architecture_patterns.md, etc.) with a helpful table explaining when to load each file. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
88%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 14 / 16 Passed | |
- Reviewed
Table of Contents
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.