Conducts investigative-grade research with primary source analysis, cross-verification, and trial-level depth.

CC0-1.0Auto-check passedResearch & Science

Install Researcher

skills CLI
$ npx skills add bitwize-music-studio/claude-ai-music-skills --skill researcher -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install bitwize-music-studio/claude-ai-music-skills researcher --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/researcher .claude/skills/researcher && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
researcher
GitHub stars
544
Token cost
~2.7k tokens
SKILL.md length
999 words
Files
4
Skills in repo
51
Repo updated
First seen
Licence
CC0-1.0

At a glance

Conducts investigative-grade research with primary source analysis, cross-verification, and trial-level depth.

  • Works in 9 steps: Primary Sources Are Mandatory → Triple-Source Verification → Academic-Level Citations → …
  • An album needs factual research
  • SKILL.md covers Your Task, Supporting Files, Core Principles and Override Support, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Researcher is an agent skill from bitwize-music-studio/claude-ai-music-skills. 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.

Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `free-sources.md`, `source-standards.md` and `templates.md`).

It sits in Research & Science. The repository describes itself as: Human + AI music production workflow for Suno - skills, templates, and tools. The licence is CC0-1.0.

When your agent uses it

  • An album needs factual research
  • Source material
  • Verification of claims

Example prompts

  • “Use the researcher skill to conduct investigative-grade research with primary source analysis, cross-verification, and trial-level depth”
  • “/researcher”

Requirements

  • Pre-approved tools (allowed-tools): Read, Edit, Write, Grep, Glob, WebFetch, WebSearch, bitwize-music-mcp

Workflow steps

9 steps, taken from the step headings in SKILL.md.

  1. Primary Sources Are Mandatory
  2. Triple-Source Verification
  3. Academic-Level Citations
  4. Investigative Depth
  5. Trial Lawyer Preparation
  6. Primary Source Acquisition
  7. Deep Reading & Cross-Verification
  8. Investigative Analysis
  9. Trial-Level Documentation

What it can do on your machine

Read from SKILL.md and the folder at commit 58f32c2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Edit
    • Write
    • Grep
    • Glob
    • WebFetch
    • WebSearch
    • bitwize-music-mcp

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Researcher loads about 2.7k tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 999 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~52
When it runs · the whole SKILL.md, loaded when a task matches
~2.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from bitwize-music-studio/claude-ai-music-skills at commit 58f32c2, republished under its CC0-1.0 licence (© bitwize-music-studio). 999 words, ~2,746 tokens.

Download SKILL.mdSave it as .claude/skills/researcher/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
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.
allowed-tools
Read, Edit, Write, Grep, Glob, WebFetch, WebSearch, bitwize-music-mcp
argument-hint
<"research [topic]" or track-path to verify>
model
sonnet
effort
high
prerequisites
album-conceptualizer

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


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 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 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:

markdown
# 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

Example:

  • User sets minimum sources to 2 for background details
  • User requires exact dates for all events
  • Result: Background context verified with 2 sources, timeline events require 3+ with exact dates

Research Process

Phase 1: Primary Source Acquisition

Do not proceed to Phase 2 until you have primary sources.

Use /document-hunter First

For court cases and legal research, invoke /document-hunter skill BEFORE manual searching:

/document-hunter "case name keywords"

This automates searching 10+ free sources and downloads all available documents.

Manual Search (If Needed)

If /document-hunter doesn't find everything, search manually. See free-sources.md for the complete directory of free sources including:

  • DocumentCloud
  • CourtListener / RECAP
  • Scribd
  • Justia
  • Government agency sites
  • News organization archives
Show full SKILL.md (409 more words)Show less
Phase 2: Deep Reading & Cross-Verification
  1. Read documents completely - Not just keyword search
  2. Extract all relevant facts with page numbers
  3. Build verification matrix for each key fact
  4. Flag discrepancies immediately
  5. Document confidence levels

See templates.md for verification matrix format.

Phase 3: Investigative Analysis

Go beyond fact-gathering:

  1. Timeline reconstruction - Detailed chronology with exact dates
  2. Financial analysis - Track money flows, calculate totals
  3. Relationship mapping - Who recruited whom, when
  4. Pattern identification - Compare to similar cases
  5. Gap analysis - What remains unanswered?
Phase 4: Trial-Level Documentation

