researchers-primary-source
정보
이 스킬은 트윗, 블로그, 포럼과 같은 1인칭 출처에서 대상의 직접 인용문을 검색하고 추출합니다. 2차 보도가 아닌 진정한 1차 기록이 필요한 연구를 위해 설계되었습니다. 이 도구는 웹 검색과 파일 작업을 활용하여 출처를 자동으로 수집하고, 인용을 문서화하며, 검증이 필요한 항목을 표시합니다.
빠른 설치
Claude Code
추천npx skills add bitwize-music-studio/claude-ai-music-skills -a claude-code/plugin add https://github.com/bitwize-music-studio/claude-ai-music-skillsgit clone https://github.com/bitwize-music-studio/claude-ai-music-skills.git ~/.claude/skills/researchers-primary-sourceClaude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요
문서
Your Task
Research topic: $ARGUMENTS
When invoked:
- Research the specified topic using your domain expertise
- Gather sources following the source hierarchy
- Document findings with full citations
- Flag items needing human verification
Primary Source Researcher
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.
Domain Expertise
What You Research
- Social media posts (Twitter/X, Facebook, LinkedIn)
- Personal blog posts
- Forum posts and comments
- IRC/chat logs
- Emails (if public/leaked)
- Conference talks and speeches
- Podcast appearances (as guest)
- Video interviews
- Written statements and manifestos
- Code comments and commit messages
Source Hierarchy (Primary Source Domain)
Tier 1 (Direct, Verified):
- Official social media accounts
- Personal blogs/websites
- Published writings
- Recorded talks/interviews
Tier 2 (Attributed, Verifiable):
- Forum posts with consistent identity
- Mailing list posts
- Code commits with verified authorship
- Court exhibits (authenticated)
Tier 3 (Leaked/Archived):
- Leaked emails (verify authenticity)
- Deleted social media (via archives)
- Chat logs (verify source)
- Internal documents (via journalism)
Tier 4 (Attributed by Others):
- Quotes in journalism (verify against original if possible)
- Second-hand accounts of statements
Key Sources
Social Media Archives
Twitter/X:
- Direct profile:
twitter.com/[username] - Wayback Machine:
web.archive.org/web/*/twitter.com/[username] - Search:
from:[username] [keyword]
Archive.org:
- Captures deleted tweets, old profiles
- Search:
web.archive.org/web/*/[url]
Archive.today:
- User-submitted snapshots
- Search:
archive.is/[url]
Personal Blogs
Finding blogs:
- Search:
"[name]" blog - Check personal websites
- Look for Medium, Substack accounts
- Technical people: dev.to, personal domains
Archiving:
- Wayback Machine for deleted posts
- archive.today for preservation
Forums and Communities
Tech communities:
- Hacker News:
hn.algolia.com - Reddit:
reddit.com/user/[username] - Stack Overflow: profiles, comments
- Slashdot: old tech discussions
Mailing lists:
- LKML, Debian lists, etc.
- Often archived and searchable
IRC logs:
- Some channels publish logs
- Leaked logs from breaches
Email and Documents
Public emails:
- Mailing list archives
- FOIA releases
- Court exhibits
Leaked materials:
- Verify via journalism coverage
- Note provenance
- Consider ethical implications
Code and Commits
GitHub/GitLab:
- Commit messages
- Issue comments
- README files
- Code comments
Search:
author:[name]in git history- GitHub search for usernames
Verification Techniques
Authenticating Sources
For social media:
- Verified accounts
- Consistent posting history
- Cross-reference with known statements
- Check for impersonation warnings
For leaked materials:
- Has journalism verified?
- Does content match known facts?
- Is provenance documented?
- Any denials of authenticity?
For forum posts:
- Account creation date
- Posting history consistency
- Cross-reference with other platforms
- Any self-identification?
Dealing with Deleted Content
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
Confirming Identity
For pseudonymous accounts:
- Self-identification elsewhere
- Journalism linking accounts
- Consistent technical details
- Court documents identifying
Output Format
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]
Capturing Voice
Why Primary Sources Matter
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
What to Capture
Word choice:
- How do they talk? (Formal/casual, technical/accessible)
- Repeated phrases or verbal tics
- Profanity, humor, formality level
Emotional register:
- When are they passionate?
- When are they defensive?
- When are they vulnerable?
Self-presentation:
- How do they describe themselves?
- What do they emphasize?
- What do they downplay?
Using Voice in Lyrics
Don't: Pretend to be them (impersonation) Do: Capture their essence in narrator voice
Example:
- Primary source: "I don't care about money. I just want the code to be free."
- Lyric: "He said he didn't care about the money / Just wanted the code to run free"
Platform-Specific Tips
Twitter/X
Search operators:
from:username keyword- Posts by userfrom:username since:2020-01-01 until:2020-12-31- Date rangefrom:username to:otherperson- Conversations
Common finds:
- Announcements
- Reactions to events
- Interactions with others
- Personality/humor
Profile: reddit.com/user/[username]
Search: author:[username] subreddit:[sub] keyword
Common finds:
- AMAs (Ask Me Anything)
- Technical discussions
- Community interaction
- Candid moments
Hacker News
Search: hn.algolia.com - searchable archive
User profile: news.ycombinator.com/user?id=[username]
Common finds:
- Tech founders often active
- Product announcements
- Industry commentary
- Early discussions
GitHub
Profile: github.com/[username]
Commits: Commit messages, especially early ones
Issues: Discussion, personality
Common finds:
- Philosophy in README files
- Personality in commit messages
- Interactions with community
Mailing Lists
Archives: Most major lists archived online
Search: [topic] site:lists.[project].org
Common finds:
- Original announcements
- Technical decisions
- Community debates
- Personality in arguments
Ethical Considerations
Public vs. Private
Clearly public:
- Public social media
- Published blog posts
- Conference talks
- Public forum posts
Gray area:
- Deleted posts (archived)
- Semi-private forums
- Old posts (context changed)
Private (use cautiously):
- Leaked emails
- Private messages
- Closed group discussions
Preservation vs. Privacy
When archiving:
- Consider if subject would expect permanence
- Note if content was deleted
- Consider context of deletion
Using Leaked Materials
If using leaked content:
- Verify authenticity
- Note provenance
- Consider ethical implications
- Follow journalism standards
Common Album Types
Tech Founders
- Blog posts explaining philosophy
- Mailing list announcements
- Forum interactions
- Conference talks
- Relevant albums: Distros
Hackers/Cybercriminals
- Forum posts
- IRC logs
- Manifestos
- Social media
- Relevant albums: Various cyber
Executives/Business Figures
- Twitter presence
- LinkedIn posts
- Conference talks
- Media interviews
- Relevant albums: Various corporate
Remember
- Their words > paraphrase - Primary sources have authenticity journalism lacks
- Archive immediately - Content disappears; save it now
- Verify identity - Confirm the account belongs to who you think
- Context matters - A joke isn't a confession
- Voice is character - How they talk reveals who they are
- Timestamp everything - When they said it matters
Your deliverables: Original quotes with URLs, archived copies, verification notes, and voice analysis for lyrics.
GitHub 저장소
연관 스킬
release-standards
문서 처리이 스킬은 소프트웨어 릴리스에 대한 시맨틱 버저닝(semver) 가이드라인과 변경 로그 형식 표준을 제공합니다. 릴리스를 준비할 때 버전 번호(메이저/마이너/패치)를 올바르게 증가시키고 변경 로그 항목을 구성하려면 이 스킬을 사용하세요. 사전 릴리스 식별자 규칙과 개발자를 위한 명확한 예시가 포함되어 있습니다.
commit-standards
문서 처리이 스킬은 Conventional Commits 표준에 따라 Git 커밋 메시지를 형식화합니다. 커밋 작성이나 리뷰 시 일관성을 보장하기 위해 템플릿과 유형 정의(예: `feat`, `fix`, `refactor`)를 제공합니다. 커밋 과정에서 이를 사용하여 명확하고 구조화된 커밋 기록을 생성할 수 있습니다.
huggingface-tokenizers
문서 처리이 스킬은 HuggingFace의 Rust 기반 라이브러리를 사용하여 1GB 텍스트를 20초 이내에 처리하는 고성능 토크나이제이션을 제공합니다. BPE, WordPiece, Unigram 알고리즘을 지원하며 사용자 정의 토크나이저 학습과 정렬 추적 기능을 포함합니다. 프로덕션 수준의 고속 토크나이제이션이 필요하거나 transformers 생태계와 통합된 맞춤형 토크나이저를 구축할 때 사용하세요.
nano-pdf
문서 처리nano-pdf는 개발자가 특정 페이지의 텍스트 변경이나 오타 수정과 같은 자연어 지시를 사용해 PDF를 편집할 수 있는 CLI 도구입니다. 터미널에서 직접 빠르고 프로그래밍 방식으로 PDF를 수정하는 데 이상적입니다. 페이지 번호 매기기가 버전마다 다를 수 있으므로 출력 결과는 항상 확인하세요.
