Keyword and pattern screen of a communication before principal review
One command in the Compliance pack, available in the CLI, as an MCP tool and as a JavaScript import: compliance scan.
What it needs, and why
Every input is checked before anything is calculated. text is required; the rest refine the answer.
| Input | Required | The question it asks | Why it matters |
|---|---|---|---|
text | yes | What is the full text of the communication? | The screen runs over the wording as it would be sent. |
Requests it answers
- “is this email compliant”
- “can we send this to clients”
- “check this marketing copy”
An agent with this pack loaded picks the command from phrasing like that, asks for whatever input is missing, and reports the figures with the method that produced them.
Run it
node bin/wealth-skills.js compliance scan --text "We offer a guaranteed 15% return with past performance."Limits it inherits from wealth-compliance
- The screen is pattern matching. It does not understand negation, judge whether a communication is fair and balanced, or review performance presentations.
- Passing the screen is not approval. Retail communications still need review by a registered principal.
The full pack, its other 3 commands and what it deliberately leaves alone are on the Compliance page.