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.
28
19%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/software-architecture/SKILL.mdQuality
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 far too broad and vague to serve as an effective skill selector. It essentially claims to cover all of software development without specifying concrete capabilities or a clear niche. The 'quality focused software architecture' framing is undermined by the catch-all trigger clause that encompasses any software-related task.
Suggestions
Narrow the scope to specific architectural concerns (e.g., 'Guides design of system architecture including component decomposition, dependency management, design patterns, and scalability planning') rather than claiming all of software development.
Add a focused 'Use when...' clause with specific trigger scenarios like 'Use when the user asks about system design, architectural patterns, code structure decisions, or trade-off analysis between approaches.'
Remove the catch-all phrase 'in any case that relates to software development' and replace with distinct, concrete triggers that differentiate this skill from general coding assistance.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'write code, design architecture, analyze code' without listing any concrete, specific actions. These are extremely broad categories rather than specific capabilities. | 1 / 3 |
Completeness | It has a weak 'what' ('quality focused software architecture') and a 'when' clause ('when users want to write code, design architecture, analyze code'), but the 'when' is so broad it essentially says 'use for anything software-related', which provides little actionable guidance. | 2 / 3 |
Trigger Term Quality | It includes some relevant keywords like 'write code', 'design architecture', 'analyze code', and 'software development', but these are overly broad and lack specific variations or natural user phrases (e.g., specific languages, frameworks, refactoring, debugging, code review). | 2 / 3 |
Distinctiveness Conflict Risk | The description covers virtually all of software development ('any case that relates to software development'), making it extremely generic and highly likely to conflict with any other coding, architecture, or development-related skill. | 1 / 3 |
Total | 6 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads as a generic software engineering best practices document rather than an actionable skill for Claude. It explains concepts Claude already knows (Clean Architecture, DDD, separation of concerns, early returns) without providing concrete, executable guidance or workflows. The content would benefit greatly from being restructured around specific, actionable workflows with concrete code examples rather than abstract principles.
Suggestions
Replace abstract principles with concrete, executable examples—e.g., show a before/after code refactoring that demonstrates the early return pattern or domain separation, rather than just stating the rule.
Add a clear workflow for architectural analysis: e.g., '1. Identify bounded contexts → 2. Map dependencies → 3. Validate separation → 4. Propose structure' with specific outputs at each step.
Remove content Claude already knows (what Clean Architecture is, what DDD means, basic principles like avoiding code duplication) and focus only on project-specific conventions or non-obvious decisions.
Cut the boilerplate 'When to Use' and 'Limitations' sections, and the redundant anti-patterns section that restates the best practices in negative form—this would reduce token usage by ~30%.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is verbose and explains many concepts Claude already knows well—Clean Architecture, DDD, separation of concerns, early returns, avoiding code duplication, error handling. Much of this is general software engineering wisdom that doesn't add novel information. The anti-patterns section largely restates the best practices section in negative form, and the 'When to Use' and 'Limitations' sections are boilerplate filler. | 1 / 3 |
Actionability | The skill provides no executable code, no concrete commands, no specific examples with input/output, and no copy-paste ready snippets. It reads as a collection of abstract principles and guidelines rather than actionable instructions. Mentions of specific libraries (cockatiel, Auth0, Zustand) are name-drops without usage examples. | 1 / 3 |
Workflow Clarity | There is no sequenced workflow, no multi-step process, and no validation checkpoints. The content is a flat list of principles and rules without any guidance on how to apply them in order or how to verify that architecture decisions are correct. For a skill about software architecture, there should be a clear process for analyzing, designing, and validating architectural decisions. | 1 / 3 |
Progressive Disclosure | The content has some structural organization with headers and sub-sections, making it scannable. However, there are no references to external files for deeper content, and the inline content is lengthy enough that it would benefit from being split. No bundle files are provided, so there's no progressive disclosure structure to leverage. | 2 / 3 |
Total | 5 / 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 | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
76aea27
- 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.