plagiarism-checker — Claude Code skill: scan lyrics for matches
The skill scans song lyrics for phrases that may echo existing songs and returns a risk report before release.
npx skills add bitwize-music-studio/claude-ai-music-skills --skill plagiarism-checker -a claude-codeWhat plagiarism-checker does
The skill pulls the lyrics for a track, extracts distinctive 4-7 word phrases and runs them through web search. At the same time the model reads every line itself and flags anything that resembles a known song. The result is a report with findings sorted into HIGH, MEDIUM and LOW risk plus a verdict: CLEAR, NEEDS REVIEW or REWRITE REQUIRED.
Six steps sit behind that: get the lyrics, extract phrases with the extract_distinctive_phrases MCP tool, search for matches, compare suspicious hits, run a knowledge check, build the report. It relies on the bitwize-music-mcp server and the Read, Glob, Grep, WebSearch, WebFetch tools. Invoke it as /plagiarism-checker <album-name> [track-slug].
Web search access is required. If WebSearch is unavailable or rate-limited, the skill falls back to the model knowledge check alone and notes that in the report. The author is blunt about scope: this is not a legal tool and does not determine copyright infringement, it only catches borrowing early enough to rewrite a line. It is also too slow to sit in front of generation, so run it before release, not before Suno.
What it helps with
- catch lines that accidentally match an existing song
- get a risk-rated report before release
- filter out common cliches so searches stay useful
- check a whole album instead of one track
- decide which line to rewrite first
Example prompts for the agent
- /plagiarism-checker dark-tide
- /plagiarism-checker dark-tide 03-the-wire
- scan this track's lyrics for matches against known songs
How to install plagiarism-checker
1Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill plagiarism-checker -a claude-code2Manually: put the files in place
~/.claude/skills/plagiarism-checker/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/plagiarism-checker/
1Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill plagiarism-checker -a codex2Manually: put the files in place
.agents/skills/plagiarism-checker/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill plagiarism-checker -a cursor2Manually: put the files in place
.cursor/skills/plagiarism-checker/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install bitwize-music-studio/claude-ai-music-skills plagiarism-checker2Manually: put the files in place
.github/skills/plagiarism-checker/SKILL.md1Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill plagiarism-checker -a gemini-cli2Platform CLI
gemini skills install https://github.com/bitwize-music-studio/claude-ai-music-skills --path skills/plagiarism-checkerManually: put the files in place
.devin/skills/plagiarism-checker/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill plagiarism-checker -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about plagiarism-checker
How do I install plagiarism-checker in Claude?
Run npx skills add bitwize-music-studio/claude-ai-music-skills --skill plagiarism-checker -a claude-code. The skill lands in ~/.claude/skills/plagiarism-checker/SKILL.md.
What does plagiarism-checker do?
It scans lyrics, searches for distinctive phrases through web search and model knowledge, and returns a report with HIGH, MEDIUM and LOW risk findings. The point is spotting accidental borrowing before release.
Does it check for copyright infringement?
No. It flags likely borrowing, not infringement. Only a lawyer can determine infringement.
Source text
SKILL.md · CC0-1.0
---
name: plagiarism-checker
description: Scans lyrics for phrases that may match existing songs using web search and LLM knowledge. Use before release to check for unintentional borrowing.
argument-hint: <album-name> [track-slug]
model: sonnet
effort: high
allowed-tools:
- Read
- Glob
- Grep
- WebSearch
- WebFetch
- bitwize-music-mcp
---
## Your Task
**Target**: $ARGUMENTS
1. Get lyrics for the specified track(s)
2. Extract distinctive phrases using MCP tool
3. Web search top phrases for matches against known songs
4. Use LLM knowledge to independently flag similarities
5. Generate structured risk report
---
# Plagiarism Checker
You scan lyrics for phrases that may unintentionally echo existing songs. This is a quality check, not a legal tool — it catches borrowing early so the writer can revise before release.
---
## Workflow
### Step 1: Get Lyrics
- Use `extract_section(album_slug, track_slug, "streaming")` to get streaming lyrics (preferred — no phonetic spellings that confuse web searches)
- If streaming lyrics empty, fall back to `extract_section(album_slug, track_slug, "lyrics")` for Suno lyrics
- If raw text was provided instead of album/track reference, use that directly
### Step 2: Extract Distinctive Phrases
Call `extract_distinctive_phrases(text, max_phrases=15, include_raw_lines=False)` MCP tool. This returns:
- Distinctive 4-7 word n-grams ranked by section priority (top 15)
- Pre-formatted search suggestions with quoted phrases + "lyrics"
- Common cliches already filtered out
### Step 3: Web Search
- Search the top 10-15 `search_suggestions` returned by the tool using WebSearch
- For short lyrics (<100 words), limit to 5-8 searches
- Look for results that reference specific songs by title/artist
- Skip results that are:
- Lyrics aggregator sites listing hundreds of matches (too generic)
- Dictionary/reference pages
- The user's own published work
### Step 4: Deep Compare
For any search result that names a specific song:
1. WebFetch the lyrics page
2. Compare the matching section against the user's lyrics
3. Check if the match is:
- Exact consecutive words (5+) — HIGH risk
- Partial overlap (4 words) — MEDIUM risk
- Thematic similarity only — LOW risk
### Step 5: LLM Knowledge Check
Independently scan ALL lines of the lyrics (not just extracted phrases) using your training knowledge:
- Flag any line that closely resembles a well-known song lyric
- Include the suspected source song and artist
- Note whether the similarity is in words, melody hook phrasing, or concept
### Step 6: Generate Report
---
## Risk Levels
| Level | Criteria | Action |
|-------|----------|--------|
| **HIGH** | 5+ consecutive matching words from a known song, especially chorus/hook | Rewrite the line immediately |
| **MEDIUM** | 4-word match from known song, or structural similarity flagged by LLM | Review and consider rewording |
| **LOW** | Common phrasing overlap, likely coincidence | Note for awareness, no action needed |
---
## Output Format
```
PLAGIARISM CHECK REPORT
Album: [Album Name]
Track: [Track Title]
Date: [Scan Date]
PHRASES SEARCHED: [N]
WEB MATCHES FOUND: [N]
LLM FLAGS: [N]
FINDINGS:
------------------------------------------------------------------------
[HIGH] Line 12 (Chorus): "burning shadows fall tonight across the wire"
Match: "Shadows Fall Tonight" by [Artist] — 5 consecutive words match chorus
Source: [URL]
Recommendation: Rewrite this line to avoid direct overlap
[MEDIUM] Line 24 (Verse 2): "walking through the ruins of the empire"
Similarity: Resembles "Empire" by [Artist] — similar phrasing in bridge
Source: LLM knowledge
Recommendation: Consider rewording if concerned
[LOW] Line 8 (Verse 1): "the city sleeps beneath the stars"
Note: Generic night imagery, appears in many songs
Recommendation: No action needed
------------------------------------------------------------------------
SUMMARY:
HIGH risk findings: 1
MEDIUM risk findings: 1
LOW risk findings: 1
VERDICT: NEEDS REVIEW
1 high-risk match requires attention before release.
COMMON PHRASES FILTERED: [N] (not searched — too generic to flag)
```
### Verdicts
| Verdict | Criteria |
|---------|----------|
| **CLEAR** | No HIGH or MEDIUM findings |
| **NEEDS REVIEW** | Any MEDIUM findings, or 1 HIGH finding |
| **REWRITE REQUIRED** | 2+ HIGH findings |
---
## Important Notes
- **This is not a legal tool.** It catches likely borrowing, not copyright infringement. Only a lawyer can determine infringement.
- **Streaming lyrics preferred.** Suno lyrics contain phonetic respellings (e.g., "Seh-KYOOR-ih-tee" for "security") that will produce garbage web search results.
- **Common cliches are pre-filtered.** The MCP tool removes ~75 ubiquitous phrases ("break my heart", "falling in love", etc.) before returning results. These are too common to flag.
- **Web searches may fail.** If WebSearch is unavailable or rate-limited, proceed with LLM knowledge check only and note the limitation in the report.
- **Not a pre-generation gate.** This check is too slow (web searches) and too unreliable (search availability) to block generation. Run it before release, not before Suno.
---
## Running for Full Album
When given an album slug without a specific track:
1. List all tracks via `list_tracks(album_slug)`
2. Run the check for each track with status "In Progress", "Generated", or "Final"
3. Skip tracks with status "Not Started" or "Sources Pending"
4. Aggregate findings into a single album-level report with per-track sections
---
## Example Invocations
```
/plagiarism-checker dark-tide
/plagiarism-checker dark-tide 03-the-wire
```
© bitwize-music-studio · CC0-1.0 · bitwize-music-studio/claude-ai-music-skills