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.
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill software-architecture52
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is too vague and overly broad to be useful for skill selection. The phrase 'any case that relates to software development' makes it a catch-all that would conflict with most technical skills. It lacks specific concrete actions and distinct trigger terms that would help Claude choose this skill appropriately.
Suggestions
Narrow the scope significantly - specify what 'quality focused' means (e.g., 'Designs scalable system architectures, creates UML diagrams, reviews code for SOLID principles violations')
Replace the overly broad 'when' clause with specific triggers like 'Use when users ask about system design, architectural patterns, microservices, or need help structuring large codebases'
Add concrete deliverables or outputs (e.g., 'produces architecture diagrams, design documents, code structure recommendations')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'write code, design architecture, analyze code' without listing concrete actions. It doesn't specify what kind of architecture, what analysis methods, or what outputs are produced. | 1 / 3 |
Completeness | Has a weak 'what' (quality focused software architecture guide) and includes a 'when' clause, but the 'when' is overly broad ('any case that relates to software development') making it essentially useless for skill selection. | 2 / 3 |
Trigger Term Quality | Contains some relevant keywords ('code', 'architecture', 'software development') but these are extremely broad. Missing specific variations users might say like 'refactor', 'design patterns', 'system design', 'code review', etc. | 2 / 3 |
Distinctiveness Conflict Risk | Extremely generic scope ('any case that relates to software development') would conflict with virtually any coding, debugging, testing, or development-related skill. No clear niche is established. | 1 / 3 |
Total | 6 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a solid foundation of software architecture principles covering Clean Architecture, DDD, and coding best practices. However, it reads more like a reference document than an actionable skill - it tells Claude what to do conceptually but lacks concrete code examples, decision workflows, and validation steps that would make it immediately executable.
Suggestions
Add concrete code examples showing early return patterns, proper error handling, and library usage (e.g., actual cockatiel retry implementation)
Create a decision workflow/flowchart for 'library vs custom code' decisions with explicit validation steps
Split detailed guidance (DDD principles, anti-patterns catalog) into separate reference files and link from a leaner overview
Remove the generic 'When to Use' section which adds no actionable information
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary elaboration. Phrases like 'This skill provides guidance for quality focused software development' and the 'When to Use' section add little value. Some bullet points could be tightened. | 2 / 3 |
Actionability | Provides principles and guidelines but lacks concrete, executable examples. Mentions libraries like 'cockatiel', 'Auth0', 'Redux/Zustand' but doesn't show actual code snippets demonstrating usage. The guidance is descriptive rather than copy-paste ready. | 2 / 3 |
Workflow Clarity | The skill presents guidelines as lists but lacks a clear workflow sequence for how to approach architecture decisions. No validation checkpoints or decision trees for when to use libraries vs custom code. The structure is more of a reference checklist than a guided process. | 2 / 3 |
Progressive Disclosure | Content is organized into logical sections with headers, but everything is inline in one document. For a skill of this scope covering Clean Architecture, DDD, and multiple best practices, it would benefit from linking to separate detailed references for each major topic area. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.