apify-content-analytics
Track engagement metrics, measure campaign ROI, and analyze content performance across Instagram, Facebook, YouTube, and TikTok.
72
66%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/apify-content-analytics/SKILL.mdQuality
Discovery
67%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 strong in specificity and distinctiveness, clearly naming concrete actions and specific platforms that carve out a well-defined niche. However, it lacks an explicit 'Use when...' clause, which limits its completeness score, and could benefit from more natural trigger terms that users would commonly say (e.g., 'social media analytics', 'followers', 'likes').
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about social media analytics, post performance, or marketing campaign results.'
Include more natural user trigger terms such as 'social media', 'social media analytics', 'likes', 'followers', 'views', 'shares', and 'post performance' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Track engagement metrics', 'measure campaign ROI', and 'analyze content performance', along with specific platforms (Instagram, Facebook, YouTube, TikTok). | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific actions and platforms, but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric. | 2 / 3 |
Trigger Term Quality | Includes good platform names and terms like 'engagement metrics', 'campaign ROI', and 'content performance', but misses common user variations like 'social media analytics', 'likes', 'followers', 'views', 'social media', or 'posts'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of social media platforms (Instagram, Facebook, YouTube, TikTok) with engagement/ROI/performance analysis creates a clear niche that is unlikely to conflict with other skills like general analytics or non-social-media marketing tools. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a functional skill with strong actionability—concrete commands, a comprehensive Actor selection table, and clear error handling. Its main weaknesses are the lack of validation checkpoints in the workflow (e.g., verifying Actor run success before summarizing) and the inline bulk of the Actor table and repetitive command variants that could be split into reference files for better progressive disclosure.
Suggestions
Add an explicit validation step after Step 4 (e.g., check exit code or output for errors before proceeding to summarize), and integrate error handling as a feedback loop within the workflow rather than a separate section.
Move the Actor lookup table to a separate reference file (e.g., ACTORS.md) and link to it from the main skill, keeping only a brief summary of platform coverage inline.
Consolidate the three output format command examples into a single template with a note about the optional --output and --format flags, reducing repetition.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy. The large Actor table is useful reference material but could be in a separate file. The three nearly identical command examples for different output formats add bulk that could be condensed. | 2 / 3 |
Actionability | Provides fully executable bash commands with clear placeholders, a comprehensive Actor selection table, and specific error handling guidance. The commands are copy-paste ready with appropriate variable substitution points. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced with a progress checklist, but there are no validation checkpoints between steps. After running the script (Step 4), there's no verification that the run succeeded before proceeding to summarize. The error handling section is separate rather than integrated into the workflow as feedback loops. | 2 / 3 |
Progressive Disclosure | The skill has reasonable structure with clear sections, but the large Actor lookup table (17 rows) and three nearly identical command variants bloat the main file. The Actor table and detailed command variants would be better as referenced files, keeping the SKILL.md as a concise overview. | 2 / 3 |
Total | 9 / 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
b739683
- 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.