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

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./Skills/agent-ops/vale/SKILL.md

Quality

Content

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

A well-organized runbook body with clear sequencing and validation feedback loops, but it lacks concrete Vale-specific commands or config examples, relying on abstract process guidance and deferred references that don't align with the provided bundle.

Suggestions

Add at least one concrete, executable Vale command or config snippet (e.g., `vale sync`, a minimal `.vale.ini`, or a pre-commit hook yaml) to lift actionability beyond high-level hints.

Reconcile the deferred-reference path with the actual bundle: either link the real `references/contract.yaml` and `references/evals.yaml` from the body, or note why the archived `Infrastructure/references/...` path is the correct entry point.

Tighten the Philosophy section by converting abstract aphorisms into Vale-specific guidance so every line earns its context-window cost.

Dimension	Reasoning	Score
Conciseness	The body is lean with short bullets and avoids explaining concepts Claude already knows, though abstract process aphorisms ("evidence-first", "smallest reversible step") could be trimmed slightly for tighter token efficiency.	4 / 5
Actionability	The workflow gives only high-level hints ("Classify the requested mode", "Take the smallest action") with no concrete Vale commands, config examples, or executable code, leaving the specific steps to execute missing.	2 / 5
Workflow Clarity	A clear five-step sequence with explicit validation checkpoints ("Stop at the first failed gate", "Rerun the relevant validation after fixes") provides a feedback loop, but the steps themselves are abstract rather than concrete, leaving minor gaps.	4 / 5
Progressive Disclosure	The body is well sectioned with a dedicated Progressive Disclosure section signaling one-level-deep deferred references, but the signaled archived path does not match the actual bundle files (contract.yaml, evals.yaml, task-profile.json are unreferenced), a minor organization gap.	4 / 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, well-structured description that clearly states the skill's purpose and explicit triggers for a distinct named tool. Minor room to add synonyms and file extensions for fuller trigger coverage.

Dimension	Reasoning	Score
Specificity	"Install, repair, and validate Vale prose linting" names three concrete actions covering the Vale lifecycle, but the verbs are somewhat high-level and omit standalone configure/author-style actions, leaving minor coverage gaps rather than full comprehensiveness.	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.	5 / 5
Trigger Term Quality	"Vale config, style sync, docs lint gates, broken Vale workflow diagnosis" are natural terms a user would say, but synonyms (prose linter, linting) and file extensions (.vale.ini, styles paths) are missing, so coverage is good rather than comprehensive.	4 / 5
Distinctiveness Conflict Risk	Vale is a named, specific tool with distinct triggers (Vale config, style sync, docs lint gates), giving it a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: jscraik/Agent-Skills
Path: Skills/agent-ops/vale/SKILL.md
Commit: f1f2f21

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.