/vocabulary-pal
This is part of a series about the AI agent skills I designed, built, and maintained to cover the full lifecycle of end-user help documentation.
What it is
/vocabulary-pal audits a Google Doc, Markdown file, text file, or Word document against an organization's custom controlled vocabulary. It flags every non-preferred term and gives the preferred term, the style guide's reasoning, and a suggested rewrite.
How it works
The skill handles details a simple find-and-replace can't: case-sensitive terms, hyphenation, acronyms that must be spelled out on first use, plurals and possessives, exceptions for terms shown literally in the product UI, and look-alike terms that mean different things. When the context is ambiguous, it flags both readings instead of picking one silently.
Why I built it
Source materials I generated content from used all kinds of variations of terms, including their spelling and capitalization (for example, common internal use for web app was WebApp, which was not a product name). I wanted to easily catch and fix inconsistencies without manually reading through the text from start to finish or running inadequate manual searches and replaces. I created it as a separate skill so I can run it on any piece of content I write, not just content generated by an AI agent skill in my plugin.