CtrlK
BlogDocsLog inGet started
Tessl Logo

trend-spotter

Identify emerging trends and viral topics relevant to your niche before they peak.

58

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./apps/desktop/electron/default-skills/trend-spotter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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, lean instruction skill with concrete signal criteria, a clear workflow, and a specific output format; it earns top progressive-disclosure marks as a compact single-purpose skill. The main gaps are the absence of an explicit validation/self-check loop and a worked example.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence without explaining what a hashtag or trend is, with only minor rhetorical framing ("Think like an editor with a finger on the pulse") that could be trimmed, placing it just below fully lean.

4 / 5

Actionability

It gives concrete, specific guidance—defined signal criteria (velocity, cross-surface, relevance, runway), a four-step approach, and a fielded output format—so an instruction-only skill is mostly executable, though no worked example of a real trend is provided.

4 / 5

Workflow Clarity

The four-step "How to approach it" sequence is clearly ordered and the skill is non-destructive analysis, so the destructive-operation validation cap does not apply; it sits below 5 only because there is no explicit validation/feedback loop.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, has no external bundle files, and is organized into well-signaled sections (When to use, What a real signal looks like, How to approach it, Output format), matching the simple-skill exception for a top score.

5 / 5

Total

17

/

20

Passed

Description

53%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 names a clear niche and a concrete action but lacks an explicit "Use when…" trigger clause and comprehensive trigger-term coverage, which together cap its strongest-weighted dimensions at 3. It is distinct from sibling skills but would benefit from explicit trigger guidance.

Suggestions

Add an explicit "Use when…" clause naming concrete trigger phrases (e.g. "Use when the user wants to find what's trending in their niche, spot rising hashtags, or catch a topic before it peaks").

Broaden trigger-term coverage with natural synonyms like "trending", "what's trending", and "rising hashtags" so the description matches how users actually phrase the request.

List one or two more concrete actions (e.g. "rank trending topics by runway and velocity") to lift specificity from a single verb toward comprehensive coverage.

DimensionReasoningScore

Specificity

The phrase "Identify emerging trends and viral topics relevant to your niche" names the domain and one concrete action ("Identify"), matching the anchor for naming a domain with 1-2 concrete actions but not comprehensive coverage.

3 / 5

Completeness

It clearly states what the skill does but has no "Use when…" clause or equivalent explicit trigger guidance, so per the rubric guideline completeness is capped at 3 even though the "what" is clear.

3 / 5

Trigger Term Quality

"emerging trends", "viral topics", and "niche" are natural terms a user might say, but common variations like "trending", "what's trending", or "hashtags" are missing, so coverage is partial rather than comprehensive.

3 / 5

Distinctiveness Conflict Risk

Trend-spotting is a clear niche distinguishable from general research or ideation, but without explicit distinct trigger phrases the overlap risk with related research/ideation skills is only minor, not minimal.

4 / 5

Total

13

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
holaboss-ai/holaOS
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.