Description 657 -> 244 chars, body 504 -> 342 words, Gotchas 50% -> 24%. The 50% was the worst ratio in the corpus and a real inverted body, not the denominator artefact the ratio usually flags: half the body was a Gotchas section doing duty as reference material. A clean-context audit caught the split leaving a false statement behind. Gotcha 1's kernel lost the qualifier that only package styles need fetching, so it asserted that any style vale sync has not fetched fails -- contradicting the same file twice, since the built-in Vale style and any committed custom style are never fetched. An agent adding a custom style would have added a spurious Packages entry and broken vale sync outright. The qualifier is restored in the body rather than behind a fourth reference pointer. Also corrects the moved fixture's framing, which tabulated a control row under a heading claiming it came from a multi-line fixture. Refs #99
vale-config
Install and configure Vale, the prose/style linter — .vale.ini, StylesPath, built-in/third-party/custom styles, and activation via BasedOnStyles.
What it does
Covers the setup side of Vale: getting a project from no config to a working .vale.ini where vale sync runs clean and every declared style is actually activated for the right files. Does not run Vale or interpret its output — see vale-run for that.
Usage
/vale-config
Describe what you want configured: initial setup, adding a third-party style package, or a custom rule. The skill covers install, StylesPath layout, .vale.ini structure, and BasedOnStyles activation.
Files
| File | Purpose |
|---|---|
SKILL.md |
Skill instructions for agents |
references/configuration-reference.md |
Full .vale.ini fields, rule-header fields, and frontmatter-scope behaviour |
references/sources.md |
Research sources backing the Vale configuration guidance |