plagiarism-checker

Q: How do I install plagiarism-checker?

Run npx skills add https://github.com/bitwize-music-studio/claude-ai-music-skills --skill plagiarism-checker in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/plagiarism-checker/ (personal) or .claude/skills/plagiarism-checker/ (project).

Q: Which AI agents can use plagiarism-checker?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Q: Is plagiarism-checker safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Q: Who maintains plagiarism-checker?

It is published by bitwize-music-studio in bitwize-music-studio/claude-ai-music-skills. It has 356 recorded installs.

by bitwize-music-studioMedia & Creative

Scans lyrics for phrases that may match existing songs using web search and LLM knowledge. Use before release to check for unintentional borrowing.

Installs: 356
Last 24h: —
Trending rank: —
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/bitwize-music-studio/claude-ai-music-skills --skill plagiarism-checker

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads plagiarism-checker automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Your Task

Target: $ARGUMENTS

Get lyrics for the specified track(s)
Extract distinctive phrases using MCP tool
Web search top phrases for matches against known songs
Use LLM knowledge to independently flag similarities
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:

WebFetch the lyrics page
Compare the matching section against the user's lyrics
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:

List all tracks via list_tracks(album_slug)
Run the check for each track with status "In Progress", "Generated", or "Final"
Skip tracks with status "Not Started" or "Sources Pending"
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

FAQ

What does the plagiarism-checker skill do?

Scans lyrics for phrases that may match existing songs using web search and LLM knowledge. Use before release to check for unintentional borrowing.

How do I install plagiarism-checker?

Run npx skills add https://github.com/bitwize-music-studio/claude-ai-music-skills --skill plagiarism-checker in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/plagiarism-checker/ (personal) or .claude/skills/plagiarism-checker/ (project).

Which AI agents can use plagiarism-checker?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is plagiarism-checker safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains plagiarism-checker?

It is published by bitwize-music-studio in bitwize-music-studio/claude-ai-music-skills. It has 356 recorded installs.