// Enforce Vale prose checks on any user-facing text the agent creates or edits — comments, documentation, status messages, release notes, READMEs, or any explanatory content that users will read. Always use this skill when producing or changing prose, even when Vale is not explicitly requested.
Autonomously optimize any Claude Code skill by running it repeatedly, scoring outputs against binary evals, mutating the prompt, and keeping improvements. Based on Karpathy's autoresearch methodology. Use when: optimize this skill, improve this skill, run autoresearch on, make this skill better, self-improve skill, benchmark skill, eval my skill, run evals on. Outputs: an improved SKILL.md, a results log, and a changelog of every mutation tried.
Workflow for generating conventional commit messages following the Conventional Commits specification. MUST be invoked every time a commit is created. Guides construction of standardized commit messages with correct type, scope, description, body, and footer.
Go coding standards and conventions for this project. Apply when writing, reviewing, or refactoring any Go source file.
Markdown formatting rules for this project. Apply when writing or editing any .md or .mdx file, including documentation and website content.
PowerShell cmdlet conventions for this project. Apply when writing or reviewing any .ps1 or module file.
| name | vale-user-facing-text |
| description | Enforce Vale prose checks on any user-facing text the agent creates or edits — comments, documentation, status messages, release notes, READMEs, or any explanatory content that users will read. Always use this skill when producing or changing prose, even when Vale is not explicitly requested. |
This skill ships its own Vale configuration as a bundled artifact so it works
consistently regardless of whether the project has its own .vale.ini.
The embedded config lives at config/.vale.ini inside this skill's directory.
It declares the style packages and targets all Markdown files. Vale downloads
the style packages into config/.styles/ next to it, keeping everything
self-contained.
Always pass --config <SKILL_DIR>/config/.vale.ini to every Vale invocation.
Never rely on the project's own .vale.ini or omit the flag.
<SKILL_DIR><SKILL_DIR> is the directory that contains this SKILL.md file. Determine
it at runtime from the path the skill was loaded from. Examples:
skills/vale-user-facing-textapm_modules/<vendor>/agentic/skills/vale-user-facing-textApply this skill whenever creating or editing user-facing text, including:
.md, .mdx)Before running Vale, check whether config/.styles/ exists under <SKILL_DIR>.
If that folder is missing, run sync first. Do not run validation commands until
sync has completed successfully.
When config/.styles/ does not exist:
vale sync --config <SKILL_DIR>/config/.vale.ini
After sync, the downloaded styles are stored in <SKILL_DIR>/config/.styles/.
For later runs, skip sync if that folder already exists.
.md and .mdx files edited or created in this change.go, .py, .ts, etc.) that contain comments or docstrings
with human-readable explanations rather than code identifiers<SKILL_DIR>/config/.styles/ is absent,
run vale sync --config <SKILL_DIR>/config/.vale.ini before proceeding.vale --config <SKILL_DIR>/config/.vale.ini <edited-file>
.md file and validate it.
Name the temp file _vale_tmp.md and place it next to the source file.
Delete it once validation is complete, never commit it.vale --config <SKILL_DIR>/config/.vale.ini _vale_tmp.md
config/.styles/