Each of these would send a user down a path Vale does not support: Core options placed under a glob header are not scoped to that glob — Vale rejects them with E201, so the guidance to nest them produced a config that will not load. The built-in `Vale` style is compiled in, but Vale still requires StylesPath to exist on disk before it will run, so the "no StylesPath needed" shortcut fails. The MDX guidance was inverted: under `[formats] mdx = md` the mapping is what makes MDX lint at all, and it needs the mdx2vast prerequisite that was never mentioned. And a spelling rule's `ignore` paths resolve against StylesPath, not against the rule file's own directory, so the documented relative paths silently matched nothing.
vale-run
Run Vale (a prose/style linter) against an already-configured project and interpret its results.
What it does
This skill covers invoking the vale CLI against files or directories, choosing an output format (human-readable CLI, line, or machine-parseable JSON), filtering by severity via --minAlertLevel, and handling exit codes in scripts and CI. It also covers resolving common runtime issues: false positives, format-specific inline suppression, and CI failures caused solely by Vale's non-zero exit code. It assumes the project already has a working .vale.ini and installed styles — setting those up is the sibling vale-config skill's job.
Usage
/vale-run
Describe what you want to lint and how (human-readable output, CI/JSON output, filtered by severity). The skill will pick the right flags and, if results include false positives, walk through the narrowest applicable fix.
Files
| File | Purpose |
|---|---|
SKILL.md |
Core invocation, key flags, output format guidance, false-positive triage order |
references/troubleshooting.md |
Load when a rule appears not to apply, when writing inline suppression or spelling-ignore syntax, or when wiring Vale into pre-commit: resolved-config diagnostic (vale ls-config), format-specific suppression markup, rule-specific disabling, spelling ignore lists, pre-commit integration, CI edge cases |
references/sources.md |
Research provenance |