CtrlK
BlogDocsLog inGet started
Tessl Logo

architecture-designer

Use when designing new high-level system architecture, reviewing existing designs, or making architectural decisions. Invoke to create architecture diagrams, write Architecture Decision Records (ADRs), evaluate technology trade-offs, design component interactions, and plan for scalability. Use for system design, architecture review, microservices structuring, ADR authoring, scalability planning, and infrastructure pattern selection — distinct from code-level design patterns or database-only design tasks.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Failed to scan

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

The body is a well-organized instruction skill: clear workflow with validation and feedback loops, good progressive disclosure via a reference table with real files, and concrete example templates. It is slightly held back by some narrative padding and guidance-level (rather than executable) workflow steps.

DimensionReasoningScore

Conciseness

Mostly efficient with tight sections and useful templates, but the narrative role definition ('You are a principal architect with 15+ years of experience...') and the fully inlined ADR example add some over-explanation that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready Mermaid and ADR templates plus explicit MUST DO / MUST NOT DO lists, though the core workflow steps remain guidance-level rather than executable commands — acceptable for an instruction-style design skill with minor gaps.

4 / 5

Workflow Clarity

A clear 5-step sequence with explicit validation checkpoints ('Verify full requirements coverage before proceeding') and a feedback loop ('If review fails, return to step 3 with recorded feedback').

5 / 5

Progressive Disclosure

SKILL.md is a concise overview with a well-signaled one-level-deep reference table mapping topic to file to 'Load When' condition; all five referenced files exist and inline content is limited to example templates rather than bulk reference material.

5 / 5

Total

18

/

20

Passed

Description

92%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-structured description that clearly states capabilities, trigger conditions, and its distinct niche relative to neighbouring skills. The only minor gap is slightly less than exhaustive trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'create architecture diagrams', 'write ADRs', 'evaluate technology trade-offs', 'design component interactions', 'plan for scalability' — giving comprehensive coverage of capabilities.

5 / 5

Completeness

Explicitly answers both what ('Invoke to create architecture diagrams, write ADRs...') and when ('Use when designing new high-level system architecture...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural terms users say ('architecture', 'system design', 'microservices', 'scalability', 'ADR', 'infrastructure') with both 'Use when' and 'Use for' phrasing, but stops short of the exhaustive synonym/extension coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche and explicitly disambiguates it as 'distinct from code-level design patterns or database-only design tasks', minimizing conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
jeffallan/claude-skills
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.