agentleFS
Jam0731Jam0731/ParallaxAI/skills/google-trends/SKILL.md

google-trends

Skill2 starsChanged 5 months agoMITView on GitHub

Monitor Google Trends - get trending searches, compare keywords, and track interest over time. Use for market research, content planning, and trend analysis.

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. terryds/google-trends-skill★ 6same name
    2. prikotov/google-trends★ 1same name
    3. teimurjan/skills★ 1same name
    4. arcadiumdata/skills★ 0same name

    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.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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 web_fetch to get Google Trends RSS:

    line 34
  2. Distinctive:

    Compare with baseline: - Use a stable term for reference

    line 165

≈ “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

Google Trends Monitoring

Monitor and analyze Google Trends data for market research, content planning, and trend tracking.

Capabilities

  1. Daily Trending Searches - What's trending today in any country
  2. Keyword Interest Over Time - Historical trend data for keywords
  3. Keyword Comparison - Compare multiple keywords
  4. Related Topics & Queries - Discover related searches
  5. Regional Interest - See where keywords are most popular

Usage

Get Trending Searches (Today)

Use web_fetch to get Google Trends RSS:

# US Daily Trends
curl -s "https://trends.google.com/trending/rss?geo=US" | head -100

# Lithuania
curl -s "https://trends.google.com/trending/rss?geo=LT" | head -100

# Worldwide
curl -s "https://trends.google.com/trending/rss?geo=" | head -100

Check Keyword Interest

For detailed keyword analysis, use the Google Trends website:

# Open in browser
open "https://trends.google.com/trends/explore?q=bitcoin&geo=US"

# Or fetch via web_fetch for basic data
web_fetch "https://trends.google.com/trends/explore?q=bitcoin"

Compare Keywords

# Compare multiple terms (comma-separated)
open "https://trends.google.com/trends/explore?q=bitcoin,ethereum,solana&geo=US"

Scripts

trends-daily.sh

Get today's trending searches:

#!/bin/bash
# Usage: ./trends-daily.sh [country_code]
# Example: ./trends-daily.sh LT

GEO="${1:-US}"
curl -s "https://trends.google.com/trending/rss?geo=$GEO" | \
  grep -o '<title>[^<]*</title>' | \
  sed 's/<[^>]*>//g' | \
  tail -n +2 | \
  head -20

trends-compare.sh

Generate comparison URL:

#!/bin/bash
# Usage: ./trends-compare.sh keyword1 keyword2 keyword3
# Example: ./trends-compare.sh bitcoin ethereum solana

KEYWORDS=$(echo "$@" | tr ' ' ',')
echo "https://trends.google.com/trends/explore?q=$KEYWORDS"

Example Workflows

Morning Market Research

1. Get US trending searches
2. Get LT trending searches  
3. Check if any trends relate to our business
4. Report interesting findings

Content Planning

1. Compare potential blog topics
2. Find which has more search interest
3. Check seasonal patterns
4. Decide on content focus

Competitor Monitoring

1. Compare brand names
2. Track interest over time
3. Identify when competitors spike
4. Investigate causes

Cron Job Integration

Set up automated trend monitoring:

// Example cron job for daily trends report
{
  "name": "Daily Trends Report",
  "schedule": { "kind": "cron", "expr": "0 9 * * *" },
  "payload": {
    "kind": "agentTurn",
    "message": "Get today's Google Trends for US and LT. Summarize top 10 trends for each. Highlight any tech/business related trends."
  }
}

Countries

Common country codes:

  • US - United States
  • LT - Lithuania
  • DE - Germany
  • GB - United Kingdom
  • FR - France
  • JP - Japan
  • (empty) - Worldwide

Limitations

  • Google Trends doesn't provide official API
  • Rate limiting may apply for heavy usage
  • Data is relative (not absolute numbers)
  • Historical data limited to ~5 years for detailed view

Tips

  1. Use specific terms - "iPhone 15 Pro" vs just "iPhone"
  2. Check seasonality - Some trends are cyclical
  3. Compare with baseline - Use a stable term for reference
  4. Look at related queries - Discover new opportunities
  5. Monitor competitors - Track brand interest over time

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.