trend-spotter

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. 热点趋势洞察/借势营销

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable skill body with a clear sequenced workflow and properly分层 references. Its only weakness is token efficiency: a duplicated worked example and dense connector-command prose that could be consolidated into the recipe reference.

Suggestions

Remove the inline TikTok fitness example from SKILL.md and keep only the pointer to references/templates.md#extended-example to avoid duplicating the same worked example in two places.

Collapse the three keyless-connector command paragraphs (Tavily, pageviews, HN Algolia) into a one-line summary in SKILL.md, moving the full command details into references/trend-scout-recipe.md.

Tighten the Data Sources section by listing the four `~~` connector placeholders as a single compact table rather than four bulleted lines plus surrounding prose.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but carries redundancy — the TikTok fitness example is duplicated in references/templates.md, and the Data Sources section runs long with multiple keyless-connector command paragraphs (Tavily, pageviews, HN Algolia) that could be collapsed or moved to the recipe reference.	2 / 3
Actionability	It gives executable commands (rss_monitor.py, tavily.py, pageviews.py invocations), concrete save paths, a per-step template mapping, and a defined X/25 scoring rubric — copy-paste ready guidance.	3 / 3
Workflow Clarity	Seven steps are clearly sequenced, each tied to a fill-in template, with a "Done when" checklist and a per-trend go/caution/skip scoring gate that functions as a validation checkpoint before the report is finalized.	3 / 3
Progressive Disclosure	SKILL.md is a concise overview pointing one level deep to real, clearly signaled references (references/templates.md and references/trend-scout-recipe.md both exist), with shared contracts linked separately — easy to navigate.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that names concrete deliverables, gives natural trigger phrasing, and explicitly disambiguates from neighboring skills. Every dimension lands at the top of the scale.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — "produces a ranked trend report with brand-fit scores, format calls (rising/peak/declining), a cultural calendar, and go/skip recommendations" — matching the score-3 anchor for several specific concrete actions.	3 / 3
Completeness	It opens with an explicit "Use when..." trigger clause and follows with a clear statement of what it produces, satisfying both the 'what' and 'when' requirements.	3 / 3
Trigger Term Quality	It quotes natural user phrases ("find trending topics", "what trends should my brand jump on", "time a campaign around a cultural moment") giving good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	It carves out a clear niche and explicitly differentiates from sibling skills ("Not for finding the creators... use influencer-discovery"; "not for building the brand posting calendar... use social-calendar-builder"), making wrong-skill triggering unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

75%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 13 suspicious	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	12 / 16 Passed

Repository: aaron-he-zhu/aaron-marketing-skills
Path: influencer/scout/trend-spotter/SKILL.md
Commit: 4a77c48

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.