agentleFS
Sign inStart free
EpistatesEpistates/sparX/.claude/skills/research/SKILL.md

research

Skill3 starsChanged 7 months agoMITView on GitHub

Research trending topics, conversations, and content opportunities for X posts. Use when the user wants content ideas, wants to know what's trending in their niche, or needs to research what to post about.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 164 edited versions we read keep these.

  • 9

    Distinctive

    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:

    Search for current conversations and trends using WebSearch:

    line 22
  2. Distinctive:

    Use WebSearch with queries like:

    line 30
  3. Distinctive:

    Read the actual discussions, not just search snippets

    line 40
  4. Distinctive:

    Look for: debates, strong opinions, "unpopular opinion" threads

    line 47
  5. Distinctive:

    Look for: "How do I...", Stack Overflow trending, common mistakes

    line 51
  6. Distinctive:

    Look for: GitHub releases, product launches, API changes

    line 55
  7. Distinctive:

    Look for: "X vs Y", "switching from A to B", benchmark results

    line 59
  8. Distinctive:

    Look for: "I hate when...", "why can't...", bug reports, rants

    line 63
  9. Distinctive:

    Look for: What others are sharing about their progress

    line 67

“Common” is measured: kept by at least 6 in 10 of the 164 edited versions of this file we could read. “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

Topic & Trend Research for X Content

Research what's being discussed, debated, and shared in a specific niche to identify high-potential content opportunities.

Input

The user provides:

  • A niche or topic to research (e.g., "Rust", "local LLMs", "developer tools")
  • Or asks "what should I post about?"
  • Or wants to understand what's trending

Process

Step 1 — Web Research

Search for current conversations and trends using WebSearch:

  1. Search X/Twitter directly for the niche topic + "2026" to find recent discussions
  2. Search Reddit (r/programming, niche subreddits) for hot topics
  3. Search Hacker News for trending technical discussions
  4. Search for recent releases/announcements in the niche
  5. Search for controversies or debates (these drive highest engagement)

Use WebSearch with queries like:

  • site:x.com [niche topic] 2026
  • [niche] trending discussion March 2026
  • [niche] controversial opinion 2026
  • [niche] new release announcement 2026

Deep-read promising results using WebFetch to extract full content from the most relevant search results. This gives you the actual conversations, not just titles.

If chrome is available and you need to browse X's live feed for real-time conversations, you can navigate to X search:

  • https://x.com/search?q=[topic]&f=live — latest posts on the topic
  • Read the actual discussions, not just search snippets

Step 2 — Identify Content Opportunities

Categorize findings into opportunity types:

Hot Takes — Controversial discussions where you can add a unique perspective

  • Look for: debates, strong opinions, "unpopular opinion" threads
  • Signal: High reply counts indicate engagement potential

Tutorials — Questions people are asking that you can answer

  • Look for: "How do I...", Stack Overflow trending, common mistakes
  • Signal: Repeat questions indicate unmet demand

Announcements — New releases, updates, or changes you can contextualize

  • Look for: GitHub releases, product launches, API changes
  • Signal: Timing matters — first-mover advantage in commentary

Comparisons — Tools/approaches being debated

  • Look for: "X vs Y", "switching from A to B", benchmark results
  • Signal: People love definitive comparisons with data

Pain Points — Frustrations being expressed

  • Look for: "I hate when...", "why can't...", bug reports, rants
  • Signal: Pain point posts have extremely low negative signal risk

Build-in-Public — Trends in the making/building space

  • Look for: What others are sharing about their progress
  • Signal: Gaps in what's being shared that you could fill

Step 3 — Prioritize by Phoenix Score Potential

Rank opportunities by predicted engagement:

  1. Conversation potential — Will this generate replies the author can respond to? (75–150× for author reply threads, 13–27× for replies)
  2. Bookmark potential — Is this save-worthy reference material? (~10× weight)
  3. Dwell potential — Will people spend time reading carefully? (high weight)
  4. Timeliness — Is this trending NOW? (freshness bonus)
  5. Authenticity fit — Can you write about this genuinely? (reduces negative risk)

Step 4 — Generate Content Briefs

For the top 5 opportunities, create a brief:

## Opportunity: [Title]

**Why now**: [What's happening that makes this timely]
**Angle**: [Your unique perspective or value-add]
**Format**: [Post / Thread / Poll / Quote tweet]
**Hook idea**: [Draft opening line]
**Key points**: [3-5 bullets of what to cover]
**Reply trigger**: [The question or take that will drive replies]
**Risk**: [Low / Medium — any negative signal concerns]

Step 5 — Output

Present:

  1. Trend summary — What's happening in the niche right now (2-3 sentences)
  2. Top 5 content opportunities — Ranked by predicted engagement
  3. Content briefs — For each opportunity
  4. Suggested posting schedule — When to publish each piece
  5. Reply farming targets — 5-10 active discussions to engage with (builds visibility before posting)

Tips

  • The best content comes from the intersection of what's trending + what you genuinely know
  • "Reply farming" (engaging in relevant conversations) for 15-30 min before posting increases your visibility to the algorithm
  • Time-sensitive opportunities should be published within 24-48 hours
  • Evergreen opportunities can be queued for optimal timing

Download now (ZIP)

  • Other versions185 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 185

    1. mattpocock/skills★ 303ksame name
    2. Yeachan-Heo/oh-my-claudecode★ 40ksame name
    3. Yeachan-Heo/oh-my-claude-sisyphus★ 40ksame name
    4. QuivrHQ/quivr★ 40ksame name
    5. udecode/plate★ 17ksame name
    6. openai/plugins★ 7.4ksame name
    7. ArcReel/ArcReel★ 6ksame name
    8. vinvcn/mattpocock-skills-zh-CN★ 5.3ksame name
    9. withcoral/coral★ 4.9ksame name
    10. docker/docs★ 4.7ksame name

    175 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use daily-arxiv, exp-eval and 10 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • LambenthanSkill

      daily-arxiv

      每日从 arXiv 拉取新论文，过滤相关性，auto-ingest 高优先级论文，检测 SOTA 更新

      Also in 5 projects that use this

    • LambenthanSkill

      exp-eval

      实验判决门：Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges

      Also in 5 projects that use this

    • truongtv22Skill

      Problem-Solving Techniques

      Apply systematic problem-solving techniques for complexity spirals (simplification cascades), innovation blocks (collision-zone thinking), recurring patterns (meta-pattern recognition), assumption constraints (inversion exercise), scale uncertainty (scale game), and dispatch when stuck. Techniques derived from Microsoft Amplifier project patterns adapted for immediate application.

      Also in 5 projects that use this

    • liufeng1976Skill

      setup-ts-deep-modules

      Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

      Also in 33 projects that use this

    • parcadeiSkill

      ast-grep-find

      AST-based code search and refactoring via ast-grep MCP

      Also in 4 projects that use this

    • parcadeiSkill

      debug-hooks

      Systematic hook debugging workflow. Use when hooks aren't firing, producing wrong output, or behaving unexpectedly.

      Also in 4 projects that use this

    • +5 more from Lambenthan
  • In this repository15 other files it gives its agents.

Does it work?

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

Reviews can't be read right now.

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.

Check your setup, free