CtrlK
BlogDocsLog inGet started
Tessl Logo

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

70

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

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

The body is a well-structured, evidence-gated workflow with concrete connector commands and clean progressive disclosure of detail into references. The main opportunities are trimming the repeated Proxy/NOT_SCORED guardrail and surfacing a worked success example inline rather than only the NEEDS_INPUT case.

Suggestions

State the Proxy candidate / NOT_SCORED rule once authoritatively and reference it from later steps instead of restating it in Data Sources, each Instruction step, and the Example.

Add a brief inline worked success snippet (one scored candidate with a go call) so the common happy path is visible without opening references/templates.md.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — no padding about what trends or platforms are — but the Proxy candidate / NOT_SCORED gate is restated across Data Sources, Instructions, and the example, which is minor redundancy that could be tightened.

4 / 5

Actionability

Provides copy-paste connector commands (tavily.py, pageviews.py), the HN Algolia API URL, exact save paths, and explicit field lists, but the inline Example demonstrates only the NEEDS_INPUT path with the full worked success case living one level deep in references.

4 / 5

Workflow Clarity

A 7-step numbered sequence with explicit validation gates (current-evidence gate), a NEEDS_INPUT feedback loop for error recovery, a 'Done when' checklist, and separate-authorization gating before ledger writes.

5 / 5

Progressive Disclosure

SKILL.md is a lean overview pointing one level deep to references/templates.md (the long scaffolds) and references/trend-scout-recipe.md (the keyless recipe), with clearly signaled links and easy navigation.

5 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

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

The description is strong across the board: concrete outputs, explicit trigger phrasings, and clear scope boundaries against sibling skills. The only gap is a few natural trigger synonyms (hashtag, viral, challenge) not appearing in the trigger clause.

Suggestions

Add one or two natural trigger variants such as 'jump on a hashtag' or 'ride a viral moment' to broaden trigger-term coverage.

Consider naming the platforms (TikTok, Reels, YouTube) in the description so platform-specific trend requests clearly match.

DimensionReasoningScore

Specificity

Names multiple concrete outputs — 'ranked trend report with brand-fit scores, format calls (rising/peak/declining), a cultural calendar, and go/skip recommendations' — giving comprehensive coverage of what the skill produces.

5 / 5

Completeness

Explicitly answers both 'what' (the ranked report and its components) and 'when' (a 'Use when the user asks to...' clause with concrete trigger phrases), matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural user phrasings ('find trending topics', 'what trends should my brand jump on', 'time a campaign around a cultural moment'), but common synonyms a user might say — hashtag, viral, challenge — are absent from the trigger clauses.

4 / 5

Distinctiveness Conflict Risk

Explicit boundary guidance — 'Not for finding the creators... use influencer-discovery; not for building the brand posting calendar... use social-calendar-builder' — carves a clear niche with minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

75%

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

Validation12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.