apify-audience-analysis

Understand audience demographics, preferences, behavior patterns, and engagement quality across Facebook, Instagram, 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 ./skills/apify-audience-analysis/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.

A compact, actionable skill with good structure and executable commands, weakened by missing validation for batch Actor runs and a referenced script that is absent from the bundle.

Suggestions

Add a validation step between Step 4 (run) and Step 5 (summarize) that checks the run succeeded and output is non-empty before reporting findings.

Either ship the referenced run_actor.js under a references/scripts bundle directory or remove the path reference so it does not point to a missing file.

Show an example JSON_INPUT structure for at least one Actor so the run commands are fully executable without guessing.

Dimension	Reasoning	Score
Conciseness	The body is lean with no over-explanation of concepts Claude knows, relying on an Actor table and tight command snippets; only minor redundancy in the 'Best For' column keeps it from a 5.	4 / 5
Actionability	Provides concrete, copy-paste-ready bash commands with flags and a full Actor-selection table, but placeholders like ACTOR_ID and JSON_INPUT require substitution and the expected JSON input shape is not shown.	4 / 5
Workflow Clarity	The 5-step checklist is clearly sequenced, but the Actor runs are batch operations with no validation checkpoint before summarizing findings, which per the guidelines caps workflow clarity at 3.	3 / 5
Progressive Disclosure	The body is well-sectioned with tables and code, but it references ${CLAUDE_PLUGIN_ROOT}/reference/scripts/run_actor.js while the bundle contains no references/scripts/assets directories, so a referenced file is missing.	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.

A reasonably specific, platform-scoped description that clearly states what it does but omits explicit trigger guidance. It is distinct from generic analytics skills thanks to the named platforms.

Suggestions

Add a 'Use when...' clause naming the trigger scenarios (e.g., 'Use when you need to analyze follower demographics or engagement across Facebook, Instagram, YouTube, or TikTok').

Include natural synonyms like 'followers', 'social media audience', or 'engagement analytics' to broaden trigger coverage.

Mention Apify/scraping in the description to sharpen distinctiveness from general analytics skills.

Dimension	Reasoning	Score
Specificity	Names the domain plus multiple concrete dimensions (demographics, preferences, behavior patterns, engagement quality) across four specific platforms, giving broad coverage though the single verb 'Understand' is generic.	4 / 5
Completeness	Gives a clear, specific 'what' but lacks any explicit 'when'/'Use when' trigger clause, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural user phrases like 'audience demographics', 'engagement', and the four platform names, but omits common synonyms such as 'followers' or 'social media analytics'.	4 / 5
Distinctiveness Conflict Risk	The four named platforms give it a clear niche with low overlap risk, though the description alone does not mention Apify or scraping, leaving minor overlap potential with general analytics skills.	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: sickn33/agentic-awesome-skills
Path: skills/apify-audience-analysis/SKILL.md
Commit: b1aebac

Reviewed: ~18 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.