CtrlK
BlogDocsLog inGet started
Tessl Logo

apify-trend-analysis

Discover and track emerging trends across Google Trends, Instagram, Facebook, YouTube, and TikTok to inform content strategy.

52

Quality

57%

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 ./skills/apify-trend-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The body is highly actionable with concrete commands and a useful Actor selection table, and its workflow is well sequenced. It loses points for generic boilerplate sections, missing validation checkpoints in a batch workflow, and a monolithic structure with no reference split.

Suggestions

Add an explicit validation checkpoint between Step 4 and Step 5 (e.g., check the run status; if FAILED, follow Error Handling before summarizing) to close the feedback loop for batch operations.

Remove or replace the generic 'When to Use' and 'Limitations' boilerplate with skill-specific guidance that earns its tokens.

Move the 19-row Actor selection table into a references file (e.g. references/actors.md) and keep SKILL.md as a concise overview pointing to it, improving progressive disclosure.

DimensionReasoningScore

Conciseness

The core table, step commands, and code blocks are efficient, but the generic 'When to Use' ('Use this skill when tackling tasks related to its primary domain...') and boilerplate 'Limitations' sections add no skill-specific value and could be trimmed.

2 / 3

Actionability

Provides concrete, copy-paste-ready mcpc and node commands with clearly marked placeholders (ACTOR_ID, JSON_INPUT) plus a specific Actor-ID selection table and three output-format variants, matching the fully-executable anchor.

3 / 3

Workflow Clarity

The 5-step sequence with checklist is clear, but these batch scraping operations lack an explicit validation/verification checkpoint integrated into the flow; error handling is reactive and listed separately, capping the score at 2 per the rubric's batch-operation note.

2 / 3

Progressive Disclosure

Sections are well organized and dynamic schema fetching via mcpc is a good disclosure pattern, but the file is a monolithic >50-line document with a large 19-row inline Actor table and no separate reference files (bundle directories references/scripts/assets are absent).

2 / 3

Total

9

/

12

Passed

Description

50%

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 specific about domain and platforms but stops short of providing explicit trigger guidance or a comprehensive action list. It answers 'what' clearly while leaving 'when to use it' only implied.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when researching trending topics, hashtags, or viral content on Google Trends, Instagram, Facebook, YouTube, or TikTok.'

Broaden trigger-term coverage with words users actually say such as 'hashtags', 'viral', 'trending sounds', and 'trend research'.

Expand the action verbs beyond 'Discover and track' to concrete operations like 'scrape hashtag posts', 'pull trend metrics', and 'export trend data'.

DimensionReasoningScore

Specificity

Names the domain (Google Trends, Instagram, Facebook, YouTube, TikTok) and two actions ('Discover and track'), but does not list a comprehensive set of distinct concrete actions as the anchor-3 example does.

2 / 3

Completeness

It clearly states what the skill does, but offers no explicit 'when'/'Use when' trigger guidance, which the rubric guidelines cap at 2.

2 / 3

Trigger Term Quality

Platform names like 'Google Trends', 'Instagram', and 'TikTok' are natural terms users say, but there is no 'Use when' clause and common variations such as 'hashtags', 'viral', or 'trending' are absent.

2 / 3

Distinctiveness Conflict Risk

The trend-analysis niche across named platforms is fairly specific, but 'content strategy' framing and the lack of explicit trigger phrasing leave room for overlap with generic content/marketing skills.

2 / 3

Total

8

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
sickn33/antigravity-awesome-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.