Document as if preparing for cross-examination:

  1. Evidence chains - Connect sources to claims
  2. Counter-evidence - Document opposing arguments
  3. Unresolved questions - What's still unknown?

See templates.md for documentation formats.


Coordinating Specialist Researchers

For deep research, coordinate with specialized researchers:

SpecialistDomain
researchers-legalCourt documents, indictments, sentencing
researchers-govDOJ/FBI/SEC press releases
researchers-journalismInvestigative articles
researchers-techProject histories, changelogs
researchers-securityMalware analysis, CVEs
researchers-financialSEC filings, market data
researchers-historicalArchives, timelines
researchers-biographicalPersonal backgrounds
researchers-primary-sourceSubject's own words
researchers-verifierQuality control, fact-checking

These specialists have user-invocable: false - you coordinate them, users don't invoke directly.


Output Format

Determine Album Location (REQUIRED)

Before creating any files, you MUST:

  1. Find album via MCP:

    • Call find_album(name) — fuzzy match by name, slug, or partial
    • If found: use the album's path from the response
  2. Determine album from context:

    • Call list_albums(status_filter="In Progress") — check for albums in active states
    • If exactly 1 album in "Concept", "Research Complete", or "In Progress" → use it
    • If multiple match or none, ask: "Which album is this research for?"
  3. Resolve content path:

    • Call resolve_path("content", album_slug) — returns the album's content directory
    • Save RESEARCH.md and SOURCES.md to this path

CRITICAL: Never save to current working directory. Always save to the album's directory.

For Research Tasks

Create these files in the album directory:

  1. RESEARCH.md - Consolidated findings with verification status
  2. SOURCES.md - Full academic citations for all sources

See templates.md for file formats.

For Verification Tasks

Report format:

VERIFICATION REPORT
===================
Topic: [topic]
Date: [date]

VERIFIED FACTS (HIGH CONFIDENCE):
- [Fact 1] - [3+ sources, all align]
- [Fact 2] - [3+ sources, all align]

PARTIALLY VERIFIED (MEDIUM CONFIDENCE):
- [Fact 3] - [2 sources, minor discrepancy]

UNVERIFIED (LOW CONFIDENCE):
- [Fact 4] - [Single source only]

DISCREPANCIES FOUND:
- [Description of conflicting information]

