CtrlK
BlogDocsLog inGet started
Tessl Logo

architecture-reviewer

Use when making architectural decisions, planning features, designing new components, reviewing PRs, or validating that proposed changes align with Clean Architecture principles. Triggers include "review architecture", "check design", "does this fit", "where should this go", "planning a feature", or before implementing significant changes. Part of the Shep autonomous SDLC platform — https://shep.bot

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

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 concise and well-structured with actionable heuristics and a usable output template. It loses a little on actionability and workflow clarity because it is advisory/checklist-driven rather than executable-code-driven with explicit validation loops.

Suggestions

Add one or two concrete executable commands (e.g., a lint/typecheck or dependency-direction check command) to lift actionability toward fully executable guidance.

Include an explicit validation/feedback checkpoint in the review workflow (e.g., 're-check dependencies after proposed placement') to make the workflow loop explicit.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding or over-explanation of basic concepts; the compact ASCII layer tree and bullet heuristics assume Claude's competence and every line earns its place.

5 / 5

Actionability

Provides concrete heuristics (layer placement rules), specific paths ('application/ports/output/'), and a copy-paste output template, but is guidance-driven with no executable commands — minor gaps versus fully executable code.

4 / 5

Workflow Clarity

Clear Q&A review sequence and an output template with an explicit checklist provide most checkpoints, though an explicit validate/feedback loop for review findings is only implicit.

4 / 5

Progressive Disclosure

A well-organized single-file overview under 50 lines with clear sections and no nested references; no bundle files are needed, satisfying the simple-skill exception.

5 / 5

Total

18

/

20

Passed

Description

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

The description is strong: it explicitly states both what the skill does and when to use it, with a rich set of natural trigger phrases and a clear architectural niche. Minor specificity gaps keep it just below ceiling.

DimensionReasoningScore

Specificity

Lists several concrete actions ('making architectural decisions, planning features, designing new components, reviewing PRs, validating that proposed changes align with Clean Architecture principles') with only minor gaps in named outputs.

4 / 5

Completeness

Explicitly answers both what (architectural guidance and Clean Architecture validation) and when (a clear 'Use when...' clause plus concrete trigger phrases).

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases users would actually say ('review architecture', 'check design', 'does this fit', 'where should this go', 'planning a feature') including synonym variations.

5 / 5

Distinctiveness Conflict Risk

Clear niche in Clean Architecture/TypeScript with distinct triggers like 'where should this go'; minor overlap risk with general code-review skills.

4 / 5

Total

18

/

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
shep-ai/shep
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.