CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-fix-violations

Use when architecture violations were found and need automated fixing by priority.

Quality

81%

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

93%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 an exemplary lean instruction skill: concrete violation-to-fix mappings ordered by priority, a copy-paste validation command applied after each fix, and a closing report step, all with zero padding. The only gap is the absence of an explicit failure-recovery loop (what to do when validation fails after a fix).

DimensionReasoningScore

Conciseness

The body is a lean priority-ordered mapping of violation pattern to remediation ("try/catch in services -> remove, move error handling to composable") with one executable validation command, no padding, and no explanations of concepts Claude already knows. Every token earns its place.

5 / 5

Actionability

Guidance is fully executable for an instruction-only skill: a copy-paste validation command ("nuxi typecheck && nuxi build && npx vitest run --passWithNoTests"), concrete pattern-to-fix directives with named examples ("$axios, asyncData, this.$store -> Nuxt 3 equivalents", "Hardcoded secrets -> move to env vars / runtimeConfig"), and specific companion skills to invoke. These cover the common cases.

5 / 5

Workflow Clarity

The four steps are clearly sequenced (find via /review-check-architecture, fix in priority order, validate after each fix, report), with an explicit per-fix validation checkpoint and exact command. It misses 5 because there is no error-recovery feedback loop (e.g., "if validation fails, revert the fix and retry"), which matters in this batch code-modification context.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, and needs no external references; the body is well organized with a clear intro, numbered Steps, bold priority tiers, and a fenced command block. Per the simple-skill exception, well-organized sections alone merit a 5.

5 / 5

Total

19

/

20

Passed

Description

62%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 has an explicit 'Use when' trigger and names both the domain (architecture violations) and the action (automated fixing by priority), but it is terse: it lists only one action and misses natural trigger variations. It is functional and distinct within its suite, yet below the strong examples that enumerate concrete capabilities and trigger phrases.

Suggestions

Enumerate the concrete fixes in the description to raise specificity, e.g., "Fixes architecture violations by priority: try/catch in services, unsanitized v-html, hardcoded secrets, missing Zod validation, Options API components, Nuxt 2 patterns."

Add natural trigger variations for discoverability, such as "Use when architecture violations were found in a review, when the user asks to fix architecture issues or ARCHITECTURE.md violations, or after running /review-check-architecture."

Mention the validation loop (typecheck, build, tests) to make the 'what' more complete and differentiate the skill from a pure edit-and-hope fixer.

DimensionReasoningScore

Specificity

"architecture violations" names the domain and "automated fixing by priority" gives one concrete action, matching the anchor for domain plus 1-2 actions without comprehensive coverage. It does not list several specific actions (not 4), and the action is more concrete than purely generic (not 2).

3 / 5

Completeness

Both parts are present: the 'what' ("automated fixing by priority" of architecture violations) and an explicit 'when' ("Use when architecture violations were found"). It falls short of 5 because the 'when' clause lacks concrete trigger phrases and the 'what' is thin; it exceeds 3 because the 'when' is explicitly stated, not merely implied.

4 / 5

Trigger Term Quality

"architecture violations" and "fixing" are relevant natural keywords a user might say, but common variations and synonyms (e.g., "fix architecture issues", "ARCHITECTURE.md compliance", "architecture review findings") are missing. Keyword coverage is present but not good enough for 4.

3 / 5

Distinctiveness Conflict Risk

"architecture violations" plus "automated fixing by priority" carves a clear niche that is mostly distinct, with only minor overlap risk against the companion checker skill (/review-check-architecture) and general lint-fixing skills. It is not fully 5 because the terse phrasing gives less trigger separation from the checker.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

fernandezbaptiste/specialist-agent

Path

packs/nuxt/skills/review-fix-violations/SKILL.md

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.