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.

46

Quality

48%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/apify-trend-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

64%Scale 1-3

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

This skill provides solid actionable guidance with executable commands and a clear multi-step workflow, but suffers from some verbosity (the large inline Actor table, the vacuous 'When to Use' section) and lacks validation checkpoints between running the Actor and summarizing results. The error handling section is practical but could be more structured.

Suggestions

Move the Actor lookup table to a separate reference file (e.g., ACTORS.md) and link to it from the main skill, keeping only 2-3 common examples inline.

Add a validation step between Step 4 and Step 5: check the script exit code, verify output file exists and is non-empty, and include a retry/fix loop for failed runs.

Remove the 'When to Use' section entirely — it adds no information beyond what the skill title and description already convey.

Trim Step 5 (Summarize Findings) to a single line — Claude already knows how to summarize data without being told to report 'number of results found' and 'key trend insights'.

DimensionReasoningScore

Conciseness

The large Actor lookup table is useful reference but could be externalized. The 'When to Use' section is vacuous filler. Some sections like Step 3 and Step 5 contain obvious guidance Claude doesn't need spelled out. Overall moderately efficient but with clear trimming opportunities.

2 / 3

Actionability

Provides fully executable bash commands with concrete flags, specific Actor IDs, and copy-paste ready script invocations. The mcpc command for fetching schemas is specific and complete. Error handling maps specific error messages to concrete fixes.

3 / 3

Workflow Clarity

The 5-step workflow is clearly sequenced with a progress checklist, which is good. However, there are no validation checkpoints — no step to verify the Actor run succeeded before summarizing, no feedback loop for retrying failed runs, and no verification that the output file was correctly written.

2 / 3

Progressive Disclosure

The skill references external scripts (`run_actor.js`) appropriately, but the massive 20-row Actor lookup table should be in a separate reference file. The content is reasonably structured with clear sections but the inline table makes the main file heavier than necessary.

2 / 3

Total

9

/

12

Passed

Description

32%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.

The description identifies a clear domain (social media trend tracking) and names specific platforms, which provides reasonable distinctiveness. However, it lacks a 'Use when...' clause, which significantly hurts completeness, and the actions described are high-level rather than concrete. Adding explicit trigger conditions and more specific capabilities would substantially improve this description.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about trending topics, viral content, social media trends, or wants to research what's popular on social platforms.'

Make capabilities more concrete by specifying actions like 'analyze keyword popularity over time, compare trend volumes across platforms, identify rising hashtags, and generate trend reports.'

Include natural user trigger terms like 'trending', 'viral', 'what's popular', 'hashtag trends', 'social media analytics' to improve keyword coverage.

DimensionReasoningScore

Specificity

Names the domain (trend tracking) and lists specific platforms (Google Trends, Instagram, Facebook, YouTube, TikTok), but the actions are somewhat vague — 'discover and track emerging trends' and 'inform content strategy' lack concrete specifics about what operations are performed (e.g., generate reports, compare keywords, export data).

2 / 3

Completeness

Describes what the skill does (discover and track trends across platforms) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'when' is not even implied strongly enough to warrant a 2.

1 / 3

Trigger Term Quality

Includes good platform-specific keywords (Google Trends, Instagram, Facebook, YouTube, TikTok) and relevant terms like 'emerging trends' and 'content strategy', but misses common user variations like 'trending topics', 'viral', 'social media trends', 'what's popular', or 'hashtag analysis'.

2 / 3

Distinctiveness Conflict Risk

The combination of multiple specific social media platforms and trend tracking creates some distinctiveness, but 'content strategy' is broad enough to overlap with general social media management or content planning skills. The lack of explicit triggers increases conflict risk.

2 / 3

Total

7

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.