architecture

Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/architecture/SKILL.md

Quality

Content

61%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 well-structured, lean overview that organizes navigation nicely, but it leans on reference files that are missing from the bundle, leaving the core actionable framework (trade-off analysis, ADR templates, decision trees) unprovided. The generic When-to-Use and Limitations boilerplate adds little value.

Suggestions

Ship the referenced bundle files (context-discovery.md, trade-off-analysis.md, pattern-selection.md, examples.md, patterns-reference.md) or inline the essential framework (an ADR template and a trade-off evaluation matrix) so the skill is actionable standalone.

Replace the generic 'When to Use' and 'Limitations' boilerplate with skill-specific guidance, or remove it to tighten the body.

Add an explicit sequenced workflow (discover context -> analyze trade-offs -> select pattern -> document ADR -> validate) with validation checkpoints instead of relying on the content map's implicit ordering.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and useful (content map, principles, checklist), with only minor trimmable boilerplate in the generic 'When to Use' and 'Limitations' sections; not 5 because that boilerplate could be removed.	4 / 5
Actionability	The validation checklist and content map provide some concrete guidance, but the actual decision framework (trade-off matrix, ADR template, decision trees) is absent and merely pointed at files that do not exist in the bundle.	3 / 5
Workflow Clarity	An implied sequence exists via content-map ordering plus a final validation checklist, but there is no explicit step-by-step workflow with validation checkpoints; not 2 because a rough sequence and a checklist are present.	3 / 5
Progressive Disclosure	The content map is a well-signaled, one-level-deep navigation table with 'When to Read' guidance; held below 5 because the referenced .md files are not present in any bundle directory.	4 / 5
	Total	14 / 20 Passed

Description

75%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 solid, third-person description that covers what the skill does and when to use it with concrete trigger phrases. The main gap is limited synonym coverage in the triggers and a lack of explicit user-mention framing.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Requirements analysis, trade-off evaluation, ADR documentation') with minor coverage gaps; falls short of 5 because the action set is not fully comprehensive.	4 / 5
Completeness	Clearly answers both what ('Architectural decision-making framework...') and when ('Use when making architecture decisions or analyzing system design'); not 5 because the 'when' lacks user-mention framing (e.g., 'when the user asks about...').	4 / 5
Trigger Term Quality	Natural user phrases ('architecture decisions', 'system design') give good keyword coverage, but common synonyms ('system architecture', 'tech decisions') are missing, so it stops short of 5.	4 / 5
Distinctiveness Conflict Risk	Targets a clear architecture-decision niche with distinct triggers; 'analyzing system design' is broad enough to risk minor overlap with related design skills, keeping it below 5.	4 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/architecture/SKILL.md
Commit: 1f67c44

Reviewed: about 16 hours ago

Table of Contents

Discovery Implementation Validation

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.