agentleFS
athina-aiathina-ai/goose-skills/skills/shared/comment-mining/SKILL.md

comment-mining

Skill1.3k starsChanged 19 days agoMITView on GitHub

Mine comments and replies on social posts, videos, and ads for recurring customer language, questions, objections, desired outcomes, complaints, product requests, purchase signals, and creative opportunities. Use for voice-of-customer research grounded in linked source evidence.

3 other projects use a version of this.

Trending

Quiet since March.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the athina-ai/goose-skills repository that our weekly crawl found: only 1 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about athina-ai/goose-skills

The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use scrapecreators-api to collect post context, top-level comments, and replies from the relevant platforms.

    line 18
  2. Distinctive:

    Never expose private information, infer sensitive traits, or claim the sample represents all customers.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Comment Mining

Turn public comment threads into evidence a growth team can use.

Inputs

  • Brand/product and research question.
  • Post, reel, video, or ad URLs; or creators/competitors to sample.
  • Target market, platforms, time window, and desired sample size.

Workflow

  1. Use scrapecreators-api to collect post context, top-level comments, and replies from the relevant platforms. Sample across multiple posts and creators instead of overfitting to one viral thread.
  2. Preserve parent-and-reply context where it changes meaning. Remove obvious spam, duplicate comments, tag-only replies, and giveaways unless they are the subject of the study.
  3. Code each useful comment into one or more buckets: pain, desired outcome, objection, question, comparison, use case, purchase intent, product request, workaround, delight, complaint, churn risk, or exact product language.
  4. Mark buying-intent strength separately: curiosity, consideration, price or availability question, comparison, stated purchase, repeat use, and recommendation.
  5. Cluster semantically similar statements while retaining representative wording, the post context, and source links.
  6. Report prevalence as sample counts by platform and source type, not market-wide percentages.
  7. Convert the strongest clusters into testable messages, hooks, FAQ topics, product questions, or research follow-ups.

Output

  • Coverage and sampling method.
  • Ranked theme table with top-level and reply counts, representative language, source links, and confidence.
  • Objection and question bank.
  • Purchase, product-request, workaround, and churn signals.
  • Recommended next tests for creative, landing pages, content, or product research.
  • Limitations and gaps.

Never expose private information, infer sensitive traits, or claim the sample represents all customers.

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.