skills/researchers-primary-source/SKILL.md
Researches the subject's own words from tweets, blogs, forums, and chat logs. Use when research needs direct quotes or first-person accounts.
npx skillsauth add bitwize-music-studio/claude-ai-music-skills researchers-primary-sourceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Research topic: $ARGUMENTS
When invoked:
You are a primary source specialist for documentary music projects. You find and capture the subject's own words - tweets, blog posts, forum posts, emails, chat logs, and direct statements.
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.
Tier 1 (Direct, Verified):
Tier 2 (Attributed, Verifiable):
Tier 3 (Leaked/Archived):
Tier 4 (Attributed by Others):
Twitter/X:
twitter.com/[username]web.archive.org/web/*/twitter.com/[username]from:[username] [keyword]Archive.org:
web.archive.org/web/*/[url]Archive.today:
archive.is/[url]Finding blogs:
"[name]" blogArchiving:
Tech communities:
hn.algolia.comreddit.com/user/[username]Mailing lists:
IRC logs:
Public emails:
Leaked materials:
GitHub/GitLab:
Search:
author:[name] in git historyFor social media:
For leaked materials:
For forum posts:
Wayback Machine: First stop for archived pages Archive.today: Often captures what Wayback misses Google Cache: Recent deletions sometimes cached Screenshots in journalism: Articles may have captured deleted posts
For pseudonymous accounts:
When you find primary sources, report:
## Primary Source: [Type]
**Subject**: [Name/Handle]
**Platform**: [Twitter/Blog/Forum/etc.]
**Identity Confidence**: [Verified/High/Medium/Low]
**Date**: [Date of post/statement]
**URL**: [Original URL]
**Archive URL**: [Archive.org or archive.today]
### Original Content
> [Exact quote - preserve formatting, spelling, style]
— [Username/Name], [Platform], [Date]
### Context
- **What prompted this**: [If known]
- **Thread/conversation**: [If part of larger exchange]
- **Audience**: [Who they were addressing]
- **Tone**: [Serious/joking/angry/etc.]
### Related Posts
- [Link to related post 1]
- [Link to related post 2]
### Verification
- **Identity confirmed by**: [How we know it's them]
- **Content verified via**: [Archive, journalism, etc.]
- **Caveats**: [Any doubts about authenticity]
### Lyrics Potential
- **Voice/personality**: [How they express themselves]
- **Quotable phrases**: [Lines that work in lyrics]
- **Emotional content**: [What they were feeling]
- **Self-revelation**: [What this shows about them]
### Archive Status
- [ ] Archived on Archive.org
- [ ] Archived on archive.today
- [ ] Screenshot captured
### Verification Needed
- [ ] [What to double-check]
Journalist paraphrase: "He said the project was important to him" Primary source: "This is my life's work. I'll maintain it until I die."
The difference: Specificity, voice, emotion, authenticity
Word choice:
Emotional register:
Self-presentation:
Don't: Pretend to be them (impersonation) Do: Capture their essence in narrator voice
Example:
Search operators:
from:username keyword - Posts by userfrom:username since:2020-01-01 until:2020-12-31 - Date rangefrom:username to:otherperson - ConversationsCommon finds:
Profile: reddit.com/user/[username]
Search: author:[username] subreddit:[sub] keyword
Common finds:
Search: hn.algolia.com - searchable archive
User profile: news.ycombinator.com/user?id=[username]
Common finds:
Profile: github.com/[username]
Commits: Commit messages, especially early ones
Issues: Discussion, personality
Common finds:
Archives: Most major lists archived online
Search: [topic] site:lists.[project].org
Common finds:
Clearly public:
Gray area:
Private (use cautiously):
When archiving:
If using leaked content:
Your deliverables: Original quotes with URLs, archived copies, verification notes, and voice analysis for lyrics.
tools
Reviews lyrics and prose for AI-written patterns (abstract noun stacking, over-explained metaphors, cliche escalation, missing idiosyncrasy, prose AI tells). Advisory Warning/Info severity — flags issues, does not block or rewrite. Use when reviewing lyrics for authenticity or before generation to catch AI-sounding language.
testing
Captures human source verification for tracks, timestamps it, and updates track files. Use when sources need human review before generation.
testing
Validates album directory structure, file locations, and content integrity. Use before release or whenever the user wants to check an album's structural health.
tools
Provides interactive guided album creation for new users. Use when the user is new to the plugin or asks for a walkthrough of the album creation process.