agentleFS
jxtsejxtse/scientific-research-skills/skills/social-media-paper-triage/SKILL.md

social-media-paper-triage

Skill68 starsChanged 7 months agoMITView on GitHub

Extracts paper recommendations from social-media posts and online articles (小红书 / Xiaohongshu / RedNote, 微信公众号 / WeChat Official Accounts, Twitter / X threads, Reddit posts, Bilibili videos, blog posts, newsletters, Jina Reader URLs), identifies the underlying academic papers, locates the authoritative original sources (arXiv, conference proceedings, DOI), and triages relevance to the user's research before any library action. Use when the user forwards a social-media link, screenshot, or article that mentions a paper / method / model, asks to "find the original paper" from a blog or thread, shares a 调研贴 / 论文推荐 / paper recommendation post, or wants to evaluate whether a buzz-worthy paper is worth reading before adding it to Zotero.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use platform-specific tools to fetch the full content:

    line 33
  2. Distinctive:

    Look for: paper titles, arXiv IDs, DOIs, author names + year citations

    line 47
  3. Distinctive:

    arXiv search: Check if it's on arXiv (most ML/AI papers are)

    line 55
  4. Distinctive:

    Semantic Scholar: Search by title for metadata + citation count

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Social Media Paper Triage

Turn social media paper recommendations into actionable research items.

When to Use

  • User forwards a 小红书 post about a paper
  • User shares a WeChat公众号 article discussing papers
  • User shares a Twitter/X thread about a paper or method
  • User asks "find the original paper from this link"
  • User shares any blog post / newsletter that references academic papers

Workflow

Step 1: Extract Content from Platform

Use platform-specific tools to fetch the full content:

PlatformToolCommand
小红书Agent Reach (XiaoHongShu)mcporter call 'xhs.get_note(note_url: "URL")'
WeChat公众号Agent Reach (WeChat)python3 ~/.agent-reach/.venv/bin/wechat_article.py "URL"
Twitter/Xxreachxreach tweet URL --json or xreach thread URL --json
RedditAgent Reachmcporter call 'reddit.read_post(url: "URL")'
BilibiliAgent Reachmcporter call 'bilibili.get_video_info(url: "URL")'
Any URLJina Readercurl -s "https://r.jina.ai/URL"

Step 2: Identify Papers

From the extracted content, identify all referenced papers:

  • Look for: paper titles, arXiv IDs, DOIs, author names + year citations
  • Distinguish between: the main paper being discussed vs. papers cited in passing
  • Note: social media posts often use informal titles or translated titles

Step 3: Find Original Sources

For each identified paper, find the authoritative source:

  1. arXiv search: Check if it's on arXiv (most ML/AI papers are)
  2. Semantic Scholar: Search by title for metadata + citation count
  3. Google Scholar (via web search): Fallback for non-arXiv papers

Priority: arXiv PDF > conference proceedings > journal version

Step 4: Summarize for Decision

Present a concise summary to the user:

📄 Paper: [Title]
👥 Authors: [First author] et al., [Year]
🏛 Venue: [Conference/Journal]
📊 Citations: [N]
🔗 Original: [arXiv/DOI link]
📱 Source: [social media link]

TL;DR: [2-3 sentence summary of what the paper does and why it matters]

Relevance to your work: [brief assessment based on user's research context]

Step 5: User Decision → Action

Based on user's response:

  • "Add to reading queue" → Add to Zotero 30_Reading Queue with appropriate tag
  • "Not relevant" → Done, no action
  • "Read it now" → Switch to paper-reading skill
  • "Save for later" → Add to Zotero with lower priority tag

Key Principles

  1. Always find the original paper — don't just summarize the social media post
  2. Don't auto-add to Zotero — summarize first, let user decide
  3. Preserve the social media link — add as a note/attachment in Zotero for provenance
  4. Assess relevance — use knowledge of user's active projects to judge fit
  5. Batch processing — if the post mentions multiple papers, triage all of them at once

Common Gotchas

  • WeChat articles often translate paper titles to Chinese — search by original English title
  • 小红书 posts may summarize methods inaccurately — always verify against the original
  • Twitter threads may reference preprints that have been updated/published since
  • Some posts discuss methods without naming specific papers — ask user for clarification

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.