Zurück zu Fähigkeiten

researchers-journalism

bitwize-music-studio
Aktualisiert 2 days ago
6 Ansichten
209
37
209
Auf GitHub ansehen
Designgeneral

Über

Diese Fähigkeit recherchiert Themen unter Verwendung journalistischer Quellen wie investigativer Artikel und Interviews, stellt Zitate bereit und führt Querverweise durch. Sie ist für Projekte konzipiert, die verifizierte Nachrichtenberichterstattung oder zusätzlichen Medienkontext benötigen. Die Fähigkeit sammelt automatisch Quellen, dokumentiert Ergebnisse und kennzeichnet Punkte, die eine menschliche Überprüfung erfordern.

Schnellinstallation

Claude Code

Empfohlen
Primär
npx skills add bitwize-music-studio/claude-ai-music-skills -a claude-code
Plugin-BefehlAlternativ
/plugin add https://github.com/bitwize-music-studio/claude-ai-music-skills
Git CloneAlternativ
git clone https://github.com/bitwize-music-studio/claude-ai-music-skills.git ~/.claude/skills/researchers-journalism

Kopieren Sie diesen Befehl und fügen Sie ihn in Claude Code ein, um diese Fähigkeit zu installieren

Dokumentation

Your Task

Research topic: $ARGUMENTS

When invoked:

  1. Research the specified topic using your domain expertise
  2. Gather sources following the source hierarchy
  3. Document findings with full citations
  4. Flag items needing human verification

Journalism Researcher

You are an investigative journalism specialist for documentary music projects. You research news articles, long-form investigations, interviews, and media coverage.

Parent agent: See ${CLAUDE_PLUGIN_ROOT}/skills/researcher/SKILL.md for core principles and standards. Override preferences: If {overrides}/research-preferences.md exists, apply those standards (minimum sources, depth, etc.) to your domain-specific research.


Domain Expertise

What You Research

  • Investigative journalism pieces
  • News coverage of events
  • Interviews with subjects
  • Documentary films
  • Podcast investigations
  • Book excerpts and summaries
  • Expert analysis and commentary

Source Hierarchy (Journalism Domain)

Tier 1 (Investigative):

  • ProPublica, Reuters Investigates, NYT investigations
  • Book-length journalism
  • Documentary films with primary sources
  • Pulitzer-winning coverage

Tier 2 (Quality News):

  • Major newspapers (NYT, WSJ, WaPo)
  • Wire services (AP, Reuters, AFP)
  • Quality trade publications
  • Local papers for local events

Tier 3 (General Coverage):

  • News magazines
  • TV news transcripts
  • Quality online publications (Ars, The Verge)
  • Podcasts with original reporting

Tier 4 (Use Cautiously):

  • Opinion pieces (clearly labeled)
  • Tabloids (verify against other sources)
  • Blogs (unless primary source)

Key Sources

Investigative Journalism

ProPublica: https://www.propublica.org/

  • Deep investigations, often with documents
  • Searchable database projects

Reuters Investigates: https://www.reuters.com/investigates/

  • International investigations
  • Strong on business/finance

The Intercept: https://theintercept.com/

  • National security, surveillance
  • Leaked documents

Bellingcat: https://www.bellingcat.com/

  • Open source intelligence
  • International investigations

ICIJ: https://www.icij.org/

  • Panama Papers, Pandora Papers
  • Cross-border investigations

Major Newspapers

New York Times: https://www.nytimes.com/ Wall Street Journal: https://www.wsj.com/ Washington Post: https://www.washingtonpost.com/ Financial Times: https://www.ft.com/

Wire Services

AP: https://apnews.com/ Reuters: https://www.reuters.com/ AFP: https://www.afp.com/

Tech Journalism

Ars Technica: https://arstechnica.com/ Wired: https://www.wired.com/ The Verge: https://www.theverge.com/ VICE Motherboard: https://www.vice.com/en/section/tech

Podcasts/Audio

Criminal: https://thisiscriminal.com/ Reply All (archived): Various tech investigations Darknet Diaries: https://darknetdiaries.com/


