architecture

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

1.18x

Quality

63%

Does it follow best practices?

Impact

98%

1.18x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/architecture/SKILL.md

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

Quality

Content

43%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 lean and well-structured on the surface, but it lacks concrete actionable guidance and a real sequenced workflow, deferring all specifics to reference files that are missing from the bundle.

Suggestions

Add a minimal inline ADR template and a concrete trade-off evaluation example so the skill is actionable without relying on absent reference files.

Either provide the five referenced files (context-discovery.md, trade-off-analysis.md, pattern-selection.md, examples.md, patterns-reference.md) or remove the content-map table that points to them.

Convert the Validation Checklist into a short sequenced workflow (e.g. discover context -> evaluate trade-offs -> document ADR -> validate) with explicit checkpoints.

Dimension	Reasoning	Score
Conciseness	The body is short and free of padding or explanations Claude already knows, but the epigraph quotes and the platitudinous Core Principle ('Simplicity is the ultimate sophistication') are minor tokens that do not earn their place.	4 / 5
Actionability	Provides only high-level hints ('Start simple', 'Add complexity ONLY when proven necessary') and a checklist of reminders; the concrete guidance (ADR templates, trade-off framework) is deferred to reference files that are not present, leaving the body without executable specifics.	2 / 5
Workflow Clarity	The Validation Checklist lists pre-finalization reminders rather than a sequenced process, and there is no clear ordered workflow or error-recovery checkpoints for the architecture-decision task.	2 / 5
Progressive Disclosure	The content map table is well-organized with File/Description/When-to-Read columns and clearly signaled references, but the five referenced files (e.g. context-discovery.md, trade-off-analysis.md) do not exist in the bundle, breaking navigation.	3 / 5
	Total	11 / 20 Passed

Description

83%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 concisely states what the skill does and gives explicit trigger guidance using third-person voice. Its main weakness is slightly abstract action phrasing and minor overlap risk with related design skills.

Dimension	Reasoning	Score
Specificity	Names the architecture domain plus three concrete actions ('Requirements analysis, trade-off evaluation, ADR documentation'), which is several specific actions but not the comprehensive coverage of the 5-anchor.	4 / 5
Completeness	Explicitly answers both what ('Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation.') and when ('Use when making architecture decisions or analyzing system design.') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('making architecture decisions', 'analyzing system design') with good coverage, but lacks synonyms and broader variations found in the 5-anchor.	4 / 5
Distinctiveness Conflict Risk	Has a clear niche (architecture decisions) with distinct triggers, though 'analyzing system design' creates minor overlap risk with related design skills.	4 / 5
	Total	17 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/architecture/SKILL.md
Commit: 900c504

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