Your 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
Check for custom explicit words list:
Loading Override
- Read
~/.bitwize-music/config.yaml → paths.overrides
- Check for
{overrides}/explicit-words.md
- If exists: parse and merge with base list
- If not exists: use base list only
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)
Merge Behavior
- Start with base explicit word list
- Add any words from "Additional Explicit Words" section
- Remove any words from "Not Explicit" section
- Merged list used for scanning
Example:
- Base list has:
fuck, shit, hell, damn
- Override adds:
slang-term
- Override removes:
hell, damn
- Final list:
fuck, shit, slang-term
Workflow
For Album Path
Find all track files:
Glob: [album-path]/tracks/*.md
For each track:
- Read the Lyrics section
- Scan for explicit words (case-insensitive)
- Note the track's Explicit flag setting
- Record any matches
Generate report
For Single Track
- Read the track file
- Scan Lyrics section for explicit words
- Check Explicit flag
- 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
- Load override first - Check for
{overrides}/explicit-words.md before scanning
- 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)
1---2name: explicit-checker3description: Scan lyrics for explicit content, verify explicit flags match actual content4---5
6## Your Task
7
8**Path to scan**: $ARGUMENTS
9
101. Scan all lyrics for explicit words
112. Report findings with word counts per track
123. Flag mismatches (explicit content but flag says No, or vice versa)
134. Provide summary suitable for distributor submission
14
15---
16
17# Explicit Content Checker
18
19You scan lyrics for explicit content to ensure proper flagging before release.
20
21---
22
23## Explicit Words (Require Explicit = Yes)
24
25These words and variations require the explicit flag:
26
27| Category | Words |
28|----------|-------|
29| **F-word** | fuck, fucking, fucked, fucker, motherfuck, motherfucker |
30| **S-word** | shit, shitting, shitty, bullshit |
31| **B-word** | bitch, bitches |
32| **C-words** | cunt, cock, cocks |
33| **D-word** | dick, dicks |
34| **P-word** | pussy, pussies |
35| **A-word** | asshole, assholes |
36| **Slurs** | whore, slut, n-word, f-word (slur) |
37| **Profanity** | goddamn, goddammit |
38
39---
40
41## Clean Words (No Explicit Flag Needed)
42
43These are acceptable without explicit flag:
44- damn, hell, crap, ass, bastard, piss
45
46Note: "damn" alone is clean, but "goddamn" is explicit.
47
48---
49
50## Override Support
51
52Check for custom explicit words list:
53
54### Loading Override
551. Read `~/.bitwize-music/config.yaml` → `paths.overrides`
562. Check for `{overrides}/explicit-words.md`
573. If exists: parse and merge with base list
584. If not exists: use base list only
59
60### Override File Format
61
62**`{overrides}/explicit-words.md`:**
63```markdown
64# Custom Explicit Words
65
66## Additional Explicit Words
67- slang-term
68- regional-profanity
69- artist-specific-explicit
70
71## Not Explicit (Override Base)
72- hell (context: historical/literary)
73- damn (context: emphasis)
74```
75
76### Merge Behavior
771. Start with base explicit word list
782. Add any words from "Additional Explicit Words" section
793. Remove any words from "Not Explicit" section
804. Merged list used for scanning
81
82**Example:**
83- Base list has: `fuck, shit, hell, damn`
84- Override adds: `slang-term`
85- Override removes: `hell, damn`
86- Final list: `fuck, shit, slang-term`
87
88---
89
90## Workflow
91
92### For Album Path
93
941. **Find all track files**:
95 ```
96 Glob: [album-path]/tracks/*.md
97 ```
98
992. **For each track**:
100 - Read the Lyrics section
101 - Scan for explicit words (case-insensitive)
102 - Note the track's Explicit flag setting
103 - Record any matches
104
1053. **Generate report**
106
107### For Single Track
108
1091. Read the track file
1102. Scan Lyrics section for explicit words
1113. Check Explicit flag
1124. Report findings
113
114---
115
116## Output Format
117
118```
119EXPLICIT CONTENT SCAN
120Album: [Album Name]
121Date: [Scan Date]
122
123TRACK RESULTS:
124━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
125
126Track 01: [Title]
127 Flag: No
128 Content: Clean
129 Status: ✓ OK
130
131Track 02: [Title]
132 Flag: Yes
133 Content: fuck (3), shit (2), bitch (1)
134 Status: ✓ OK (flag matches content)
135
136Track 03: [Title]
137 Flag: No
138 Content: fuck (1)
139 Status: ⚠️ MISMATCH - Contains explicit content but flag is No
140
141━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
142
143SUMMARY:
144 Total tracks: 10
145 Clean tracks: 7
146 Explicit tracks: 3
147 Mismatches: 1
148
149ALBUM EXPLICIT FLAG: Yes (any track explicit = album explicit)
150
151ACTION REQUIRED:
152 - Track 03: Set Explicit flag to Yes
153```
154
155---
156
157## Mismatch Detection
158
159### Flag Says No, Content Is Explicit
160```
161⚠️ MISMATCH: Track contains explicit content but Explicit flag is "No"
162ACTION: Set Explicit: Yes in track file
163```
164
165### Flag Says Yes, Content Is Clean
166```
167ℹ️ NOTE: Track flagged explicit but no explicit words found
168This is OK - artist may want explicit flag for themes/context
169No action required (conservative flagging is fine)
170```
171
172---
173
174## Distributor Requirements
175
176Most distributors (DistroKid, TuneCore, CD Baby) require:
177- **Track-level flags**: Each track marked explicit or clean
178- **Album-level flag**: If ANY track is explicit, album is explicit
179- **Consistent metadata**: Flag must match actual content
180
181**Consequences of wrong flags**:
182- Explicit content marked clean → Potential removal from platforms, account issues
183- Clean content marked explicit → Reduced reach (filtered from some playlists) but no penalty
184
185**Rule**: When in doubt, mark explicit. Under-flagging is worse than over-flagging.
186
187---
188
189## Integration
190
191This skill is called during:
1921. **Ready to Generate Checkpoint** - Before Suno generation
1932. **Album Completion Checklist** - Before release
1943. **Manual review** - Anytime with `/explicit-checker [path]`
195
196---
197
198## Example Invocations
199
200```
201/explicit-checker artists/[artist]/albums/rock/dark-tide/
202/explicit-checker artists/[artist]/albums/rock/dark-tide/tracks/01-the-tank.md
203```
204
205---
206
207## Remember
208
209- **Load override first** - Check for `{overrides}/explicit-words.md` before scanning
210- Case-insensitive matching (Fuck = fuck = FUCK)
211- Check variations (fucking, fucked, fucker)
212- Phonetic spellings count (fuk, sh1t if intentional)
213- Context matters less than presence - if the word is there, flag it
214- Album is explicit if ANY track is explicit
215- **Override additions** - Add artist/genre-specific explicit words
216- **Override removals** - Remove words for specific contexts (historical, literary)