apify-content-analytics

Track engagement metrics, measure campaign ROI, and analyze content performance across Instagram, Facebook, YouTube, and TikTok.

Quality

65%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/apify-content-analytics/SKILL.md

Quality

Content

65%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 content is action-oriented and concisely organized with executable commands, but it lacks a validation checkpoint for its batch scraping workflow and keeps bulk reference material inline while referencing a script absent from the bundle.

Suggestions

Add an explicit validation step between running the actor and summarizing (e.g. verify the output file is non-empty and spot-check a result row before reporting findings).

Move the 16-row actor selection table into a references/ file and link to it, keeping SKILL.md as a concise overview.

Ensure the referenced run_actor.js actually exists at the cited path (reference/scripts/run_actor.js) and is listed in the bundle, or inline its key behavior.

Dimension	Reasoning	Score
Conciseness	The body is efficient — concrete commands, a reference actor table, and a compact error-handling section — with only minor trims needed (e.g. the parenthetical "(No need to check it upfront)" and "Based on character of use case"), so it sits at anchor 4 rather than the fully lean anchor 5.	4 / 5
Actionability	It provides copy-paste-ready bash commands for schema fetch and three output formats with specific Actor IDs and flags, but placeholders like ACTOR_ID and JSON_INPUT plus the absent run_actor.js leave minor gaps below the fully executable anchor 5.	4 / 5
Workflow Clarity	The five steps are clearly sequenced with a progress checklist, but this is a batch scraper operation with no explicit validation checkpoint (e.g. confirm schema fetched, verify non-empty results before summarizing), so per the batch-operation cap workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	Sections are well organized, but the 16-row actor table is bulk inlined content that could live in a reference file, and the referenced script reference/scripts/run_actor.js is not present in the bundle, leaving structure and signaling short of the well-split anchor 4.	3 / 5
	Total	14 / 20 Passed

Description

66%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 specific and uses natural trigger terms with a clear, distinct niche, but it omits an explicit "Use when..." trigger clause, which caps completeness at 3 and limits the overall score.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger situations (e.g. 'Use when the user asks to measure post engagement, track follower growth, or audit campaign ROI on Instagram, Facebook, YouTube, or TikTok.').

Expand the action list slightly to move specificity toward comprehensive coverage (e.g. add 'export results to CSV/JSON', 'compare performance across posts').

Include a few synonyms users might naturally say (e.g. 'social media analytics', 'reach and impressions') to strengthen trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (content analytics across four named platforms) and three concrete actions — "Track engagement metrics", "measure campaign ROI", "analyze content performance" — but does not enumerate the fuller set of analytics actions, so it falls below the comprehensive anchor 5.	4 / 5
Completeness	It clearly states what the skill does but provides no "Use when..." clause or equivalent explicit trigger guidance, so per the judging guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	Natural user-facing terms are present ("engagement metrics", "campaign ROI", "content performance", plus Instagram/Facebook/YouTube/TikTok), giving good keyword coverage, but synonyms and finer-grained variations a user might say are not exhaustively covered.	4 / 5
Distinctiveness Conflict Risk	The four-platform social-content-analytics niche is clearly scoped with distinct triggers, leaving only minor overlap risk with broader social-media or general analytics skills rather than the minimal-conflict profile of anchor 5.	4 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/apify-content-analytics/SKILL.md
Commit: 57c135b

Reviewed: 5 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.