CtrlK
BlogDocsLog inGet started
Tessl Logo

software-architecture

Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.

50

Quality

55%

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 ./skills/software-architecture/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

47%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 set of architecture principles with concrete thresholds, but it re-explains familiar concepts, lacks executable examples, and offers no real workflow despite framing itself around an architecture development process.

Suggestions

Trim explanations of well-known concepts (Clean Architecture, DDD, NIH) and keep only the non-obvious directives.

Add a concrete worked example (e.g., a short before/after snippet) showing the rules applied, rather than a placeholder user request.

Replace the circular 'When to Use' section with an explicit sequence of steps for approaching an architecture task.

DimensionReasoningScore

Conciseness

Mostly efficient bullet-list format, but it explains concepts Claude already knows (Clean Architecture, DDD, NIH syndrome) and could be tightened, fitting 'mostly efficient but includes some unnecessary explanation or could be tightened'.

3 / 5

Actionability

Provides specific actionable thresholds (80-line functions, 200-line files, max 3 levels nesting) and concrete tooling hints (cockatiel for retries), but lacks executable code examples showing how to apply the rules, fitting 'some concrete guidance but incomplete; missing key details'.

3 / 5

Workflow Clarity

Despite framing architecture work as a process, there is no sequenced workflow; the 'When to Use' section is circular ('applicable to execute the workflow or actions described in the overview') and no workflow is actually described, matching 'rough sequence present but many gaps; steps poorly defined'.

2 / 5

Progressive Disclosure

Well-organized into clear sections (General Principles, Best Practices, Anti-Patterns, Code Quality) with no external references needed; slightly over 50 lines with some inline content that could be split, fitting 'good structure; most content is appropriately placed; minor organization gaps'.

4 / 5

Total

12

/

20

Passed

Description

62%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 states both what the skill does and when to use it with reasonable trigger terms, but its actions are generic and the 'any case that relates to software development' scope creates high conflict risk with other coding skills.

Suggestions

Replace the broad 'in any case that relates to software development' trigger with specific scenarios (e.g., 'when designing system structure, defining domain boundaries, or planning module separation').

List more concrete architectural actions (e.g., 'structure modules by bounded context, separate domain logic from infrastructure') instead of generic 'write code, analyze code'.

Narrow the niche so it is distinguishable from general coding skills.

DimensionReasoningScore

Specificity

Names the domain ('quality focused software architecture') and a few actions ('write code, design architecture, analyze code'), but the actions are generic rather than concretely specified, matching the 'names domain and 1-2 concrete actions but not comprehensive' anchor.

3 / 5

Completeness

Provides both a 'what' (guide for quality focused software architecture) and an explicit 'when' ('This skill should be used when users want to write code, design architecture, analyze code'), but the 'when' clause is partly broad ('in any case that relates to software development'), so it falls short of the fully concrete anchor 5.

4 / 5

Trigger Term Quality

Includes natural phrases users would say ('write code', 'design architecture', 'analyze code', 'software development') with good coverage, though a few common synonyms are missing, fitting the 'good keyword coverage; a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

The trigger 'in any case that relates to software development' is extremely broad and would overlap with virtually any coding skill, fitting 'very broad; high overlap risk with many similar skills' rather than the more distinct anchor 3.

2 / 5

Total

13

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
sickn33/antigravity-awesome-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.