CtrlK
BlogDocsLog inGet started
Tessl Logo

architecture-review

Review a change for architectural drift, guardrail weakening, and ADR impact before shipping.

68

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, well-structured review checklist with concrete checks, executable validation commands, and a clear findings format including a terminal-state message. It assumes Claude's competence and adds only domain-specific guidance.

DimensionReasoningScore

Conciseness

The body is lean with no over-explanation of concepts Claude already knows (no definition of ADRs or guardrails); every section earns its place, matching the 'lean and efficient' anchor.

3 / 3

Actionability

Concrete file paths to inspect (`.github/workflows/**`, `AGENTS.md`, `scripts/adr_guard/**`), two executable `python3 scripts/adr_guard/adr_guard.py` commands, and a precise findings format give copy-paste-ready guidance.

3 / 3

Workflow Clarity

As a simple review skill it has an unambiguous single task with numbered focus areas, automated validation commands, and an explicit terminal state ("If no issues are found, say: ..."), satisfying the simple-skill allowance for a 3.

3 / 3

Progressive Disclosure

Under 50 lines with no need for external references, organized into clear sections (Focus Areas, Commands, Findings Format); no bundle files are present and no broken reference links exist, so the well-organized-sections criterion yields a 3.

3 / 3

Total

12

/

12

Passed

Description

67%

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 occupies a clear niche, but it lacks an explicit user-facing 'Use when...' trigger and relies on terse, somewhat jargon-heavy phrasing for when to invoke it. Adding natural trigger terms would lift the weaker completeness and trigger dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when reviewing a change or PR before shipping to catch architecture, guardrail, or ADR issues.'

Include natural user-facing keywords users would actually say, such as 'architecture review', 'ADR', 'guardrails', or 'before shipping this change'.

Expand the 'when' beyond the terse 'before shipping' to describe the user situations that should invoke the skill.

DimensionReasoningScore

Specificity

"Review a change for architectural drift, guardrail weakening, and ADR impact" names three concrete, distinct review concerns rather than vague language, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

The 'what' is clearly stated, and 'before shipping' gives a minimal when, but there is no explicit 'Use when...' clause or equivalent user-facing trigger guidance, so completeness caps at 2 per the guidelines.

2 / 3

Trigger Term Quality

Terms like "architectural drift", "guardrail weakening", and "ADR impact" are relevant to the domain but are somewhat jargon-heavy and lack common natural variations or a user-facing trigger phrase, fitting 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

The architecture/ADR/guardrail niche is specific and clearly distinguishable from general skills, making it unlikely to trigger for the wrong skill.

3 / 3

Total

10

/

12

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

referenced_paths_exist

Referenced path issues: 3 missing, 2 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository
PaloAltoNetworks/shifter
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.