plagiarism-checker
Scans lyrics for phrases that may match existing songs using web search and LLM knowledge. Use before release to check for unintentional borrowing.
What this skill does
## 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
```
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.