CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

vale

Install, repair, and validate Vale prose linting. Use when users need Vale config, style sync, docs lint gates, or broken Vale workflow diagnosis.

Quality

79%

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 ./Skills/agent-ops/vale/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%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 excels at process discipline: a clear sequenced workflow with explicit fail-fast validation and a fix-rerun loop, all in a lean format. Its main weaknesses are the complete absence of executable Vale commands or concrete file references, and a Progressive Disclosure pointer that does not match the actual bundle layout.

Suggestions

Add concrete, executable Vale commands and file names (e.g., `vale sync`, running `vale` against target docs, editing `.vale.ini`) so the runbook can be executed without inventing steps.

Fix the Progressive Disclosure path to point at the actual bundle files and name them explicitly (references/contract.yaml, evals.yaml, task-profile.json) with one-line descriptions of when to load each.

Remove the verbatim duplicate of the frontmatter description in the opening paragraph and merge the overlapping Philosophy/Avoid/Anti-Patterns bullets to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is lean bullet-style guidance with no concept explanations, but the description is duplicated verbatim in the opening paragraph and "Philosophy" overlaps with "Avoid"/"Anti-Patterns", so minor trimming is possible. Not a 5 because those redundant tokens do not earn their place.

4 / 5

Actionability

The body contains no executable commands or concrete artifacts: no `vale` invocations, no `.vale.ini` path, no style-package location; steps like "Inspect 2-3 focused surfaces" and "Take the smallest action that advances the confirmed goal" are high-level hints missing the specific steps to execute. It is not a 3 because even the guidance present is generic runbook discipline rather than Vale-specific instruction.

2 / 5

Workflow Clarity

The five numbered steps form a clear sequence with explicit validation checkpoints ("Stop at the first failed gate or blocker and report exact evidence") and a fix-then-rerun feedback loop ("Rerun the relevant validation after fixes before claiming completion"), reinforced by the Validation section. No validation gaps remain, so the top anchor fits.

5 / 5

Progressive Disclosure

Section structure is well organized with a dedicated Progressive Disclosure section, but the referenced archive path ("Infrastructure/references/deferred-skill-context/agent-ops-vale/") does not match the actual bundle files (references/contract.yaml, evals.yaml, task-profile.json), which are never named. References are present but not correctly signaled, matching the mid anchor; not a 2 because the body is short and headers make navigation reasonable.

3 / 5

Total

14

/

20

Passed

Description

87%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.

A strong description: concrete actions, an explicit 'Use when...' trigger clause, and a well-defined Vale-specific niche. The only weaknesses are minor gaps in action coverage and a few missing natural trigger variations.

Suggestions

Add one or two concrete artifact-level actions (e.g., style package installation, .vale.ini config authoring) to lift specificity to comprehensive coverage.

Include a few natural user phrasings such as 'styles missing in CI' or 'lint gate failures' to broaden trigger coverage.

DimensionReasoningScore

Specificity

"Install, repair, and validate Vale prose linting" lists several specific actions plus concrete nouns ("Vale config, style sync, docs lint gates, or broken Vale workflow diagnosis"), matching the 'several specific actions; minor gaps' anchor. It is not a 5 because the verbs are broad and coverage of what Vale actually operates on is thin.

4 / 5

Completeness

It explicitly answers both: what ("Install, repair, and validate Vale prose linting") and when ("Use when users need Vale config, style sync, docs lint gates, or broken Vale workflow diagnosis") with concrete trigger phrases, exactly matching the top anchor.

5 / 5

Trigger Term Quality

Natural terms users would say are present ("Vale", "config", "lint", "style sync", "broken Vale workflow"), giving good keyword coverage. A few natural variations are missing (e.g., "styles not found", "lint failures in CI", "prose checks"), so it falls short of the comprehensive-synonym anchor.

4 / 5

Distinctiveness Conflict Risk

"Vale" is a specific named tool with distinct triggers (Vale config, style sync, docs lint gates), forming a clear niche with minimal conflict risk against other skills.

5 / 5

Total

18

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Skills/agent-ops/vale/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.