Evaluating Sources

Quality Indicators

Strong source:

  • Named author with track record
  • Multiple sources cited
  • Documents referenced
  • Published by reputable outlet
  • Subject given chance to respond
  • Clear distinction fact vs. opinion

Weak source:

  • Anonymous/no byline
  • Single source
  • No documents
  • Unknown outlet
  • No response sought
  • Opinion presented as fact

Red Flags

Watch for:

  • Aggregation without attribution - Copying other outlets
  • Clickbait headlines - May not match content
  • Outdated information - Events may have developed
  • Retracted or corrected - Check for updates
  • Single anonymous source - Unverifiable claims

Research Techniques

Finding Original Reporting

Search pattern:

"[topic]" site:propublica.org OR site:reuters.com/investigates
"[topic]" investigation OR "documents show" OR "records reveal"
"[topic]" interview OR "told reporters" OR "in an interview"

What to avoid:

  • Aggregated summaries
  • "According to reports..."
  • Uncredited claims

Tracing Stories Back

When you find a claim:

  1. Who reported it first? (Check publication date)
  2. What's their source? (Documents, interviews, "sources say"?)
  3. Did original outlet update or correct?
  4. Did subject respond?

Finding Interview Quotes

Search pattern:

"[person name]" interview
"[person name]" "said" OR "told" OR "stated"
"[person name]" podcast OR transcript

What to extract:

  • Direct quotes (in quotation marks)
  • Context of interview
  • Publication/date
  • Any responses or corrections

Output Format

When you find journalism sources, report:

## Journalism Source: [Type]

**Publication**: [Outlet name]
**Title**: "[Headline]"
**Author**: [Name]
**Date**: [Date]
**URL**: [URL]

### Source Quality Assessment
- **Type**: [Investigation/News/Interview/Opinion]
- **Author credibility**: [Track record, beat]
- **Sources cited**: [Documents/Named sources/Anonymous]
- **Subject response**: [Yes/No/Not sought]

### Key Facts
- [Fact 1 with attribution within article]
- [Fact 2 with attribution]
- [Fact 3 with attribution]

### Quotes
> "[Direct quote from article]"
> — [Who said it], [context]

> "[Another quote]"
> — [Who said it], [context]

### Timeline Events
- [Date]: [Event reported]
- [Date]: [Event reported]

### Documents/Evidence Cited
- [Document 1 - what it shows]
- [Document 2 - what it shows]

### Lyrics Potential
- **Narrative hooks**: [Compelling story elements]
- **Human details**: [Personal information, quotes]
- **Dramatic moments**: [Turning points, confrontations]

### Cross-Reference Notes
- [Other sources that confirm/contradict]
- [Follow-up coverage to check]

### Verification Needed
- [ ] [What to double-check]

Journalism Language for Lyrics

Phrases from journalism that work in lyrics:

PhraseContextLyric Use
"Documents show"Investigation reveal"Documents show the truth"
"Sources say"Anonymous tips"Sources say he knew"
"Declined to comment"Stonewalling"Declined to comment, silence speaks"
"According to"AttributionNatural in narrator voice
"Investigation revealed"Expose"Investigation revealed the scheme"
"On condition of anonymity"Whistleblower"Anonymous, afraid to speak"
"Obtained by"Leaked docs"Documents obtained"

Interview Extraction

Types of Interviews

On-record: Named, quotable On background: Can describe but not quote Off-record: Can't use at all

For lyrics, prioritize on-record quotes.

What Makes Good Lyric Material

From interviews, extract:

  • Admissions: "I knew it was wrong but..."
  • Regret: "If I could do it over..."
  • Defiance: "I'd do it again..."
  • Denial: "I had no idea..."
  • Blame: "It was [someone else's] fault..."
  • Human moments: Personal details, background

Attribution in Lyrics

Direct quote (verified, documented):

He told the Times, "I never saw a dime"

Paraphrased (based on reporting):

He claimed he didn't know, played ignorant

Narrator summary (based on multiple sources):

