CtrlK
BlogDocsLog inGet started
Tessl Logo

architectural-review

How to review PRs for architectural quality — module boundaries, dependency direction, export surface, pattern consistency

62

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.copilot/skills/architectural-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 content is highly actionable and well-structured, with concrete rules, specific paths, and worked examples that cover common architectural review cases. It is efficient with only minor verbosity and clear navigation, though progressive disclosure could be improved by splitting dense sections into reference files.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence, using checklists, tables, and terse rules rather than explaining what PRs or architectures are; minor redundancy (e.g., protected-files table echoed by the sweeping-refactor checklist) keeps it just short of fully lean.

4 / 5

Actionability

Provides concrete decision rules (REJECT/APPROVE with reasons), specific file paths, an authoritative protected-files table, and five worked examples with explicit findings and recommendations, fully covering the common cases for an instruction-only skill.

5 / 5

Workflow Clarity

Clear structure from trigger conditions through eight review patterns to a structured output format with verdicts and severity levels; it is a read-only review rather than a destructive workflow, and verification guidance (e.g., batched testing, line-by-line deletion review) is present with only minor checkpoint gaps.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections (Context, Patterns, Examples, Review Output Format, Anti-Patterns) with one well-signaled external reference to the sibling proposals skill; no bundle files exist, and the cohesive review guidance is appropriately inline, though at ~200 lines some patterns/examples could optionally be split out.

4 / 5

Total

17

/

20

Passed

Description

66%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 specific and reasonably distinct, naming concrete architectural concerns, but it omits any 'Use when...' trigger guidance, which caps completeness. Adding an explicit trigger clause would raise the score meaningfully.

Suggestions

Add a 'Use when...' clause naming concrete triggers, e.g. 'Use when reviewing PRs that add modules, change package dependencies, modify barrel exports, or apply sweeping refactors.'

Include a natural synonym such as 'pull request' alongside 'PR' to improve trigger-term coverage.

Clarify the boundary against the sibling proposals skill directly in the description to reduce conflict risk.

DimensionReasoningScore

Specificity

Names the domain ('review PRs for architectural quality') and lists several concrete review concerns ('module boundaries, dependency direction, export surface, pattern consistency'), but the verb is a single action ('review') rather than multiple distinct operations, leaving minor coverage gaps.

4 / 5

Completeness

The 'what' is clear (review PRs for architectural quality across four named concerns), but there is no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes natural phrases users would say ('review PRs', 'architectural quality', 'module boundaries') with good keyword coverage, though synonyms like 'pull request' and 'API surface' are missing.

4 / 5

Distinctiveness Conflict Risk

The architectural niche with specific concerns (dependency direction, export surface) is mostly distinct, with only minor overlap risk against generic code-review skills; not a 5 because it lacks an explicit trigger that would fully separate it from sibling review skills.

4 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
bradygaster/squad
Reviewed

Table of Contents

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.