METHODOLOGY GAPS:
- [What couldn't be verified and why]

Remember

  1. Load override first - Call load_override("research-preferences.md") at invocation
  2. Apply research standards - Use override verification standards and source priorities if available
  3. Primary sources or nothing - Don't cite news about documents, cite documents
  4. Triple-verify key facts - 3+ independent sources minimum (or override minimum)
  5. Page numbers always - "p.47 ¶112" not "the document says"
  6. Document discrepancies - Don't hide conflicting information
  7. Know the counter-argument - What would defense say?
  8. Use /document-hunter - Automate free source searching
  9. Coordinate specialists - Delegate deep dives to researcher variants

© bitwize-music-studio, CC0-1.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files in skills/researcher of bitwize-music-studio/claude-ai-music-skills.

  • SKILL.md
  • free-sources.md
  • source-standards.md
  • templates.md

Open the folder on GitHubat commit 58f32c2

Compare with similar skills

Researcher next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Researcher compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Researcher this skillbitwize-music-studio/claude-ai-music-skills544—~2.7kAutomated safety check: PassCC0-1.0
Hypothesis Generationspacering-net/codeg3.9k14 repos~3.6kAutomated safety check: NotesMIT
GitHub Deep Researchbytedance/deer-flow84k4 repos~1.3kAutomated safety check: PassMIT
Nature Paper CardYuan1z0825/nature-skills47k2 repos~2.1kAutomated safety check: PassApache-2.0
Content Research Writerweapp-tailwindcss/weapp-tailwindcss1.9k25 repos~3.5kAutomated safety check: PassMIT
Last30daysmvanhorn/last30days-skill64k—~7.9kAutomated safety check: NotesMIT

Similar skills

  • Hypothesis Generation

    spacering-net/codeg

    Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.

    3.9k GitHub starsUsed in 14 repos~3.6k tokens
    Research & ScienceAuto-check: notes
  • GitHub Deep Research

    bytedance/deer-flow

    Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.

    84k GitHub starsUsed in 4 repos~1.3k tokens
    Research & ScienceAuto-check passed
  • Nature Paper Card

    Yuan1z0825/nature-skills

    Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.

    47k GitHub starsUsed in 2 repos~2.1k tokens
    Research & ScienceAuto-check passed
  • Content Research Writer

    weapp-tailwindcss/weapp-tailwindcss

    Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.

    1.9k GitHub starsUsed in 25 repos~3.5k tokens
    Research & ScienceAuto-check passed
  • Last30days

    mvanhorn/last30days-skill

    Research what people actually say about any topic in the last 30 days.

    64k GitHub stars~7.9k tokensUpdated yesterday
    Research & ScienceAuto-check: notes
  • Peer Review

    spacering-net/codeg

    Structured manuscript/grant review with checklist-based evaluation.

    3.9k GitHub starsUsed in 17 repos~5.9k tokens
    Research & ScienceAuto-check: notes

More from bitwize-music-studio/claude-ai-music-skills

All 51 skills in this repo
  • Album Conceptualizer

    bitwize-music-studio/claude-ai-music-skills

    Designs album concepts, tracklist architecture, and thematic planning through 7 structured phases.

    544 GitHub stars~3.6k tokensUpdated 3 days ago
    Auto-check passed
  • Album Dashboard

    bitwize-music-studio/claude-ai-music-skills

    Shows a structured progress dashboard for an album with percentage complete per phase, blocking items, and status breakdown.

    544 GitHub stars~1.1k tokensUpdated 3 days ago
    Auto-check passed
  • Album Ideas

    bitwize-music-studio/claude-ai-music-skills

    Tracks and manages album ideas including brainstorming, planning, and status updates.

    544 GitHub stars~2.2k tokensUpdated 3 days ago
    Auto-check passed
  • Clipboard

    bitwize-music-studio/claude-ai-music-skills

    Copies track content (lyrics, style prompts, streaming lyrics) to the system clipboard.

    544 GitHub stars~1.4k tokensUpdated 3 days ago
    Auto-check: notes
  • Cloud Uploader

    bitwize-music-studio/claude-ai-music-skills

    Uploads promo videos and content to Cloudflare R2 or AWS S3.

    544 GitHub stars~2.1k tokensUpdated 3 days ago
    Auto-check: notes
  • Configure

    bitwize-music-studio/claude-ai-music-skills

    Sets up or edits the plugin configuration file interactively.

    544 GitHub stars~2.2k tokensUpdated 3 days ago
    Auto-check: notes

Questions about Researcher

What does Researcher do?

Conducts investigative-grade research with primary source analysis, cross-verification, and trial-level depth. Researcher is an agent skill from bitwize-music-studio/claude-ai-music-skills. Conducts investigative-grade research with primary source analysis, cross-verification, and trial-level depth.

When should I use Researcher?

Researcher fits situations like: an album needs factual research; source material; verification of claims.

How do I install Researcher in Claude Code?

Run `npx skills add bitwize-music-studio/claude-ai-music-skills --skill researcher -a claude-code`. Or copy the skill folder (skills/researcher in bitwize-music-studio/claude-ai-music-skills) into .claude/skills/researcher in your project. Claude Code loads it when a task matches its description.

How do I install Researcher in Codex?

Run `npx skills add bitwize-music-studio/claude-ai-music-skills --skill researcher -a codex`. Or copy the skill folder (skills/researcher in bitwize-music-studio/claude-ai-music-skills) into .agents/skills/researcher in your project. Codex loads it when a task matches its description.

Can I use Researcher in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bitwize-music-studio/claude-ai-music-skills --skill researcher -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/researcher, .gemini/skills/researcher, .github/skills/researcher and .opencode/skills/researcher in your project.

What does Researcher need to run?

SKILL.md names no scripts, command-line tools or credentials: Researcher is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Edit, Write, Grep, Glob, WebFetch, WebSearch, bitwize-music-mcp.

Does Researcher access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Researcher safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Researcher use?

Researcher is published under the CC0-1.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Researcher use?

About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Researcher?

Skills that share tags, products or a category with Researcher: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Researcher?

bitwize-music-studio (a GitHub organization) maintains it in bitwize-music-studio/claude-ai-music-skills, which has 544 GitHub stars. The repository holds 51 skills in this directory. The repository was last updated on October 7, 2026.

Source: bitwize-music-studio/claude-ai-music-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.