backend-architect

Backend Architect Agent. 시스템 설계, 아키텍처 결정, 기술 선택을 담당합니다. 설계, 아키텍처, 구조, 패턴, 기술 선택 관련 요청 시 사용됩니다.

Quality

22%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/backend-architect/SKILL.md

Quality

Discovery

N/A

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

Something went wrong

Implementation

22%

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

This skill reads more like a reference document or overview than actionable guidance for an architect agent. It describes the current architecture and principles well but lacks concrete instructions on what Claude should actually do when invoked. The content explains concepts Claude already knows (SOLID, basic patterns) rather than providing project-specific decision frameworks or executable workflows.

Suggestions

Add concrete decision workflows: e.g., 'When asked about technology selection: 1. Check existing stack in X file, 2. Evaluate against criteria Y, 3. Document decision in ADR format at Z location'

Replace SOLID principle definitions with project-specific examples or remove entirely - Claude knows these concepts

Provide an executable ADR template with specific file paths and a step-by-step process for creating new records

Add specific commands or code snippets for common architect tasks (e.g., generating module structure, checking dependencies, validating architecture constraints)

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes some explanatory content Claude already knows (SOLID principles definitions, basic pattern explanations). The architecture diagrams add value but the principle explanations are redundant.	2 / 3
Actionability	The skill describes concepts and patterns but provides no executable code, commands, or concrete examples. It tells Claude what patterns exist but not how to implement them or what specific actions to take.	1 / 3
Workflow Clarity	No clear workflows or step-by-step processes are defined. The 'expansion considerations' and 'ADR' sections list items but lack sequencing, validation checkpoints, or actionable procedures.	1 / 3
Progressive Disclosure	Content is organized into logical sections with headers, but everything is inline with no references to detailed documentation. For an architect role, links to ADR templates, detailed patterns, or implementation guides would improve navigation.	2 / 3
	Total	6 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	10 / 11 Passed

Repository: shaul1991/shaul-agents-plugin
Commit: 9242c58

Reviewed: 29 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.