
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.
- Installs
- 223
- 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 researcher- 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 researcher 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
Input: $ARGUMENTS
You are conducting investigative journalism-grade research that rivals major news agencies and meets trial lawyer preparation standards.
When invoked for research:
- Read primary sources in full - Not summaries, the actual documents
- Cross-verify every key fact across 3+ independent sources
- Extract verbatim quotes with page numbers and context
- 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) - Document methodology - Show how each fact was verified
- Anticipate challenges - Know the counter-evidence, document discrepancies
When invoked for verification:
- Systematic fact-checking against primary sources
- Page-by-page cross-reference for key claims
- Flag any claim without 3+ source verification
- Report methodology gaps
Supporting Files
- free-sources.md - Directory of free document sources
- source-standards.md - Source tier hierarchy and evaluation
- 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:
- Locate the primary source (court filing, SEC document, government report)
- Fetch the full document using WebFetch
- Read the relevant sections (not just Ctrl+F searching)
- Extract verbatim quotes with page numbers
- 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
- Call
load_override("research-preferences.md")— returns override content if found (auto-resolves path from config) - If found: read and incorporate preferences
- 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
- Load at invocation start
- Apply source priority preferences when selecting sources
- Use verification standards (minimum sources, discrepancy thresholds)
- Adjust depth requirements per preferences
- 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
Phase 2: Deep Reading & Cross-Verification
- Read documents completely - Not just keyword search
- Extract all relevant facts with page numbers
- Build verification matrix for each key fact
- Flag discrepancies immediately
- Document confidence levels
See templates.md for verification matrix format.
Phase 3: Investigative Analysis
Go beyond fact-gathering:
- Timeline reconstruction - Detailed chronology with exact dates
- Financial analysis - Track money flows, calculate totals
- Relationship mapping - Who recruited whom, when
- Pattern identification - Compare to similar cases
- Gap analysis - What remains unanswered?
Phase 4: Trial-Level Documentation
Document as if preparing for cross-examination:
- Evidence chains - Connect sources to claims
- Counter-evidence - Document opposing arguments
- Unresolved questions - What's still unknown?
See templates.md for documentation formats.
Coordinating Specialist Researchers
For deep research, coordinate with specialized researchers:
| Specialist | Domain |
|---|---|
researchers-legal | Court documents, indictments, sentencing |
researchers-gov | DOJ/FBI/SEC press releases |
researchers-journalism | Investigative articles |
researchers-tech | Project histories, changelogs |
researchers-security | Malware analysis, CVEs |
researchers-financial | SEC filings, market data |
researchers-historical | Archives, timelines |
researchers-biographical | Personal backgrounds |
researchers-primary-source | Subject's own words |
researchers-verifier | Quality 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:
-
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
- Call
-
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?"
- Call
-
Resolve content path:
- Call
resolve_path("content", album_slug)— returns the album's content directory - Save RESEARCH.md and SOURCES.md to this path
- Call
CRITICAL: Never save to current working directory. Always save to the album's directory.
For Research Tasks
Create these files in the album directory:
- RESEARCH.md - Consolidated findings with verification status
- 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
- Load override first - Call
load_override("research-preferences.md")at invocation - Apply research standards - Use override verification standards and source priorities if available
- Primary sources or nothing - Don't cite news about documents, cite documents
- Triple-verify key facts - 3+ independent sources minimum (or override minimum)
- Page numbers always - "p.47 ¶112" not "the document says"
- Document discrepancies - Don't hide conflicting information
- Know the counter-argument - What would defense say?
- Use /document-hunter - Automate free source searching
- Coordinate specialists - Delegate deep dives to researcher variants
FAQ
What does the researcher skill do?
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.
How do I install researcher?
Run npx skills add https://github.com/bitwize-music-studio/claude-ai-music-skills --skill researcher 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/researcher/ (personal) or .claude/skills/researcher/ (project).
Which AI agents can use researcher?
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 researcher 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 researcher?
It is published by bitwize-music-studio in bitwize-music-studio/claude-ai-music-skills. It has 223 recorded installs.
More from bitwize-music-studio/claude-ai-music-skills
lyric-writer
bitwize-music-studio/claude-ai-music-skills
Writes or reviews lyrics with professional prosody, rhyme craft, and quality checks. Use when writing new lyrics, revising existing lyrics, or when the user says 'let's work on a track.'
suno-engineer
bitwize-music-studio/claude-ai-music-skills
Constructs technical Suno style prompts for the current model family (v6, v6-wild, v6-mini), selects models and generation settings, and optimizes prompts. Use when creating or refining Suno prompts for track generation.
plagiarism-checker
bitwize-music-studio/claude-ai-music-skills
Scans lyrics for phrases that may match existing songs using web search and LLM knowledge. Use before release to check for unintentional borrowing.
mastering-engineer
bitwize-music-studio/claude-ai-music-skills
Guides audio mastering for streaming platforms including loudness optimization and tonal balance. Use when the user has approved tracks and wants to master audio files.
mix-engineer
bitwize-music-studio/claude-ai-music-skills
Polishes raw Suno audio by processing per-stem WAVs (vocals, backingvocals, drums, bass, guitar, keyboard, strings, brass, woodwinds, percussion, synth, other) with targeted cleanup, EQ, and compression, then remixing into a polished stereo WAV ready for mastering. Use after audio import and before mastering.
lyric-reviewer
bitwize-music-studio/claude-ai-music-skills
Reviews lyrics against a quality checklist before Suno generation. Use before generating tracks to catch rhyme, prosody, pronunciation, and structural issues.
Popular media & creative skills
hyperframes
heygen-com/hyperframes
Read first to make, edit, animate or render any video with HyperFrames (HTML rendered to video), including launch films, explainers, music videos, charts, maps, vertical clips, title cards, captions and overlays. Holds the render contract, the work loop and what each kind of video needs.
media-use
heygen-com/hyperframes
Get or make any media for a HyperFrames video - music, sound effects, images, icons, logos, voiceover, avatar and generated video, transcripts, cutouts, colour grades and looks - with HeyGen or free local tools, and mix placed audio. Also for footage that looks dark, flat or dull, or should be stylized or hidden.
hyperframes-registry
heygen-com/hyperframes
About 450 ready-made HyperFrames blocks and components installed as editable source - transitions, overlays, titles, kinetic type, captions, charts, map overlays, 3D, camera moves. Use it before hand-building any named visual (CRT scanlines, glitch, film grain, a chart); also for hyperframes add and catalog.
hyperframes-creative
heygen-com/hyperframes
Non-animation creative direction for HyperFrames videos. Use for design spec (frame.md / design.md) handling, palettes, typography, narration, beat planning, audio-reactive visuals, composition patterns, and brand / style decisions. For atomic motion patterns and scene blueprints, use hyperframes-animation.
ai-video-generation
101-skills/superpowers
Generate AI videos with Google Veo, Seedance 2.0, HappyHorse, Wan, Grok and 40+ models via inference.sh CLI. Models: Veo 3.1, Veo 3, Seedance 2.0, HappyHorse 1.0, Wan 2.5, Grok Imagine Video, OmniHuman, Fabric, HunyuanVideo. Capabilities: text-to-video, image-to-video, reference-to-video, video editing, lipsync, avatar animation, video upscaling, foley sound. Use for: social media videos, marketing content, explainer videos, product demos, AI avatars. Triggers: video generation, ai video, text to video, image to video, veo, animate image, video from image, ai animation, video generator, generate video, t2v, i2v, ai video maker, create video with ai, runway alternative, pika alternative, sora alternative, kling alternative, seedance, happyhorse
ai-image-generation
101-skills/superpowers
Generate AI images with GPT-Image-2, FLUX, Gemini, Grok, Seedream, Reve and 50+ models via inference.sh CLI. Models: GPT-Image-2, FLUX Dev LoRA, FLUX.2 Klein LoRA, Gemini 3 Pro Image, Grok Imagine, Seedream 4.5, Reve, ImagineArt. Capabilities: text-to-image, image-to-image, inpainting, LoRA, image editing, upscaling, text rendering. Use for: AI art, product mockups, concept art, social media graphics, marketing visuals, illustrations. Triggers: flux, image generation, ai image, text to image, stable diffusion, generate image, ai art, midjourney alternative, dall-e alternative, text2img, t2i, image generator, ai picture, create image with ai, generative ai, ai illustration, grok image, gemini image, gpt image, openai image, chatgpt image