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

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

Quality

Content

42%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 well-structured as an overview with a clear content map, but it is hollow in practice: all referenced detail files are missing and the body itself offers little executable guidance beyond a checklist. Motivational filler in the Core Principle section slightly inflates the token budget.

Suggestions

Add the referenced bundle files (context-discovery.md, trade-off-analysis.md, pattern-selection.md, examples.md, patterns-reference.md) so the content map's navigation actually resolves, or inline the key decision guidance directly in SKILL.md.

Replace the motivational Core Principle bullets with concrete, actionable decision guidance (e.g., when to favor simplicity, how to evaluate a trade-off) that Claude does not already know.

Convert the implicit 'When to Read' ordering into an explicit numbered workflow with validation checkpoints (e.g., confirm constraints before pattern selection, review ADR against checklist before finalizing).

Dimension	Reasoning	Score
Conciseness	Mostly lean, but the 'Core Principle' section restates concepts Claude already knows ('Start simple', 'Removing complexity is MUCH harder than adding') and the 'When to Use' line is vague filler that adds tokens without guidance.	3 / 5
Actionability	The body is a navigation map plus a checklist; the concrete executable guidance (decision trees, ADR templates, trade-off framework) is promised in referenced files that do not exist, leaving only high-level hints.	2 / 5
Workflow Clarity	A rough sequence is implied via the content-map 'When to Read' column and a closing validation checklist, but there is no explicit numbered workflow with validation checkpoints between phases.	3 / 5
Progressive Disclosure	The content-map table is well-signaled with one-level-deep references, but every referenced file (context-discovery.md, trade-off-analysis.md, etc.) is absent from the bundle, so the promised navigation is non-functional.	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.

A strong, concise description that answers both what and when with concrete trigger phrases and third-person voice. Slightly abstract action wording and a few missing synonyms keep specificity and trigger-term quality just below the top anchor.

Dimension	Reasoning	Score
Specificity	Lists several specific actions ('Requirements analysis, trade-off evaluation, ADR documentation'), though they lean abstract rather than concrete operations, placing it at anchor 4 rather than 5.	4 / 5
Completeness	Clearly states what ('Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation.') and an explicit when with concrete trigger phrases ('Use when making architecture decisions or analyzing system design.').	5 / 5
Trigger Term Quality	'making architecture decisions or analyzing system design' gives natural phrases users would say, but misses common synonyms like 'architecting', 'trade-offs', or 'ADRs'.	4 / 5
Distinctiveness Conflict Risk	The 'architecture' niche is mostly distinct with clear triggers, but 'analyzing system design' has minor overlap risk with closely 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/skills/architecture/SKILL.md
Commit: debb2ec

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