architecture

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

50%

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 and lean, but it functions mainly as a pointer to five reference files that do not exist, leaving the actual architecture guidance (templates, decision trees, examples) missing.

Suggestions

Provide the referenced bundle files (context-discovery.md, trade-off-analysis.md, pattern-selection.md, examples.md, patterns-reference.md) or inline their key guidance so the skill is self-sufficient.

Replace the aphoristic Core Principle and generic "When to Use" boilerplate with a concrete, sequenced architecture workflow with validation checkpoints.

Add at least one concrete artifact in the body (e.g. an ADR template skeleton or a trade-off decision-tree) so the skill is actionable without the missing references.

Dimension	Reasoning	Score
Conciseness	The body is short and assumes Claude's competence, but aphorisms ("Simplicity is the ultimate sophistication") and generic "When to Use"/"Limitations" boilerplate do not all earn their tokens.	2 / 3
Actionability	A validation checklist and a content map give some concrete guidance, but the substantive actionable material (ADR templates, decision trees, examples) is delegated to files that are not present in the bundle.	2 / 3
Workflow Clarity	A validation checklist provides a checkpoint, but there is no sequenced multi-step process for conducting architecture design in the body — the workflow lives only in the missing referenced files.	2 / 3
Progressive Disclosure	The content map is well-organized and one level deep, but every referenced file (context-discovery.md, trade-off-analysis.md, pattern-selection.md, examples.md, patterns-reference.md) is absent from references/, so navigation is broken.	2 / 3
	Total	8 / 12 Passed

Description

77%

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 description with an explicit Use-when trigger and several concrete actions, though its trigger vocabulary is narrow and the "system design" phrasing risks overlap with sibling design skills.

Suggestions

Broaden trigger terms to include natural variations users say, e.g. "scalability", "design review", "system architecture", or "high-level design".

Tighten the when-clause to a more distinctive trigger (e.g. "Use when making architectural decisions or documenting trade-offs as ADRs") to reduce overlap with other design skills.

Consider dropping the generic "framework" label so the description leads with concrete actions.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Requirements analysis, trade-off evaluation, ADR documentation" — beyond a vague domain label, matching the multiple-specific-actions anchor.	3 / 3
Completeness	Clearly answers both what (the action list) and when via an explicit "Use when making architecture decisions or analyzing system design" clause.	3 / 3
Trigger Term Quality	Includes natural phrases ("architecture decisions", "system design", "trade-off", "ADR") but misses common variations users say like "scalability", "design review", or "system architecture".	2 / 3
Distinctiveness Conflict Risk	The ADR/trade-off niche is distinct, but "analyzing system design" is broad enough to overlap with related design skills such as database-design or api-patterns.	2 / 3
	Total	10 / 12 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: boisenoise/skills-collections
Commit: f36337d

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