explicit-checker
npx machina-cli add skill bitwize-music-studio/claude-ai-music-skills/explicit-checker --openclawYour Task
Path to scan: $ARGUMENTS
- Scan all lyrics for explicit words
- Report findings with word counts per track
- Flag mismatches (explicit content but flag says No, or vice versa)
- Provide summary suitable for distributor submission
Explicit Content Checker
You scan lyrics for explicit content to ensure proper flagging before release.
Explicit Words (Require Explicit = Yes)
These words and variations require the explicit flag:
| Category | Words |
|---|---|
| F-word | fuck, fucking, fucked, fucker, motherfuck, motherfucker |
| S-word | shit, shitting, shitty, bullshit |
| B-word | bitch, bitches |
| C-words | cunt, cock, cocks |
| D-word | dick, dicks |
| P-word | pussy, pussies |
| A-word | asshole, assholes |
| Slurs | whore, slut, n-word, f-word (slur) |
| Profanity | goddamn, goddammit |
Clean Words (No Explicit Flag Needed)
These are acceptable without explicit flag:
- damn, hell, crap, ass, bastard, piss
Note: "damn" alone is clean, but "goddamn" is explicit.
Override Support
The MCP check_explicit_content tool automatically loads and merges user overrides from {overrides}/explicit-words.md. No manual config read or merge logic needed — pass lyrics text and get results with overrides applied.
Override File Format
{overrides}/explicit-words.md:
# Custom Explicit Words
## Additional Explicit Words
- slang-term
- regional-profanity
- artist-specific-explicit
## Not Explicit (Override Base)
- hell (context: historical/literary)
- damn (context: emphasis)
Workflow
For Album Path
- Call
list_tracks(album_slug)— get all tracks with metadata - For each track:
- Call
extract_section(album_slug, track_slug, "lyrics")— get lyrics text - Call
check_explicit_content(lyrics_text)— returns matches with line numbers (overrides auto-merged) - Get Explicit flag from track metadata
- Compare flag vs. content
- Call
- Generate report
For Single Track
- Call
extract_section(album_slug, track_slug, "lyrics")— get lyrics text - Call
check_explicit_content(lyrics_text)— scan for explicit words - Get Explicit flag from track metadata via
get_track(album_slug, track_slug) - Report findings
Output Format
EXPLICIT CONTENT SCAN
Album: [Album Name]
Date: [Scan Date]
TRACK RESULTS:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Track 01: [Title]
Flag: No
Content: Clean
Status: ✓ OK
Track 02: [Title]
Flag: Yes
Content: fuck (3), shit (2), bitch (1)
Status: ✓ OK (flag matches content)
Track 03: [Title]
Flag: No
Content: fuck (1)
Status: ⚠️ MISMATCH - Contains explicit content but flag is No
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
SUMMARY:
Total tracks: 10
Clean tracks: 7
Explicit tracks: 3
Mismatches: 1
ALBUM EXPLICIT FLAG: Yes (any track explicit = album explicit)
ACTION REQUIRED:
- Track 03: Set Explicit flag to Yes
Mismatch Detection
Flag Says No, Content Is Explicit
⚠️ MISMATCH: Track contains explicit content but Explicit flag is "No"
ACTION: Set Explicit: Yes in track file
Flag Says Yes, Content Is Clean
ℹ️ NOTE: Track flagged explicit but no explicit words found
This is OK - artist may want explicit flag for themes/context
No action required (conservative flagging is fine)
Distributor Requirements
Most distributors (DistroKid, TuneCore, CD Baby) require:
- Track-level flags: Each track marked explicit or clean
- Album-level flag: If ANY track is explicit, album is explicit
- Consistent metadata: Flag must match actual content
Consequences of wrong flags:
- Explicit content marked clean → Potential removal from platforms, account issues
- Clean content marked explicit → Reduced reach (filtered from some playlists) but no penalty
Rule: When in doubt, mark explicit. Under-flagging is worse than over-flagging.
Integration
This skill is called during:
- Ready to Generate Checkpoint - Before Suno generation
- Album Completion Checklist - Before release
- Manual review - Anytime with
/explicit-checker [path]
Example Invocations
/explicit-checker artists/[artist]/albums/rock/dark-tide/
/explicit-checker artists/[artist]/albums/rock/dark-tide/tracks/01-the-tank.md
Remember
- Case-insensitive matching (Fuck = fuck = FUCK)
- Check variations (fucking, fucked, fucker)
- Phonetic spellings count (fuk, sh1t if intentional)
- Context matters less than presence - if the word is there, flag it
- Album is explicit if ANY track is explicit
- Override additions - Add artist/genre-specific explicit words
- Override removals - Remove words for specific contexts (historical, literary)
Source
git clone https://github.com/bitwize-music-studio/claude-ai-music-skills/blob/main/skills/explicit-checker/SKILL.mdView on GitHub Overview
Explicit-checker scans track lyrics for explicit words and verifies that each track's Explicit flag matches the actual content. It helps ensure accurate content ratings before Suno generation or release and outputs per-track counts plus a distributor-ready summary.
How This Skill Works
The tool analyzes lyrics using explicit word lists (F-word, S-word, B-word, C-words, D-word, P-word, A-word, slurs, and profanity), merges user overrides from explicit-words.md, and compares each track's flag to detected content. It then outputs a structured report with per-track word counts, mismatch status, and a summary suitable for distribution.
When to Use It
- Before Suno generation or release to ensure accurate content ratings
- During album prep to verify track-by-track explicit flags
- When artist overrides or regional terms are needed via explicit-words.md
- For distributor submission audits requiring per-track and album flags
- When auditing a full album to compute the Album Explicit flag if any track is explicit
Quick Start
- Step 1: Step 1: Provide the path to scan as ARGUMENTS
- Step 2: Step 2: Run the explicit-checker workflow to extract lyrics and detect explicit words
- Step 3: Step 3: Review the per-track results and update track or album Explicit flags as needed, then submit
Best Practices
- Keep the overrides file at {overrides}/explicit-words.md up to date with new terms
- Run the checker on every track in an album and on individual tracks
- Enable line-number reporting for precise edits to lyrics
- Always compare per-track flags and the album-level flag (any explicit track makes the album explicit)
- Use the SUMMARY and ACTION REQUIRED sections to drive flag updates before release
Example Use Cases
- Track 02 contains explicit words (e.g., fuck, shit); flag Yes; OK
- Track 03 shows explicit words but flag No -> MISMATCH
- Override file adds regional terms; new explicit content detected and counted
- Single-track scan identifies no explicit words; flag No; content Clean
- Album flag updated to Yes because at least one track is explicit; summary reflects counts and mismatches