Comment mining
Use when the user wants to mine comments and replies for audience reactions, customer language, questions, objections, complaints, product ideas, buying intent, sentiment, or voice-of-customer insights from public social posts and videos.
How to use it
- Hit Copy the whole skill.
- Claude: ⋯ → Download .md, then Customize → Skills → Add → Upload skill.
ChatGPT: make a Project and paste it into Instructions.
Neither? Paste it at the top of a new chat — it works for that chat. - Describe your job in plain words. The AI follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit ScrapeCreators/social-media-research-skills/skills/comment-mining#main ~/.claude/skills/comment-miningFor one project only, change the path to .claude/skills/comment-mining.
Not working?
- Check which app you pasted it into — the steps above name the right one.
- Some skills need the paid tier of Claude or ChatGPT.
Paste into Claude, ChatGPT or Cursor.
Show the full text139 lines
Comment Mining
Overview
Mine public comments for what people actually ask, complain about, want, misunderstand, or repeat. The output should help with product research, content ideas, copywriting, objection handling, and audience understanding.
When to Use
Use this skill when the user asks to:
- analyze comments on a TikTok, YouTube video, Instagram Reel, Facebook post, Reddit post, or Rumble video
- find audience questions, objections, complaints, or buying intent
- extract voice-of-customer language
- find content ideas from comments
- understand sentiment around a post, creator, product, or topic
Comment Sources
| Platform | Endpoint |
|---|---|
| TikTok comments | /v1/tiktok/video/comments |
| TikTok replies | /v1/tiktok/video/comment/replies |
| YouTube comments | /v1/youtube/video/comments |
| YouTube replies | /v1/youtube/video/comment/replies |
| Instagram comments | /v2/instagram/post/comments |
| Facebook comments | /v1/facebook/post/comments |
| Facebook replies | /v1/facebook/post/comment/replies |
| Reddit comments | /v1/reddit/post/comments |
| Rumble comments | /v1/rumble/video/comments |
Workflow
Fetch comments
- Use the post/video URL whenever possible.
- Paginate when the endpoint supports it and the user wants depth.
- Preserve comment text, author if public, like/upvote count, timestamp, and source URL.
Clean lightly
- Remove obvious spam/duplicates.
- Keep slang, misspellings, and emotional wording if it is useful customer language.
- Do not over-normalize exact quotes.
Classify each useful comment Use these buckets:
- questions
- objections
- complaints/pain points
- praise
- confusion
- requests/feature ideas
- buying intent
- controversy/debate
- jokes/memes/culture signals
Cluster themes
- Group similar comments.
- Score themes by frequency and intensity.
- Highlight exact quotes for each theme.
Turn insights into actions Depending on the user's goal, produce:
- content ideas
- FAQ ideas
- landing page copy angles
- product ideas
- objection-handling bullets
- sales/support notes
Output Format
# Comment Mining Report
## Summary
- Source(s): {urls}
- Comments analyzed: {count}
- Confidence: High/Medium/Low
## Top Themes
| Theme | Type | Frequency | Intensity | Representative quote |
|---|---|---:|---|---|
## Audience Questions
- "..."
## Objections and Concerns
- **Objection:** ...
- Evidence: "..."
- Response angle: ...
## Buying Intent / Demand Signals
- "..."
## Exact Language to Reuse
- "..."
- "..."
## Content Ideas From Comments
1. ...
2. ...
Quality Guardrails
- Label sample size and confidence.
- Separate one loud comment from a repeated pattern.
- Preserve exact quotes for useful language.
- Avoid claiming broad market sentiment from one post's comments.
- Call out moderation/platform bias when relevant.
Common Pitfalls
- Do not flatten comments into generic sentiment. The value is in questions, objections, and exact wording.
- Do not include personally identifying details unless they are already public and necessary.
- Do not treat bot/spam comments as audience signal.
- Do not skip Reddit post context. For Reddit, read both the original post and comments.
| 1 | |
| 2 | name comment-mining |
| 3 | description Use when the user wants to mine comments and replies for audience reactions, customer language, questions, objections, complaints, product ideas, buying intent, sentiment, or voice-of-customer insights from public social posts and videos. |
| 4 | allowed-tools Bash, Read, Write, WebFetch |
| 5 | |
| 6 | version 1.0.0 |
| 7 | author ScrapeCreators |
| 8 | license MIT |
| 9 | homepage https://scrapecreators.com |
| 10 | repository https://github.com/ScrapeCreators/social-media-research-skills |
| 11 | metadata |
| 12 | openclaw |
| 13 | requires |
| 14 | env |
| 15 | - SCRAPECREATORS_API_KEY |
| 16 | primaryEnv SCRAPECREATORS_API_KEY |
| 17 | homepage https://scrapecreators.com |
| 18 | tags |
| 19 | - social-media |
| 20 | - research |
| 21 | - scrapecreators |
| 22 | |
| 23 | |
| 24 | # Comment Mining |
| 25 | |
| 26 | ## Overview |
| 27 | |
| 28 | Mine public comments for what people actually ask, complain about, want, misunderstand, or repeat. The output should help with product research, content ideas, copywriting, objection handling, and audience understanding. |
| 29 | |
| 30 | ## When to Use |
| 31 | |
| 32 | Use this skill when the user asks to: |
| 33 | |
| 34 | analyze comments on a TikTok, YouTube video, Instagram Reel, Facebook post, Reddit post, or Rumble video |
| 35 | find audience questions, objections, complaints, or buying intent |
| 36 | extract voice-of-customer language |
| 37 | find content ideas from comments |
| 38 | understand sentiment around a post, creator, product, or topic |
| 39 | |
| 40 | ## Comment Sources |
| 41 | |
| 42 | | Platform | Endpoint | |
| 43 | |---|---| |
| 44 | | TikTok comments | `/v1/tiktok/video/comments` | |
| 45 | | TikTok replies | `/v1/tiktok/video/comment/replies` | |
| 46 | | YouTube comments | `/v1/youtube/video/comments` | |
| 47 | | YouTube replies | `/v1/youtube/video/comment/replies` | |
| 48 | | Instagram comments | `/v2/instagram/post/comments` | |
| 49 | | Facebook comments | `/v1/facebook/post/comments` | |
| 50 | | Facebook replies | `/v1/facebook/post/comment/replies` | |
| 51 | | Reddit comments | `/v1/reddit/post/comments` | |
| 52 | | Rumble comments | `/v1/rumble/video/comments` | |
| 53 | |
| 54 | ## Workflow |
| 55 | |
| 56 | **Fetch comments** |
| 57 | Use the post/video URL whenever possible. |
| 58 | Paginate when the endpoint supports it and the user wants depth. |
| 59 | Preserve comment text, author if public, like/upvote count, timestamp, and source URL. |
| 60 | |
| 61 | **Clean lightly** |
| 62 | Remove obvious spam/duplicates. |
| 63 | Keep slang, misspellings, and emotional wording if it is useful customer language. |
| 64 | Do not over-normalize exact quotes. |
| 65 | |
| 66 | **Classify each useful comment** |
| 67 | Use these buckets: |
| 68 | questions |
| 69 | objections |
| 70 | complaints/pain points |
| 71 | praise |
| 72 | confusion |
| 73 | requests/feature ideas |
| 74 | buying intent |
| 75 | controversy/debate |
| 76 | jokes/memes/culture signals |
| 77 | |
| 78 | **Cluster themes** |
| 79 | Group similar comments. |
| 80 | Score themes by frequency and intensity. |
| 81 | Highlight exact quotes for each theme. |
| 82 | |
| 83 | **Turn insights into actions** |
| 84 | Depending on the user's goal, produce: |
| 85 | content ideas |
| 86 | FAQ ideas |
| 87 | landing page copy angles |
| 88 | product ideas |
| 89 | objection-handling bullets |
| 90 | sales/support notes |
| 91 | |
| 92 | ## Output Format |
| 93 | |
| 94 | |
| 95 | # Comment Mining Report |
| 96 | |
| 97 | ## Summary |
| 98 | - Source(s): {urls} |
| 99 | - Comments analyzed: {count} |
| 100 | - Confidence: High/Medium/Low |
| 101 | |
| 102 | ## Top Themes |
| 103 | | Theme | Type | Frequency | Intensity | Representative quote | |
| 104 | |---|---|---:|---|---| |
| 105 | |
| 106 | ## Audience Questions |
| 107 | - "..." |
| 108 | |
| 109 | ## Objections and Concerns |
| 110 | - **Objection:** ... |
| 111 | - Evidence: "..." |
| 112 | - Response angle: ... |
| 113 | |
| 114 | ## Buying Intent / Demand Signals |
| 115 | - "..." |
| 116 | |
| 117 | ## Exact Language to Reuse |
| 118 | - "..." |
| 119 | - "..." |
| 120 | |
| 121 | ## Content Ideas From Comments |
| 122 | 1. ... |
| 123 | 2. ... |
| 124 | |
| 125 | |
| 126 | ## Quality Guardrails |
| 127 | |
| 128 | Label sample size and confidence. |
| 129 | Separate one loud comment from a repeated pattern. |
| 130 | Preserve exact quotes for useful language. |
| 131 | Avoid claiming broad market sentiment from one post's comments. |
| 132 | Call out moderation/platform bias when relevant. |
| 133 | |
| 134 | ## Common Pitfalls |
| 135 | |
| 136 | Do not flatten comments into generic sentiment. The value is in questions, objections, and exact wording. |
| 137 | Do not include personally identifying details unless they are already public and necessary. |
| 138 | Do not treat bot/spam comments as audience signal. |
| 139 | Do not skip Reddit post context. For Reddit, read both the original post and comments. |