agentleFS
Sign inStart free
retracnretracn/automationnation-data-tools/skills/market-research/SKILL.md

market-research

Skill0 starsChanged 40 days agoMITView on GitHub

Research demand, prices and news for a market, product or topic with live Google data. Use when the user asks what's trending, how interest in something is changing, seasonality, comparing products or brands by search interest, current prices of a product, recent news about a company, or job market demand.

113 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use everything-claude-code, everything-claude-code-conventions 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.
  • InfopibeSkill

    everything-claude-code

    Also in 9 projects that use this

  • mryeastcodeSkill

    everything-claude-code-conventions

    Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.

    Also in 8 projects that use this

  • InfopibeSkill

    investor-outreach

    Draft cold emails, warm intro blurbs, follow-ups, update emails, and investor communications for fundraising. Use when the user wants outreach to angels, VCs, strategic investors, or accelerators and needs concise, personalized, investor-facing messaging.

    Also in 22 projects that use this

  • shawnpangSkill

    competitor-monitoring

    When the user wants to set up ongoing tracking of competitor activity — pricing changes, feature launches, hiring signals, content, or public mentions. Also use when the user mentions "track competitors", "what are competitors doing", "competitor alerts", or "market watch".

    Also in 3 projects that use this

  • tpavanipradeepSkill

    nextjs-turbopack

    Next.js 16+ and Turbopack — incremental bundling, FS caching, dev speed, and when to use Turbopack vs webpack.

    Also in 14 projects that use this

  • niloykumarbarmanSkill

    agent-sort

    Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.

    Also in 7 projects that use this

  • +1 more from Infopibe

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 99 edited versions we read keep these.

  • 0

    Distinctive

    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:

    If these tools aren't available, the AutomationNation connector isn't connected: ask the user to add …

    line 16

“Common” is measured: kept by at least 6 in 10 of the 99 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

Combine the AutomationNation connector's research tools as the question needs. Through Apify's hosted connector each tool name carries a prefix and a short suffix, for example automati--data-tools-mcp-server--get_google_trends-7d5f; match tools by the name in the middle:

  • get_google_trends: interest over time, top regions and rising searches for up to 5 terms. Set compare to put terms on one scale, geo for a country or region, and time_range.
  • get_trending_searches: what's trending right now in a country.
  • search_google_shopping: current prices, discounts, stores and ratings for a product in a country.
  • search_google_news: recent coverage. Use sort_by: date and time for "latest" questions.
  • search_jobs: job listings and salaries, as a demand signal for skills or roles.

Work in this order: frame the question, pull the minimum data that answers it, then report findings with numbers and dates (for example "interest up 34% over the last 90 days, peak on 9 September"). Separate what the data shows from your interpretation. Keep max_results modest: every call is billed per result on the user's Apify account.

If these tools aren't available, the AutomationNation connector isn't connected: ask the user to add https://mcp.apify.com/?tools=automationnation/data-tools-mcp-server as an MCP server or connector and sign in with a free Apify account, then continue.

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.

Check your setup, free