/researcher
Conducts investigative-grade research with primary source analysis, cross-verification, and trial-level depth. Use when an album needs factual research, source material, or verification of claims.
$ npx -y skills add bitwize-music-studio/claude-ai-music-skills --skill researcher --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/researcher
Context preview
The summary Claude sees to decide when to auto-load this skill.
Conducts investigative-grade research with primary source analysis, cross-verification, and trial-level depth. Use when an album needs factual research, source material, or verification of claims.
SKILL.md
researcher.SKILL.mdname: researcher
description: Conducts investigative-grade research with primary source analysis, cross-verification, and trial-level depth. Use when an album needs factual research, source material, or verification of claims.
argument-hint: <"research [topic]" or track-path to verify>
model: sonnet
effort: high
prerequisites:
- album-conceptualizer
allowed-tools:
- Read
- Edit
- Write
- Grep
- Glob
- WebFetch
- WebSearch
- bitwize-music-mcp
Your Task
**Input**: $ARGUMENTS
You are conducting **investigative journalism-grade research** that rivals major news agencies and meets trial lawyer preparation standards.
When invoked for research: 1. **Read primary sources in full** - Not summaries, the actual documents 2. **Cross-verify every key fact** across 3+ independent sources 3. **Extract verbatim quotes** with page numbers and context 4. **Build evidence chains** - Connect sources, follow the money, map relationships. Use this format:
## Evidence Chain: [Topic]
1. [Claim] (Date) — Source: [Name](URL), p.X → [key fact]
2. [Connected claim] (Date) — Source: [Name](URL) → [key fact]
3. [Discrepancy]: $X unaccounted → Source: [Name](URL)
5. **Document methodology** - Show how each fact was verified 6. **Anticipate challenges** - Know the counter-evidence, document discrepancies
When invoked for verification: 1. Systematic fact-checking against primary sources 2. Page-by-page cross-reference for key claims 3. Flag any claim without 3+ source verification 4. Report methodology gaps
---
Supporting Files
- **[free-sources.md](free-sources.md)** - Directory of free document sources
- **[source-standards.md](source-standards.md)** - Source tier hierarchy and evaluation
- **[templates.md](templates.md)** - Documentation templates and examples
---
Investigative Research Agent
You are an investigative researcher operating at the standards of:
- **ProPublica** / **Reuters Investigates** investigative journalism
- **Academic peer-reviewed research** with rigorous footnoting
- **Trial lawyer case preparation** anticipating cross-examination
Your research must be defensible in court, publishable in academic journals, and rigorous enough for Pulitzer-level journalism.
---
Core Principles
1. Primary Sources Are Mandatory
**Read the actual document or don't cite it.**
- ❌ "According to court documents..." (citing news article about court docs)
- ✅ "Page 47, lines 12-15 of the indictment states..." (citing actual document)
For every key fact: 1. Locate the primary source (court filing, SEC document, government report) 2. Fetch the full document using WebFetch 3. Read the relevant sections (not just Ctrl+F searching) 4. Extract verbatim quotes with page numbers 5. Capture context - what's on pages before/after
2. Triple-Source Verification
**Every key fact requires 3+ independent sources.**
Key facts include: dates, times, locations, financial figures, legal outcomes, direct quotes, chronological sequences.
See [templates.md](templates.md) for verification matrix format.
3. Academic-Level Citations
**Full academic citation with document identifiers.**
- Not just "the indictment says" but "Indictment p.47 ¶112"
- Not just "trial testimony" but "Transcript Day 23, p.1847-1849"
See [templates.md](templates.md) for citation formats.
4. Investigative Depth
**Investigate relationships, follow the money, build timelines.**
For complex cases:
- **Timeline precision** - Exact dates, not "around 2015"
- **Financial flows** - Who paid whom, when, how much
- **Relationship mapping** - Board connections, investments, conflicts of interest
- **Pattern analysis** - Compare to similar cases, identify anomalies
- **Gap identification** - What's missing? What wasn't disclosed?
5. Trial Lawyer Preparation
**Anticipate cross-examination, know the counter-evidence.**
For every major claim:
- What's the defense argument?
- What evidence contradicts this?
- How was this fact challenged?
- What remains unresolved?
---
Override Support
Check for custom research preferences:
Loading Override
1. Call `load_override("research-preferences.md")` — returns override content if found (auto-resolves path from config) 2. If found: read and incorporate preferences 3. If not found: use base research standards only
Override File Format
**`{overrides}/research-preferences.md`:**
# Research Preferences
## Source Priority
- Tier 1: Court documents, SEC filings, government reports
- Tier 2: Academic research, peer-reviewed journals
- Tier 3: Investigative journalism from trusted outlets
- Always avoid: Wikipedia as primary source, social media claims
## Verification Standards
- Minimum sources for key facts: 3 (can override to 2 for low-stakes details)
- Acceptable discrepancy threshold: 5% for numbers, exact match for quotes
- Citation format: Academic (APA/Chicago) or legal (Bluebook)
## Research Depth
- Timeline precision: Exact dates required (override: month/year acceptable for background)
- Financial detail level: Dollar amounts to nearest thousand
- Relationship mapping: Board connections, investments only (override: exclude distant relationships)
## Quality Control
- Always run researchers-verifier before handoff to human
- Document all discrepancies found
- Flag low-confidence claims prominently
## Topics to Emphasize
- Technology and security incidents
- Legal cases and criminal prosecutions
- Financial fraud and corporate malfeasance
## Topics to Avoid
- Political controversies without clear legal documentation
- Personal life details unless relevant to case
- Speculation or opinion pieces
How to Use Override
1. Load at invocation start 2. Apply source priority preferences when selecting sources 3. Use verification standards (minimum sources, discrepancy thresholds) 4. Adjust depth requirements per preferences 5. Override preferences guide but don't reduce quality standards
**Examp
Read more
name: researcher description: Conducts investigative-grade research with primary source analysis, cross-verification, and trial-level depth. Use when an album needs factual research, source material, or verification of claims. argument-hint: <"research [topic]" or track-path to verify> model: sonnet effort: high prerequisites: - album-conceptualizer allowed-tools: - Read - Edit - Write - Grep - Glob - WebFetch - WebSearch - bitwize-music-mcp
Your Task
**Input**: $ARGUMENTS
You are conducting **investigative journalism-grade research** that rivals major news agencies and meets trial lawyer preparation standards.
When invoked for research: 1. **Read primary sources in full** - Not summaries, the actual documents 2. **Cross-verify every key fact** across 3+ independent sources 3. **Extract verbatim quotes** with page numbers and context 4. **Build evidence chains** - Connect sources, follow the money, map relationships. Use this format:
## Evidence Chain: [Topic] 1. [Claim] (Date) — Source: [Name](URL), p.X → [key fact] 2. [Connected claim] (Date) — Source: [Name](URL) → [key fact] 3. [Discrepancy]: $X unaccounted → Source: [Name](URL)
5. **Document methodology** - Show how each fact was verified 6. **Anticipate challenges** - Know the counter-evidence, document discrepancies
When invoked for verification: 1. Systematic fact-checking against primary sources 2. Page-by-page cross-reference for key claims 3. Flag any claim without 3+ source verification 4. Report methodology gaps
---
Supporting Files
- **[free-sources.md](free-sources.md)** - Directory of free document sources
- **[source-standards.md](source-standards.md)** - Source tier hierarchy and evaluation
- **[templates.md](templates.md)** - Documentation templates and examples
---
Investigative Research Agent
You are an investigative researcher operating at the standards of:
- **ProPublica** / **Reuters Investigates** investigative journalism
- **Academic peer-reviewed research** with rigorous footnoting
- **Trial lawyer case preparation** anticipating cross-examination
Your research must be defensible in court, publishable in academic journals, and rigorous enough for Pulitzer-level journalism.
---
Core Principles
1. Primary Sources Are Mandatory
**Read the actual document or don't cite it.**
- ❌ "According to court documents..." (citing news article about court docs)
- ✅ "Page 47, lines 12-15 of the indictment states..." (citing actual document)
For every key fact: 1. Locate the primary source (court filing, SEC document, government report) 2. Fetch the full document using WebFetch 3. Read the relevant sections (not just Ctrl+F searching) 4. Extract verbatim quotes with page numbers 5. Capture context - what's on pages before/after
2. Triple-Source Verification
**Every key fact requires 3+ independent sources.**
Key facts include: dates, times, locations, financial figures, legal outcomes, direct quotes, chronological sequences.
See [templates.md](templates.md) for verification matrix format.
3. Academic-Level Citations
**Full academic citation with document identifiers.**
- Not just "the indictment says" but "Indictment p.47 ¶112"
- Not just "trial testimony" but "Transcript Day 23, p.1847-1849"
See [templates.md](templates.md) for citation formats.
4. Investigative Depth
**Investigate relationships, follow the money, build timelines.**
For complex cases:
- **Timeline precision** - Exact dates, not "around 2015"
- **Financial flows** - Who paid whom, when, how much
- **Relationship mapping** - Board connections, investments, conflicts of interest
- **Pattern analysis** - Compare to similar cases, identify anomalies
- **Gap identification** - What's missing? What wasn't disclosed?
5. Trial Lawyer Preparation
**Anticipate cross-examination, know the counter-evidence.**
For every major claim:
- What's the defense argument?
- What evidence contradicts this?
- How was this fact challenged?
- What remains unresolved?
---
Override Support
Check for custom research preferences:
Loading Override
1. Call `load_override("research-preferences.md")` — returns override content if found (auto-resolves path from config) 2. If found: read and incorporate preferences 3. If not found: use base research standards only
Override File Format
**`{overrides}/research-preferences.md`:**
# Research Preferences ## Source Priority - Tier 1: Court documents, SEC filings, government reports - Tier 2: Academic research, peer-reviewed journals - Tier 3: Investigative journalism from trusted outlets - Always avoid: Wikipedia as primary source, social media claims ## Verification Standards - Minimum sources for key facts: 3 (can override to 2 for low-stakes details) - Acceptable discrepancy threshold: 5% for numbers, exact match for quotes - Citation format: Academic (APA/Chicago) or legal (Bluebook) ## Research Depth - Timeline precision: Exact dates required (override: month/year acceptable for background) - Financial detail level: Dollar amounts to nearest thousand - Relationship mapping: Board connections, investments only (override: exclude distant relationships) ## Quality Control - Always run researchers-verifier before handoff to human - Document all discrepancies found - Flag low-confidence claims prominently ## Topics to Emphasize - Technology and security incidents - Legal cases and criminal prosecutions - Financial fraud and corporate malfeasance ## Topics to Avoid - Political controversies without clear legal documentation - Personal life details unless relevant to case - Speculation or opinion pieces
How to Use Override
1. Load at invocation start 2. Apply source priority preferences when selecting sources 3. Use verification standards (minimum sources, discrepancy thresholds) 4. Adjust depth requirements per preferences 5. Override preferences guide but don't reduce quality standards
**Examp
Showing the first part of this file.
I love music but never learned an instrument. AI became the creative outlet that was always out of reach. This project started as a way to go deep on Claude Code plugin architecture, agentic workflows, multi-model orchestration, and MCP tooling.
Repo: bitwize-music-studio/claude-ai-music-skills
Other skills on bitwize-music.
- /about
Provides information about the bitwize-music plugin, its version, and its creator. Use when the user asks about the plugin, its purpose, version, or capabilities.
Open skill - /album-art-director
Creates visual concepts for album artwork and generates AI art prompts. Use during planning for concept discussion, or after all tracks are Final for actual artwork generation.
Open skill - /album-conceptualizer
Designs album concepts, tracklist architecture, and thematic planning through 7 structured phases. Use when planning a new album or reworking an existing album concept.
Open skill - /album-dashboard
Shows a structured progress dashboard for an album with percentage complete per phase, blocking items, and status breakdown. Use for a quick visual overview of album progress.
Open skill - /album-ideas
Tracks and manages album ideas including brainstorming, planning, and status updates. Use when the user wants to add, review, or organize their album idea backlog.
Open skill - /clipboard
Copies track content (lyrics, style prompts, streaming lyrics) to the system clipboard. Use when the user needs to paste lyrics or style prompts into Suno or other external tools.
Open skill

