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 ./.agents/skills/architecture/SKILL.md

The canonical home for this skill is architecture in sickn33/antigravity-awesome-skills

Quality

Content

50%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 concise and well-structured as an overview, but its actionability and progressive disclosure are undermined because the reference files it directs Claude to are absent from the bundle. Workflow clarity is moderate: a checklist exists but the process sequence is only implicit.

Suggestions

Ship the referenced files (context-discovery.md, trade-off-analysis.md, pattern-selection.md, examples.md, patterns-reference.md) in a references/ directory so the signaled navigation is actually fulfillable.

Add at least minimal concrete guidance inline (e.g., a short ADR template skeleton or a trade-off matrix example) so the skill is actionable before any reference file is opened.

Lay out the architecture process as an explicit ordered sequence with validation/fix feedback loops rather than relying on a checkbox checklist alone.

Dimension	Reasoning	Score
Conciseness	Lean tables and terse bullets assume Claude's competence with no concept over-explanation; only the aphoristic 'Core Principle' framing and near-synonymous complexity bullets are minor trim candidates.	4 / 5
Actionability	Guidance is high-level — a reading table and a checklist that point to other files rather than providing concrete steps, code, or commands; the actual executable detail lives in reference files that are not present in the bundle.	2 / 5
Workflow Clarity	A validation checklist provides some checkpoints and the reading table maps stage to file, but there is no explicit ordered sequence or fix/retry loop; checkpoints are implicit rather than sequenced.	3 / 5
Progressive Disclosure	The body uses a well-signaled one-level-deep reference table, but the referenced files (context-discovery.md, trade-off-analysis.md, etc.) do not exist in any references/ bundle, so the signaled navigation cannot be fulfilled.	3 / 5
	Total	12 / 20 Passed

Description

87%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 is strong: it explicitly answers both 'what' and 'when' with concrete trigger phrases and carves out a distinct, low-conflict niche. Specificity and trigger-term coverage are solid but could add a few more concrete actions or synonyms to reach the top anchor.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Requirements analysis, trade-off evaluation, ADR documentation') with minor gaps in coverage, matching the several-specific-actions anchor rather than the comprehensive 5.	4 / 5
Completeness	Explicitly states both what it does ('Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation.') and when to use it ('Use when making architecture decisions or analyzing system design.'), with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural keyword coverage ('architecture decisions', 'trade-offs', 'ADRs', 'system design'), though a few common synonyms and file/extension variations are missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (architectural decision-making / ADRs) with distinct triggers and an explicit delimitation ('NOT for direct code implementation'), giving minimal conflict risk.	5 / 5
	Total	18 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: vudovn/ag-kit
Path: .agents/skills/architecture/SKILL.md
Commit: 211561c

Reviewed: 8 days 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.