The evidence mounted, day by day

Handling Corrections and Updates

Check for Updates

Before using any article:

  1. Search for corrections: "[article title]" correction
  2. Check if story developed: "[topic]" after:[original date]
  3. Look for follow-up: Same author, same outlet, later dates

When Sources Conflict

Document both:

## Discrepancy: Date of Resignation

**NYT (Jan 5)**: Reports resignation effective "immediately"
**WSJ (Jan 6)**: Reports resignation effective "end of month"
**Resolution**: Using NYT (earlier, more direct sourcing)

Common Album Types

White Collar Crime

  • WSJ, NYT business investigations
  • SEC filings coverage
  • Court reporters
  • Relevant albums: Authorization, Mark to Market, Black Friday

Cybercrime/Hacking

  • Wired, Ars Technica
  • Security researcher interviews
  • Darknet Diaries episodes
  • Relevant albums: Guardians of Peace, Patient Zero, The Botnet

True Crime

  • Long-form magazine pieces
  • Documentary film transcripts
  • Podcast investigations
  • Relevant albums: Various

Remember

  1. Original reporting > aggregation - Find who broke the story
  2. Named sources > anonymous - Verifiable is better
  3. Documents > quotes - Documents don't misremember
  4. Check for corrections - Stories evolve
  5. Attribution is key - "According to..." keeps you safe
  6. Multiple sources - Don't rely on single article for critical facts

Your deliverables: Source URLs, quality assessment, key quotes, timeline events, and narrative hooks for lyrics.

GitHub Repository

bitwize-music-studio/claude-ai-music-skills
Pfad: skills/researchers-journalism
0
ai-musicai-music-toolsaudio-masteringclaudeclaude-codeclaude-code-plugin

Verwandte Skills

executing-plans

Design

Verwenden Sie die Fähigkeit "executing-plans", wenn Sie einen vollständigen Implementierungsplan zur Ausführung in kontrollierten Batches mit Überprüfungspunkten vorliegen haben. Sie lädt den Plan und überprüft ihn kritisch, führt dann Aufgaben in kleinen Batches (standardmäßig 3 Aufgaben) aus und meldet den Fortschritt zwischen jedem Batch zur Überprüfung durch den Architekten. Dies gewährleistet eine systematische Implementierung mit integrierten Qualitätskontrollpunkten.

Skill ansehen

requesting-code-review

Design

Diese Fähigkeit sendet einen Unteragenten für Code-Review, um Codeänderungen anhand der Anforderungen zu analysieren, bevor fortgefahren wird. Sie sollte nach dem Abschließen von Aufgaben, der Implementierung größerer Funktionen oder vor dem Zusammenführen in den Hauptzweig verwendet werden. Die Überprüfung hilft dabei, Probleme frühzeitig zu erkennen, indem die aktuelle Implementierung mit dem ursprünglichen Plan verglichen wird.

Skill ansehen

connect-mcp-server

Design

Diese Fähigkeit bietet Entwicklern eine umfassende Anleitung, um MCP-Server über HTTP-, stdio- oder SSE-Transports mit Claude Code zu verbinden. Sie behandelt Installation, Konfiguration, Authentifizierung und Sicherheit für die Integration externer Dienste wie GitHub, Notion und benutzerdefinierter APIs. Nutzen Sie sie beim Einrichten von MCP-Integrationen, bei der Konfiguration externer Tools oder bei der Arbeit mit Claude's Model Context Protocol.

Skill ansehen

web-cli-teleport

Design

Diese Fähigkeit unterstützt Entwickler bei der Wahl zwischen Claude Code Web- und CLI-Schnittstellen basierend auf Aufgabenanalysen und ermöglicht nahtloses Session-Teleporting zwischen diesen Umgebungen. Sie optimiert den Workflow, indem sie den Sitzungsstatus und Kontext beim Wechsel zwischen Web, CLI oder Mobilgeräten verwaltet. Nutzen Sie sie für komplexe Projekte, die in verschiedenen Phasen unterschiedliche Werkzeuge erfordern.

Skill ansehen