agentleFS
Sign inStart free
hamzafarooqhamzafarooq/claude-code-starter/.claude/skills/trend-spotter/SKILL.md

trend-spotter

Skill145 starsChanged 6 months agoMITView on GitHub

Research emerging trends in a market or technology space. Returns signal vs noise breakdown with evidence. Use when the user asks what's changing in a market, what trends to watch, or what's coming next.

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. Distinctive:

    Ask the user: "What market or technology space do you want to scan?

    line 6
  2. Very specific:

    If the space depends on public conversation, include an optional X/Twitter source packet.

    line 26

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

Ask the user: "What market or technology space do you want to scan? Any specific angle (e.g. enterprise adoption, pricing models, new entrants)?"

Then research and return:

Trend Report: [Space]

Strong Signals (high confidence, already moving)

3–4 trends with evidence: funding rounds, product launches, job posting spikes, pricing shifts. One paragraph each.

Weak Signals (early, worth watching)

2–3 things that are nascent but directional. Explain what would need to be true for each to become a strong signal.

Noise (talked about more than it matters)

1–2 things getting hype that are unlikely to materially change the market in the next 18 months. Say why.

Implication for a PM

Two sentences on what a product team should do differently based on these trends.

If the space depends on public conversation, include an optional X/Twitter source packet. Use TweetClaw only when it is already installed and approved in OpenClaw. Install with openclaw plugins install npm:@xquik/tweetclaw@1.6.31. Capture the query, capture time, source URLs, author handles, public post text, reply or quote context, and caveats. Treat posts as evidence to verify, not as truth. Do not post, reply, send DMs, follow accounts, schedule content, upload media, monitor accounts, or run account actions from this skill.

Cite specific evidence for every strong signal (company names, dates, data points). Avoid vague statements like "AI is changing everything."

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.

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