CtrlK
BlogDocsLog inGet started
Tessl Logo

system-architecture

Design systems with appropriate complexity - no more, no less. Use when the user asks to architect applications, design system boundaries, plan service decomposition, evaluate monolith vs microservices, make scaling decisions, or review structural trade-offs. Applies to new system design, refactoring, and migration planning.

69

Quality

85%

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

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

A dense, well-structured architecture skill with a clear sequenced workflow, explicit complexity-gate validation, anti-pattern guidance, and an output template. Progressive disclosure is sound with one-level references, though referenced bundle files were not present to verify.

DimensionReasoningScore

Conciseness

Lean and dense, with almost every line carrying actionable or decision-relevant content and no padding explaining concepts Claude already knows; a few principle restatements keep it just below a 5.

4 / 5

Actionability

Provides concrete guidance — a constraint-question table, a complexity checklist, anti-pattern table, and a fillable output template — though guidance is procedural/heuristic rather than executable code, leaving minor gaps.

4 / 5

Workflow Clarity

A six-step workflow with a tracked-progress block, an explicit complexity checklist with a 'keep it simple if no' decision gate, and a structured output template — clear sequence with explicit validation checkpoints.

5 / 5

Progressive Disclosure

Well-organized sections with two clearly signaled one-level-deep references ([examples.md], [scaling-checklist.md]) for detail; the referenced bundle files are not present, so structure is good but verifiable file placement is not confirmed.

4 / 5

Total

17

/

20

Passed

Description

88%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, third-person description with explicit 'Use when' triggers and concrete capability verbs. It clearly distinguishes the architecture-design niche and enumerates natural trigger phrases a user would actually say.

DimensionReasoningScore

Specificity

Lists several concrete architectural actions ('architect applications, design system boundaries, plan service decomposition, evaluate monolith vs microservices, make scaling decisions, or review structural trade-offs'), with minor gaps in coverage relative to the body's full scope.

4 / 5

Completeness

Explicitly answers what ('Design systems with appropriate complexity') and when ('Use when the user asks to...') with concrete trigger phrases, plus scope ('new system design, refactoring, and migration planning').

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage spanning 'architect applications', 'design system boundaries', 'plan service decomposition', 'monolith vs microservices', 'scaling decisions', and 'review structural trade-offs' — phrases users would naturally say.

5 / 5

Distinctiveness Conflict Risk

Clear niche (system architecture trade-offs and decomposition) with minimal conflict risk; slight overlap with general software-design skills keeps it just below a 5.

4 / 5

Total

18

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

16

Passed

Repository
MODSetter/SurfSense
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.