Researchers Primary Source logo

Researchers Primary Source

Organization
bitwize-music-studio
researchers-primary-source

Researches the subject's own words from tweets, blogs, forums, and chat logs. Use when research needs direct quotes or first-person accounts.

Overview

Publisherbitwize-music-studio
Repositoryclaude-ai-music-skills
Skill nameresearchers-primary-source
Stars
546
Forks
130
Bundled files
1
LicenseCC0-1.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by bitwize-music-studio on GitHub. Read the source before you install it.

Installation

Install the Researchers Primary Source AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/researchers-primary-source
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skills.git /tmp/claude-ai-music-skills
mkdir -p .claude/skills
cp -r /tmp/claude-ai-music-skills/skills/researchers-primary-source .claude/skills/researchers-primary-source
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Researchers Primary Source in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Researchers Primary Source on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Researchers Primary Source is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

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:

markdown
## 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 user
  • from:username since:2020-01-01 until:2020-12-31 - Date range
  • from:username to:otherperson - Conversations

Common finds:

  • Announcements
  • Reactions to events
  • Interactions with others
  • Personality/humor

Reddit

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

  1. Their words > paraphrase - Primary sources have authenticity journalism lacks
  2. Archive immediately - Content disappears; save it now
  3. Verify identity - Confirm the account belongs to who you think
  4. Context matters - A joke isn't a confession
  5. Voice is character - How they talk reveals who they are
  6. Timestamp everything - When they said it matters

Your deliverables: Original quotes with URLs, archived copies, verification notes, and voice analysis for lyrics.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Researchers Primary Source AI skill do?

Researches the subject's own words from tweets, blogs, forums, and chat logs. Use when research needs direct quotes or first-person accounts.

Why use Researchers Primary Source on TypingMind?

Because you install it once and use it with any model. Researchers Primary Source is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Researchers Primary Source in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/researchers-primary-source. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Researchers Primary Source?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Researchers Primary Source?

As many as you like. As long as a model supports skills, you can use Researchers Primary Source with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Researchers Primary Source AI skill free?

Yes. It is published on GitHub by bitwize-music-studio under the CC0-1.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