Content ComplianceAvailable

Banned Word Checker

Pre-publish scan for banned wording. The script handles the orthographic, deterministic part: dictionary hits plus evasions such as full-width forms, inserted spaces or symbols, zero-width characters and line-break splitting; pinyin and homophone aliases listed in the word list are matched too. Genuinely subtle phrasing (metaphor, slang) is left to the Agent reading the copy. Custom company word lists can be mounted.

Installbanned-word-checker-skill

Capabilities

Orthographic evasion detection (full-width / spacing / symbols / zero-width / line breaks)
Custom company word lists, including pinyin and homophone aliases
Hit line numbers, matched text and context for human review
Subtle semantic variants delegated to the Agent

Specifications

Use cases
Banned wordsCompliance
Roles
OperationsMarketing
Runtime
No third-party deps
Offline
Fully offline
Data boundary
Data stays local
Package
banned-word-checker-skill

How to install

Skill packages follow the open Agent Skills standard (one directory plus a SKILL.md). No request or licence is needed. Pick whichever path matches your client, then just describe the task in chat to trigger it.

① Import the package

Recommended

Download the skill zip and load it from your client's "import / upload local skill package" entry. If SKILL.md sits at the top level of the archive, the package is well formed.

Download packageCurrent version v1.0.0

② Command line

For command-line clients that support the Agent Skills standard: one command syncs the skill into your local skills directory.

$npx skills add m9ai/m9ai-skills --skill banned-word-checker-skill

Pass -a to name the client (claude-code, codex); omit it and you will be asked which one to use.

③ Unzip manually

You can also unzip the archive straight into your client's skills directory - no installer to run. The zip is self-contained and can be distributed offline, which makes it easy to host on an internal file server for company-wide rollout.

WorkBuddySettings → Skills directory (as shown in the client)
Claude Code (user level)~/.claude/skills/
Claude Code (project level).claude/skills/

Other clients supporting the Agent Skills standard work the same way: drop the skill directory into their skills folder.

Need this inside your own systems?

Ready-made skills cover generic scenarios. Internal data sources, private models and compliance requirements call for a tailored build.

See custom services