packages/openclaw/skills/profanity_check/SKILL.md
Check messages for profanity and inappropriate content in 24 languages
npx skillsauth add glincker/glin-profanity profanity_checkInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
When the user asks you to check a message for profanity, or when you need to
verify content before sending, use the check_profanity tool.
check_profanity tool with the text to checkcontainsProfanity is true, warn the userIf profanity is detected: "I found some inappropriate language in your message. The words [words] were flagged. Would you like me to suggest alternatives?"
If clean: "Your message looks good! No inappropriate content detected."
This skill supports 24 languages. Specify languages parameter if checking non-English content:
languages: ["english", "spanish"] for multi-languagearabic, chinese, czech, danish, dutch, english, esperanto, finnish, french, german, hindi, hungarian, italian, japanese, korean, norwegian, persian, polish, portuguese, russian, spanish, swedish, thai, turkish
Powered by glin-profanity
Compatible with OpenClaw, Moltbot (legacy), and Clawdbot (legacy).
content-media
Proactive content moderation guard for all incoming messages
testing
Automatically censor profanity in messages by replacing with asterisks
testing
Create, edit, improve, or audit AgentSkills. Use when creating a new skill from scratch or when asked to improve, review, audit, tidy up, or clean up an existing skill or SKILL.md file. Also use when editing or restructuring a skill directory (moving files to references/ or scripts/, removing stale content, validating against the AgentSkills spec). Triggers on phrases like "create a skill", "author a skill", "tidy up a skill", "improve this skill", "review the skill", "clean up the skill", "audit the skill".
testing
Host security hardening and risk-tolerance configuration for OpenClaw deployments. Use when a user asks for security audits, firewall/SSH/update hardening, risk posture, exposure review, OpenClaw cron scheduling for periodic checks, or version status checks on a machine running OpenClaw (laptop, workstation, Pi, VPS).