Skip to content

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

researcher

Verified

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.

FileKindSize
SKILL.mdskill md10.7 KB
free-sources.mdmarkdown3.2 KB
source-standards.mdmarkdown2.8 KB
templates.mdmarkdown3.9 KB

templates.md

View on GitHub
# Research Templates & Examples

Reference templates for documentation, verification, and citations.

---

## Verification Matrix Format

```
FACT: [Statement being verified]
SOURCE 1: [Citation] - PRIMARY/SECONDARY
SOURCE 2: [Citation] - PRIMARY/SECONDARY
SOURCE 3: [Citation] - PRIMARY/SECONDARY
VERIFIED: ✅/⚠️/❌ [X sources, Y primary, alignment status]
```

**Example**:
```
FACT: USIA found liable for the Great Molasses Flood (1925)
SOURCE 1: Court verdict by Hugh Ogden (1925) - PRIMARY
SOURCE 2: Boston Globe coverage (Jan 16, 1919) - PRIMARY
SOURCE 3: Stephen Puleo "Dark Tide" (2003) - SECONDARY
SOURCE 4: Engineering investigation reports - PRIMARY
VERIFIED: ✅ 4 sources, 3 primary, dates align
```

---

## Citation Formats

### Court Documents
```
[Case Name]
[Court], [Jurisdiction]
[Document Type], Filed [Date]
Pages [X-Y]
Retrieved: [date]
Archive: [location]
```

### Historical Records
```
[Publication] - [Topic]
[Date Range]
[Description]
Retrieved: [date]
Archive: [location]
```

### Page-Level Citations
- Not just "the indictment says" but "Indictment p.47 ¶112"
- Not just "trial testimony" but "Transcript Day 23, p.1847-1849, Lines 12-28"

---

## RESEARCH.md Format

Every section must include:
1. **Fact Statement**
2. **Primary Source Citation** (full academic format)
3. **Verification Matrix** (3+ sources)
4. **Page Numbers** for key quotes
5. **Context** (what document section is about)
6. **Confidence Level** (High/Medium/Low)
7. **Discrepancies** (if any)
8. **Unresolved Questions**

### Example Entry

```markdown
## Track 01: The Tank - Fact Sheet

### FACT 1: Tank collapsed January 15, 1919 at approximately 12:40 PM

**Primary Source 1: Boston Globe**
- Source: Boston Globe, January 16, 1919 (front page)
- Direct quote: "Giant tank burst shortly after noon"
- Context: Contemporary newspaper account, day after disaster
- Confidence: HIGH (primary source)

**Primary Source 2: Court records**
- Dorr et al. v. USIA trial documents
- Multiple witness testimonies establish time
- Hugh Ogden's report references "midday"

**Primary Source 3: Stephen Puleo "Dark Tide"**
- Pages 1-5: "12:40 in the afternoon"
- Cites primary sources including survivor interviews
- Confidence: HIGH (extensively sourced secondary)

**VERIFICATION STATUS: ✅ TRIPLE-CONFIRMED**
- All 3 sources align: January 15, 1919, midday
- No discrepancies found
- Confidence: VERY HIGH
```

---

## SOURCES.md Format

```markdown
## Legal Sources

### 1. [Case Name] - Court Records

**Full Citation**:
[Full case citation]

**Document**: [Document type]
**Filed**: [Date]
**Pages**: [Page count]
**Outcome**: [Result]

**Retrieved**: [date]
**Archive**: [Location]

**Key Sections Used**:
- [Section 1 description]
- [Section 2 description]
```

---

## Discrepancy Documentation

```
DISCREPANCY FOUND:

FACT: [What fact has conflicting information]
SOURCE A: [Version 1]
SOURCE B: [Version 2]
SOURCE C: [Version 3 if applicable]

RESOLUTION: [Which version to use and why]
CONFIDENCE: [High/Medium/Low]
ACTION NEEDED: [What to verify further]
```

---

## Counter-Evidence Documentation

```
DEFENSE CLAIM: [What the opposing argument is]

SUPPORTING EVIDENCE:
- [Evidence point 1]
- [Evidence point 2]

CONTRADICTORY EVIDENCE:
- [Counter-evidence point 1]
- [Counter-evidence point 2]

RESOLUTION: [How this was resolved - court ruling, expert consensus, etc.]
CONFIDENCE: [Assessment of claim validity]
```

---

## Unresolved Questions Format

```
UNRESOLVED:
- [Question 1]
- [Question 2]

IMPACT: [Minor/Moderate/Major] - [Why]
MITIGATION: [How to handle in lyrics/narrative]
```

---

## Confidence Levels

| Level | Definition | Requirements |
|-------|------------|--------------|
| **HIGH** | 3+ primary sources, all align | Can state as fact |
| **MEDIUM** | 3+ sources, mix primary/secondary | Use "reportedly" or similar |
| **LOW** | Only secondary sources or conflicts | Flag for review |
| **UNVERIFIED** | Single source or no primary | Do not use without caveat |
add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks.Stars: 115kUpdated Claude CodeCodexVerifiedInstall