Back to Skills

explicit-checker

bitwize-music-studio
Updated 2 days ago
10 views
209
37
209
View on GitHub
Metageneral

About

This skill scans song lyrics for explicit content and verifies that explicit flags match the actual findings. It reports word counts per track and flags any mismatches for accurate content ratings. Use it before music generation or release to ensure proper distributor submissions.

Quick Install

Claude Code

Recommended
Primary
npx skills add bitwize-music-studio/claude-ai-music-skills -a claude-code
Plugin CommandAlternative
/plugin add https://github.com/bitwize-music-studio/claude-ai-music-skills
Git CloneAlternative
git clone https://github.com/bitwize-music-studio/claude-ai-music-skills.git ~/.claude/skills/explicit-checker

Copy and paste this command in Claude Code to install this skill

Documentation

Your Task

Path to scan: $ARGUMENTS

  1. Scan all lyrics for explicit words
  2. Report findings with word counts per track
  3. Flag mismatches (explicit content but flag says No, or vice versa)
  4. 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:

CategoryWords
F-wordfuck, fucking, fucked, fucker, motherfuck, motherfucker
S-wordshit, shitting, shitty, bullshit
B-wordbitch, bitches
C-wordscunt, cock, cocks
D-worddick, dicks
P-wordpussy, pussies
A-wordasshole, assholes
Slurswhore, slut, n-word, f-word (slur)
Profanitygoddamn, 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

  1. Call list_tracks(album_slug) — get all tracks with metadata
  2. 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
  3. Generate report

For Single Track

  1. Call extract_section(album_slug, track_slug, "lyrics") — get lyrics text
  2. Call check_explicit_content(lyrics_text) — scan for explicit words
  3. Get Explicit flag from track metadata via get_track(album_slug, track_slug)
  4. 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:

  1. Ready to Generate Checkpoint - Before Suno generation
  2. Album Completion Checklist - Before release
  3. 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)

GitHub Repository

bitwize-music-studio/claude-ai-music-skills
Path: skills/explicit-checker
0
ai-musicai-music-toolsaudio-masteringclaudeclaude-codeclaude-code-plugin

Related Skills

content-collections

Meta

This skill provides a production-tested setup for Content Collections, a TypeScript-first tool that transforms Markdown/MDX files into type-safe data collections with Zod validation. Use it when building blogs, documentation sites, or content-heavy Vite + React applications to ensure type safety and automatic content validation. It covers everything from Vite plugin configuration and MDX compilation to deployment optimization and schema validation.

View skill

polymarket

Meta

This skill enables developers to build applications with the Polymarket prediction markets platform, including API integration for trading and market data. It also provides real-time data streaming via WebSocket to monitor live trades and market activity. Use it for implementing trading strategies or creating tools that process live market updates.

View skill

creating-opencode-plugins

Meta

This skill helps developers create OpenCode plugins that hook into 25+ event types like commands, files, and LSP operations. It provides the plugin structure, event API specifications, and implementation patterns for JavaScript/TypeScript modules. Use it when you need to intercept, monitor, or extend the OpenCode AI assistant's lifecycle with custom event-driven logic.

View skill

sglang

Meta

SGLang is a high-performance LLM serving framework that specializes in fast, structured generation for JSON, regex, and agentic workflows using its RadixAttention prefix caching. It delivers significantly faster inference, especially for tasks with repeated prefixes, making it ideal for complex, structured outputs and multi-turn conversations. Choose SGLang over alternatives like vLLM when you need constrained decoding or are building applications with extensive prefix sharing.

View skill