CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-fix-violations

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

Quality

71%

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 ./packs/svelte/skills/review-fix-violations/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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, actionable instruction list: prioritized concrete fix rules, an exact validation command, and a clear reporting step. Its only real gap is the absence of an explicit failure-handling loop after validation fails.

DimensionReasoningScore

Conciseness

The body is ~40 lines of lean pattern→fix mappings plus one exact validation command, with no padding and no explanations of concepts Claude already knows. It matches 'Lean and efficient; assumes Claude's competence; every token earns its place'.

5 / 5

Actionability

Concrete ordered fix rules ("try/catch in services -> remove, move error handling to load function"), an exact checker invocation, and a copy-paste validation command make the guidance mostly executable, matching 'Mostly executable guidance; concrete code or commands with minor gaps'. Not 5 because entries like "type correctly" and "decompose" give direction without executable detail, and there is no handling for a missing $ARGUMENTS module.

4 / 5

Workflow Clarity

A clear four-step sequence (find via checker, fix by priority tier, validate after each fix, report) with an explicit validation checkpoint on this batch-modification workflow matches 'Clear sequence with most checkpoints present; minor validation gaps'. Not 5 because no error-recovery loop is specified — nothing says what to do when svelte-check or the build fails after a fix (revert or fix forward).

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, and needs no external references; its well-organized sections (## Steps with Critical/Important/Improvements tiers) satisfy the simple-skill exception, so progressive disclosure scores 5 on structure alone.

5 / 5

Total

18

/

20

Passed

Description

45%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 a clear, explicit trigger clause but a vague capability statement — it says when to use the skill without saying concretely what it does or operates on. Trigger vocabulary is narrow and distinctiveness from sibling review skills is only moderate.

Suggestions

State the 'what' concretely, e.g.: 'Fixes docs/ARCHITECTURE.md violations (error handling placement, Svelte 4-to-5 migrations, sanitization, typing) in a specified module, in priority order. Use when architecture violations were found and need automated fixing.'

Add natural trigger variations users might say, such as 'arch violations', 'fix violations', or 'architecture review findings', to broaden trigger coverage.

Distinguish the skill from the checker explicitly (e.g., 'fixes violations found by /review-check-architecture') to reduce conflict risk with sibling review skills.

DimensionReasoningScore

Specificity

The description names the domain ("architecture violations") but its only action is the generic "automated fixing by priority", matching the anchor 'Names the domain but actions are minimal or generic'. It never states what is actually fixed (ARCHITECTURE.md, a module, specific patterns), so it does not reach the 3 anchor's 1-2 concrete actions.

2 / 5

Completeness

The 'when' is explicit ("Use when architecture violations were found") but the 'what' is weak — "need automated fixing by priority" never specifies what gets fixed or how, the mirror image of anchor 3 (one half clear, the other weak). It does not reach 4 because the 'what' is far vaguer than concrete action lists like 'Extract text from PDFs and fill forms'.

3 / 5

Trigger Term Quality

"architecture violations" is a phrase a user might naturally say, but the description includes no synonyms or variations (e.g., "arch violations", "fix violations", "architecture review"), matching 'Some relevant keywords but missing common variations or synonyms'. It is above the 2 anchor because the one keyword present is domain-specific rather than generic.

3 / 5

Distinctiveness Conflict Risk

"Architecture violations... automated fixing" carves out a niche but can overlap with the sibling checker skill (/review-check-architecture) and generic lint/fix skills, matching 'Somewhat specific but could still overlap with similar skills'. Not 4 because no scope details reinforce the fix-vs-check distinction.

3 / 5

Total

11

/

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/svelte/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.