CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

architect-review

Master software architect specializing in modern architecture

Quality

42%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/architect-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

28%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 opens well (use/don't-use triggers, brief instructions, safety notes) but then devolves into a padded persona resume enumerating technologies and principles Claude already knows. It provides almost no executable review procedure, output format, or validation guidance.

Suggestions

Delete the Expert Purpose, Capabilities, Behavioral Traits, and Knowledge Base sections — they enumerate standard knowledge (SOLID, Kafka, C4, DDD) Claude already has and consume most of the token budget; move any genuinely non-obvious criteria to a reference file.

Merge the Instructions and Response Approach lists into one sequenced review workflow with concrete checkpoints: what artifacts to request, what criteria to evaluate against, and explicit validation (e.g. confirm assumptions with the user before rating High/Medium/Low impact).

Add a concrete output format, such as findings ranked by architectural impact with trade-offs and a minimal ADR template, and replace the abstract Example Interactions with one worked example of input and expected review output.

DimensionReasoningScore

Conciseness

Roughly 130 of 170 lines are Capabilities, Behavioral Traits, and Knowledge Base sections that name-drop concepts Claude already knows (SOLID, Kafka, circuit breakers, the C4 model), plus two redundant step lists (Instructions and Response Approach); the efficient front sections keep it above anchor 1's 'severely verbose' but it is noticeably padded.

2 / 5

Actionability

The guidance is abstract — "Gather system context", "Evaluate architecture decisions and identify risks", "Recommend improvements with tradeoffs" — with no concrete commands, output formats, review checklists, or worked examples, matching anchor 2 ('high-level hints but missing the specific steps to execute').

2 / 5

Workflow Clarity

Two competing, loosely defined step lists exist (Instructions 1-4 and Response Approach 1-8) with no validation checkpoints or error-recovery loops, matching anchor 2 ('Rough sequence present but many gaps; steps poorly defined; validation absent').

2 / 5

Progressive Disclosure

Sections are clearly labeled (no bundle files exist, so there are no broken references), but ~130 lines of capability and knowledge lists are inlined in SKILL.md that belong in reference files or should simply be cut, matching anchor 3 ('Some structure but could be better organized; content that should be separate is inline').

3 / 5

Total

9

/

20

Passed

Description

28%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 a persona tagline rather than a functional description: it names a domain but lists no concrete actions and provides no use-when trigger guidance. It would rarely be selected confidently over related review skills.

Suggestions

Rewrite the description to state concrete actions, e.g. "Reviews system architectures and major design changes for scalability, resilience, security, and maintainability; identifies anti-patterns and recommends improvements with trade-offs."

Add an explicit trigger clause with natural user phrases, e.g. "Use when reviewing architecture or system design, evaluating microservice boundaries, choosing between architectural patterns, or assessing scalability and trade-offs."

Avoid the vague modifier "modern architecture" — replace it with the concrete subdomains the skill actually covers (microservices, event-driven design, DDD, clean architecture).

DimensionReasoningScore

Specificity

The description names the domain ("software architect", "modern architecture") but contains no concrete actions — "Master software architect specializing in" is a persona label, not a capability, matching the anchor 'Names the domain but actions are minimal or generic' rather than anchor 3 which requires 1-2 concrete actions.

2 / 5

Completeness

There is a vague 'what' (a persona specializing in architecture, with no stated actions) and no 'when' clause at all, which matches anchor 2 ('Has a vague what and no when'); it is above anchor 1 only because the domain is explicitly named.

2 / 5

Trigger Term Quality

It offers essentially one keyword ("architecture") repeated twice; natural phrases a user would say such as 'architecture review', 'system design', or 'scalability' are absent, fitting anchor 2 ('one or two generic keywords; missing the natural phrases users say') rather than anchor 3's 'some relevant keywords'.

2 / 5

Distinctiveness Conflict Risk

"Master software architect specializing in modern architecture" carves out a stated niche but the broad architecture domain overlaps with code-review, refactoring, and security-review skills, matching anchor 3 ('Somewhat specific but could still overlap with similar skills').

3 / 5

Total

9

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

BigSimmo/Communication

Path

.agents/skills/architect-review/SKILL.md

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.