apify-content-analytics

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

Quality

68%

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 ./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 well-structured and actionable with concrete, executable commands and a clear five-step workflow, but a batch operation lacks validation checkpoints and the referenced run_actor.js script is missing from the bundle. Adding a verification step and shipping the referenced script (or splitting the Actor table into a reference file) would raise the lower scores.

Suggestions

Add an explicit validation checkpoint after Step 4, e.g. verify the output file is non-empty and contains expected fields before summarizing in Step 5.

Provide at least one concrete --input JSON example (e.g. a minimal post-URL or hashtag input) so the command templates are fully copy-paste ready.

Ship the referenced reference/scripts/run_actor.js in the scripts/ bundle, or move the 17-row Actor-selection table into a references/ file and link to it.

Dimension	Reasoning	Score
Conciseness	The body is lean, with compact tables and bare executable commands and no padding of concepts Claude already knows; minor loose spots like the vague 'Based on character of use case' and a slightly redundant intro keep it from a 5.	4 / 5
Actionability	Provides three copy-paste-ready command templates (quick/CSV/JSON) plus a real mcpc schema-fetch command and an Actor-selection table, but never shows a concrete --input example and the referenced run_actor.js is not present in the bundle.	4 / 5
Workflow Clarity	Five steps are clearly sequenced with a copy-paste checklist, but this batch data-collection workflow has no explicit validation/verification checkpoint before summarizing, which caps workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	Section headers give decent structure, but the referenced ${CLAUDE_PLUGIN_ROOT}/reference/scripts/run_actor.js is not present in the empty scripts/ bundle, and the large 17-row Actor table is inlined rather than split into a reference file.	3 / 5
	Total	14 / 20 Passed

Description

71%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 well-targeted with concrete actions and platform names, but it lacks an explicit 'when to use' trigger clause, which limits its completeness score. Adding a 'Use when...' sentence with natural synonyms like 'analytics' or 'social media stats' would lift both completeness and trigger term quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks for social media analytics, content performance, or ROI across Instagram, Facebook, YouTube, or TikTok.'

Add natural synonyms users say, such as 'analytics', 'social media stats', and platform-specific terms like 'reels', 'shorts', or 'ads'.

Tighten distinctiveness by naming the data source (Apify Actors) so the description clearly differentiates from generic analytics skills.

Dimension	Reasoning	Score
Specificity	Lists three concrete actions ('Track engagement metrics', 'measure campaign ROI', 'analyze content performance') across four named platforms, giving comprehensive coverage of the domain.	5 / 5
Completeness	The 'what' is clear and specific, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Includes natural terms like 'engagement metrics', 'campaign ROI', 'content performance' and four platform names, but misses common synonyms such as 'analytics', 'social media stats', or file extensions.	4 / 5
Distinctiveness Conflict Risk	The four named platforms and content-analytics focus carve a clear niche, though broad phrasing like 'content performance' leaves minor overlap risk with general analytics skills.	4 / 5
	Total	16 / 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: sickn33/antigravity-awesome-skills
Path: skills/apify-content-analytics/SKILL.md
Commit: 1f67c44

Reviewed: about 16 hours 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.