Threads Profile Search
browser-act/skills
Discovers Threads user accounts by keyword, extracting profile data including username, display name, verification status, biography, and follower count.
A skill your agent uses when the user asks to "find trending topics", "what trends should my brand jump on", or "time a campaign around a cultural moment"; produces a ranked trend report with…
Install Trend Spotter
$ npx skills add aaron-he-zhu/aaron-marketing-skills --skill trend-spotter -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aaron-he-zhu/aaron-marketing-skills trend-spotter --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/aaron-he-zhu/aaron-marketing-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/influencer/scout/trend-spotter .claude/skills/trend-spotter && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "trend-spotter" agent skill from https://github.com/aaron-he-zhu/aaron-marketing-skills/tree/main/influencer/scout/trend-spotter into .claude/skills/trend-spotter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trend-spotter", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/aaron-he-zhu/aaron-marketing-skills/tree/main/influencer/scout/trend-spotterType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add aaron-he-zhu/aaron-marketing-skills --skill trend-spotter -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aaron-he-zhu/aaron-marketing-skills trend-spotter --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aaron-he-zhu/aaron-marketing-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/influencer/scout/trend-spotter .agents/skills/trend-spotter && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "trend-spotter" agent skill from https://github.com/aaron-he-zhu/aaron-marketing-skills/tree/main/influencer/scout/trend-spotter into .agents/skills/trend-spotter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trend-spotter", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aaron-he-zhu/aaron-marketing-skills --skill trend-spotter -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aaron-he-zhu/aaron-marketing-skills trend-spotter --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aaron-he-zhu/aaron-marketing-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/influencer/scout/trend-spotter .cursor/skills/trend-spotter && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "trend-spotter" agent skill from https://github.com/aaron-he-zhu/aaron-marketing-skills/tree/main/influencer/scout/trend-spotter into .cursor/skills/trend-spotter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trend-spotter", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/aaron-he-zhu/aaron-marketing-skills.git --path influencer/scout/trend-spotter--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add aaron-he-zhu/aaron-marketing-skills --skill trend-spotter -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aaron-he-zhu/aaron-marketing-skills trend-spotter --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aaron-he-zhu/aaron-marketing-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/influencer/scout/trend-spotter .gemini/skills/trend-spotter && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "trend-spotter" agent skill from https://github.com/aaron-he-zhu/aaron-marketing-skills/tree/main/influencer/scout/trend-spotter into .gemini/skills/trend-spotter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trend-spotter", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install aaron-he-zhu/aaron-marketing-skills trend-spotterInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add aaron-he-zhu/aaron-marketing-skills --skill trend-spotter -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aaron-he-zhu/aaron-marketing-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/influencer/scout/trend-spotter .github/skills/trend-spotter && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "trend-spotter" agent skill from https://github.com/aaron-he-zhu/aaron-marketing-skills/tree/main/influencer/scout/trend-spotter into .github/skills/trend-spotter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trend-spotter", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aaron-he-zhu/aaron-marketing-skills --skill trend-spotter -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aaron-he-zhu/aaron-marketing-skills trend-spotter --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aaron-he-zhu/aaron-marketing-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/influencer/scout/trend-spotter .opencode/skills/trend-spotter && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "trend-spotter" agent skill from https://github.com/aaron-he-zhu/aaron-marketing-skills/tree/main/influencer/scout/trend-spotter into .opencode/skills/trend-spotter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trend-spotter", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
trend-spotter- GitHub stars
- 2.9k
- Token cost
- ~2.7k tokens
- SKILL.md length
- 1,064 words
- Files
- 3 (incl. references)
- Skills in repo
- 119
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when the user asks to "find trending topics", "what trends should my brand jump on", or "time a campaign around a cultural moment"; produces a ranked trend report with…
- Works in 3 steps: Every named current trend,… → Each candidate with complete current… → The report names the top 3 trends, watch…
- The user asks to find trending topics
- SKILL.md covers Quick Start, Skill Contract, Data Sources and Instructions, plus 3 more sections
- Calls python3; reaches hn.algolia.com
What it does
Trend Spotter is an agent skill from aaron-he-zhu/aaron-marketing-skills. Use when the user asks to "find trending topics", "what trends should my brand jump on", or "time a campaign around a cultural moment"; produces a ranked trend report with brand-fit scores, format calls (rising/peak/declining), a cultural calendar, and go/skip recommendations. Not for finding the creators to run those trends — use influencer-discovery; not for building the brand posting calendar from a go verdict — use social-calendar-builder. 热点趋势洞察/借势营销
Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/templates.md` and `references/trend-scout-recipe.md`). Compatibility notes: Claude Code and compatible agent-skill hosts
It sits in Marketing & SEO, covering Influencer and creator marketing and Social media marketing. The repository describes itself as: 120 marketing skills as an AI marketing staff — plugin, portable skills, or an 8-bot team across 7 disciplines (narrative, SEO/GEO, social, email, paid, influencer, launch) on… The licence is Apache-2.0.
When your agent uses it
- The user asks to find trending topics
- What trends should my brand jump on
- Time a campaign around a cultural moment
- Produces a ranked trend report with brand-fit scores
Example prompts
- “find trending topics”
- “what trends should my brand jump on”
- “time a campaign around a cultural moment”
- “/trend-spotter”
Requirements
- Python 3
- Compatibility (from SKILL.md): Claude Code and compatible agent-skill hosts
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Every named current trend, volume/growth/status claim, cultural moment, and competitor-adoption claim has a dated source ref plus the…
- Each candidate with complete current evidence for that exact scope has a brand-fit score and a go / caution / skip call; RSS/title overlap…
- The report names the top 3 trends, watch list, and avoid list only when current evidence supports them; otherwise it returns NEEDS_INPUT…
What it can do on your machine
Read from SKILL.md and the folder at commit d5529cb. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
hn.algolia.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Claude Code and compatible agent-skill hosts
From compatibility in the SKILL.md frontmatter.
Context cost
Trend Spotter loads about 2.7k tokens when it runs, and up to ~6.7k if it reads all its reference files. Until then it costs about 118 tokens; SKILL.md has 1,064 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from aaron-he-zhu/aaron-marketing-skills at commit d5529cb, republished under its Apache-2.0 licence (© aaron-he-zhu). 1,064 words, ~2,662 tokens.
Download SKILL.mdSave it as
.claude/skills/trend-spotter/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- trend-spotter
- description
- Use when the user asks to "find trending topics", "what trends should my brand jump on", or "time a campaign around a cultural moment"; produces a ranked trend report with brand-fit scores, format calls (rising/peak/declining), a cultural calendar, and go/skip recommendations. Not for finding the creators to run those trends — use influencer-discovery; not for building the brand posting calendar from a go verdict — use social-calendar-builder. 热点趋势洞察/借势营销
- compatibility
- Claude Code and compatible agent-skill hosts
- slug
- trend-spotter
- displayName
- Trend Spotter · 趋势侦察
- summary
- 排名化趋势报告:品牌契合评分、rising/peak/declining 判断与 go/skip 建议
- version
- 20.1.0
- license
- Apache-2.0
- homepage
- https://github.com/aaron-he-zhu/aaron-marketing-skills
- when_to_use
- Use when planning campaign timing and themes, deciding whether to join a hashtag, sound, or challenge, scouting trending content formats on a platform…
- argument-hint
- <brand or industry> [platform] [time horizon]
- metadata.author
- aaron-he-zhu
- metadata.version
- 20.1.0
Trend Spotter
This skill helps you identify and capitalize on trends that matter to your audience. It monitors social conversations, emerging topics, viral content formats, and cultural moments to inform influencer campaign timing and content strategy.
Quick Start
Shortest invocation:
What trends are relevant for [brand/industry] right now?Common scenario — analyze one specific trend before committing:
Should [brand] participate in [trend/challenge]? Score the brand fit and give a go/skip call.Skill Contract
- Reads: brand/industry, target platforms, audience, geographic focus, time horizon, content categories; prior audience and niche findings from
memory/influencer/if present. - Writes: return the trend report inline by default; save it to
memory/influencer/trend-spotter/YYYY-MM-DD-<topic>.mdonly with exact authorization for that WARM path. - Promotes: only with separate exact authorization, promote durable facts (top trends to act on now, trends to avoid, next review date) to
memory/hot-cache.md. - Done when:
- Every named current trend, volume/growth/status claim, cultural moment, and competitor-adoption claim has a dated source ref plus the requested platform, geography, observation window, metric definition, and momentum comparison.
- Each candidate with complete current evidence for that exact scope has a brand-fit score and a go / caution / skip call; RSS/title overlap alone remains a
Proxy candidatewithscore_state: NOT_SCORED. - The report names the top 3 trends, watch list, and avoid list only when current evidence supports them; otherwise it returns
NEEDS_INPUTwith an exact query/collection plan.
- Primary next skill: influencer-discovery — find the creators who can execute the chosen trends.
Handoff Summary
Emit the standard shape from skill-contract.md §Handoff Summary Format.
Data Sources
The intake and query plan work with no live integration. A report about what is current does not: it requires dated user-supplied evidence, a public fetch, or a live connector result for the requested platform, geography, and horizon. Brand inputs alone support search terms and evaluation criteria, not trend names, counts, growth, rising/peak/declining calls, or go/skip recommendations. Without current evidence, return NEEDS_INPUT and the exact queries/fields to collect. Where a tool supplies the read, use a ~~ connector placeholder:
~~social platform analytics— trending hashtags, sounds, and view counts per platform.~~trend database— emerging topics, challenge participation, and growth rates.~~social listening— cultural conversations and sentiment around a topic.~~competitor tracking— which trends rival brands have adopted and how they performed.
No connector is required to produce a useful query plan. A named current-trend report requires the source records above. See CONNECTORS.md for the free/keyless recipe per category.
For a keyless way to discover topics worth measuring, run the multi-source candidate scout — Google Trends RSS + Hacker News + Reddit + YouTube upload titles via the bundled stdlib rss_monitor.py (no new dependency): references/trend-scout-recipe.md. RSS/title overlap is only a Proxy candidate and stays NOT_SCORED; it does not establish a platform trend, view-count outlier, lifecycle state, or act-now recommendation. This is the Tier-1 candidate recipe behind ~~trend database (Google Trends RSS).
Keyless news pulse (Tavily): python3 "${CLAUDE_PLUGIN_ROOT}/scripts/connectors/tavily.py" search "<vertical or candidate trend>" --topic news --time-range w --limit 10 adds recency-filtered discovery refs. Agreement with an RSS title may raise query priority, but it remains a Proxy candidate/NOT_SCORED; news overlap does not prove momentum on TikTok, Reels, YouTube, or another requested platform.
Keyless source-specific sharpeners: python3 "${CLAUDE_PLUGIN_ROOT}/scripts/connectors/pageviews.py" "<Topic_Article>" --granularity daily --days 30 measures Wikipedia page attention, and the Hacker News Algolia API (https://hn.algolia.com/api/v1/search?query=<topic>, keyless) measures HN points/comments. Those values are Measured only for their named source and window. Treat them as Proxy for a different requested platform; require dated momentum from the exact platform/geography/window before any rising / peak / declining or act-now call.
Show full SKILL.md (511 more words)Show less
Instructions
When a user requests trend analysis, run these steps. Each step has a fill-in template in references/templates.md — copy the matching block and populate it.
- Define trend parameters — capture brand/industry, platforms, audience, geographic focus, time horizon, and content categories. (Template: Step 1.)
- Qualify current evidence — for every candidate topic, hashtag, audio, challenge, format, cultural moment, and competitor observation, retain source ref, observed/retrieved date, measurement window, platform/geography, metric definition, current value, and comparable prior value. RSS/title overlap alone stays
Proxy candidate/NOT_SCORED. Missing current evidence stops factual output and yields the query plan. (Template: Step 2.) - Analyze content format trends — list rising/peak/declining formats only from a dated momentum series for the exact requested platform/geography/window; label explanations as observed association or hypothesis, never unsupported causation. (Template: Step 3.)
- Track cultural moments — source dates and current conversation/sentiment claims; otherwise return calendar/search fields as
TBD. (Template: Step 4.) - Assess trend relevance — score only evidence-backed candidates on audience alignment, brand value fit, content adaptability, risk, and timing (X/25). Unsupported candidates remain
NOT_SCOREDwith no go/caution/skip call. (Template: Step 5.) - Monitor competitor trend adoption — require dated post/campaign evidence; do not infer adoption, performance, gaps, or overuse from general brand knowledge. (Template: Step 6.)
- Generate the trend report — fill top-3-act-now, watch, avoid, timed action, format, and hashtag blocks only for candidates that pass the complete current-evidence gate for the exact platform/geography/window; otherwise leave those blocks
TBDand returnNEEDS_INPUTwith the collection plan. Return it inline; offer the exact WARM save path, then ask separately before any HOT promotion. (Template: Step 7.)
For repeatable monitoring, return any proposed ledger write as an inline plan first. Do not run ledger.py record until the user gives a separate exact authorization naming the normalized ledger path, the record operation, and the exact source/topic/platform/geography/window scope. Report-save or HOT-promotion authorization never covers that write.
Example
User: "What TikTok trends should a fitness brand run right now?"
Output is NEEDS_INPUT because the prompt supplies no dated TikTok evidence. It returns platform/geography/window-specific queries for topic, hashtag, sound, format, safety, and competitor-adoption records, plus the fields source_ref, observed_at, and measurement_window. It names no trend, count, status, hashtag, format winner, or this-week action until those records arrive. Full version: references/templates.md.
Reference Materials
references/templates.md — fill-in templates for every step, the extended worked example, and execution tips.
skill-contract.md — shared contract and Handoff Summary format.
state-model.md — HOT/WARM/COLD memory tiers and save paths.
CONNECTORS.md — free/keyless data recipe per connector category.
STAR benchmark scoring at references/star-benchmark.md — for grading trend-driven creative output downstream.
Siblings in the scout phase: audience-mapper, influencer-discovery, fit-scorer.
Next Best Skill
- Primary: influencer-discovery — turn the chosen trends into a shortlist of creators who can execute them.
- Alternate: audience-mapper — confirm which trends actually resonate with your audience before committing.
- Alternate: fit-scorer — score which creators fit the chosen trends and the brand before committing.
Termination: keep a visited-set of skills invoked this session. If the primary next skill was already run this turn, stop and report the chain complete rather than re-invoking. Max handoff depth is 3; once reached, summarize and return control to the user.
© aaron-he-zhu, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in influencer/scout/trend-spotter of aaron-he-zhu/aaron-marketing-skills.
- SKILL.md
- references/templates.md
- references/trend-scout-recipe.md
Open the folder on GitHubat commit d5529cb
Compare with similar skills
Trend Spotter next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Trend Spotter this skillaaron-he-zhu/aaron-marketing-skills | 2.9k | — | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| Threads Profile Searchbrowser-act/skills | 6.1k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Xiaohongshu User Profilebrowser-act/skills | 6.1k | — | ~2k | Automated safety check: Pass | MIT | |
| Ecommerce Social Media Marketingnexscope-ai/eCommerce-Skills | 1.1k | — | ~4.8k | Automated safety check: Pass | MIT | |
| Paw Mkt Socialpawbytes/skill-suites | 113 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Interactive Contentsocial-media-skills/skills | 134 | — | ~2k | Automated safety check: Pass | MIT |
Similar skills
Xiaohongshu User Profile
browser-act/skills
Fetch Xiaohongshu (RedNote / xhs) user profile information and their published notes list by user ID, returning nickname, bio, follower/following counts, engagement totals, tags, and paginated notes…
Ecommerce Social Media Marketing
nexscope-ai/eCommerce-Skills
Social media marketing strategy for ecommerce brands. An agent skill from nexscope-ai/eCommerce-Skills.
Paw Mkt Social
pawbytes/skill-suites
Organic social media strategy and content creation. An agent skill from pawbytes/skill-suites.
Interactive Content
social-media-skills/skills
The participation content format — polls, quizzes, Q&A / scoped AMAs, this-or-that, emoji sliders, question boxes, caption-this, Add-Yours, and challenges.
Twitter Intelligence
sandbaseai/sandbase-skills
Search tweets, analyze trends, monitor users, and gather social intelligence from Twitter/X through SandBase.
More from aaron-he-zhu/aaron-marketing-skills
All 119 skills in this repoAd Account Auditor
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when auditing a paid ad account for incremental contribution, wasted spend, or measurement integrity before scaling; runs a typed 20-item ROAS profile with verified vetoes…
Ad Creative Builder
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "write ad copy", "generate RSA headlines", or "build ad creative at volume"; produces ad units — RSA headlines/descriptions, hooks, and an angle matrix…
Ad Test Designer
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "design an A/B test", "set up a creative/landing test", "run an incrementality test", or "is this result statistically and practically material?"…
Bid Strategy Planner
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "pick a bid strategy", "set a tCPA/tROAS target", or "plan the learning-phase entry"; produces a bid-strategy choice (tCPA / tROAS / max-conversions /…
Conversion Signal QA
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "QA my conversion tracking before launch", "check my UTMs / pixel / event firing", "set up a tracking pre-flight", or "set the dedup rule so Meta and…
Creator Registry
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks "what did we pay this creator last time" or to "update the creator roster"; curates creator identity, rate, rights, exclusivity, compliance-event, and…
Related
Categories
Questions about Trend Spotter
What does Trend Spotter do?
A skill your agent uses when the user asks to "find trending topics", "what trends should my brand jump on", or "time a campaign around a cultural moment"; produces a ranked trend report with…. Trend Spotter is an agent skill from aaron-he-zhu/aaron-marketing-skills. Use when the user asks to "find trending topics", "what trends should my brand jump on", or "time a campaign around a cultural moment"; produces a ranked trend report with brand-fit scores, format calls (rising/peak/declining), a cultural calendar, and go/skip recommendations.
When should I use Trend Spotter?
Trend Spotter fits situations like: the user asks to find trending topics; what trends should my brand jump on; time a campaign around a cultural moment; produces a ranked trend report with brand-fit scores.
How do I install Trend Spotter in Claude Code?
Run `npx skills add aaron-he-zhu/aaron-marketing-skills --skill trend-spotter -a claude-code`. Or copy the skill folder (influencer/scout/trend-spotter in aaron-he-zhu/aaron-marketing-skills) into .claude/skills/trend-spotter in your project. Claude Code loads it when a task matches its description.
How do I install Trend Spotter in Codex?
Run `npx skills add aaron-he-zhu/aaron-marketing-skills --skill trend-spotter -a codex`. Or copy the skill folder (influencer/scout/trend-spotter in aaron-he-zhu/aaron-marketing-skills) into .agents/skills/trend-spotter in your project. Codex loads it when a task matches its description.
Can I use Trend Spotter in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aaron-he-zhu/aaron-marketing-skills --skill trend-spotter -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/trend-spotter, .gemini/skills/trend-spotter, .github/skills/trend-spotter and .opencode/skills/trend-spotter in your project.
What does Trend Spotter need to run?
Going by SKILL.md and its folder, Trend Spotter needs the command-line tools its instructions call (python3). Our summary lists: Python 3. Compatibility (from SKILL.md): Claude Code and compatible agent-skill hosts.
Does Trend Spotter access the network?
SKILL.md names 1 domain. In commands or code: hn.algolia.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Trend Spotter safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Trend Spotter use?
Trend Spotter is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Trend Spotter use?
About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.1k tokens, read only when the agent opens those files.
What are the alternatives to Trend Spotter?
Skills that share tags, products or a category with Trend Spotter: Threads Profile Search (browser-act/skills, 6.1k stars), Xiaohongshu User Profile (browser-act/skills, 6.1k stars), Ecommerce Social Media Marketing (nexscope-ai/eCommerce-Skills, 1.1k stars) and Paw Mkt Social (pawbytes/skill-suites, 113 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Trend Spotter?
aaron-he-zhu (a GitHub user) maintains it in aaron-he-zhu/aaron-marketing-skills, which has 2,898 GitHub stars. The repository holds 119 skills in this directory. The repository was last updated on October 11, 2026.
Source: aaron-he-zhu/aaron-marketing-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.