apify-brand-reputation-monitoring

Scrape reviews, ratings, and brand mentions from multiple platforms using Apify Actors.

Quality

61%

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-brand-reputation-monitoring/SKILL.md

Quality

Content

57%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 body is well-structured with an actionable workflow and concrete commands, but it inlines a large actor table that belongs in a reference, points to a run_actor.js script that is absent from the bundle, and lacks a validation checkpoint before summarizing batch scrape results.

Suggestions

Add an explicit validation step between Step 4 and Step 5: verify the Apify run status is SUCCEEDED and check result count/non-empty output before summarizing.

Move the 19-row actor table into a references file (e.g. references/actors.md) and keep only the selection guidance inline, or confirm and include the referenced reference/scripts/run_actor.js in the bundle.

Tighten vague phrasing like 'Based on character of use case' into concrete guidance (e.g. suggested result counts per use case).

Dimension	Reasoning	Score
Conciseness	Mostly efficient with a tidy checklist and command blocks, but the 19-row actor table is large inline content that could live in a reference, and a few phrases ('Based on character of use case') are padding rather than guidance.	3 / 5
Actionability	Provides concrete, mostly copy-pasteable bash commands for schema fetch and three output variants, with placeholders (ACTOR_ID, JSON_INPUT, YYYY-MM-DD_OUTPUT_FILE) that still require user substitution.	4 / 5
Workflow Clarity	The five steps are sequenced with a progress checklist, but this batch-scraping skill has no validation checkpoint (e.g. verifying the run succeeded before summarizing, checking result count) before reporting, which caps workflow_clarity at 3.	3 / 5
Progressive Disclosure	Structure is sectioned, but the large actor-selection table is inlined in SKILL.md and the body references ${CLAUDE_PLUGIN_ROOT}/reference/scripts/run_actor.js while no references/scripts bundle directory is present, so the referenced detail is not actually available.	3 / 5
	Total	13 / 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 for a well-scoped niche, but it omits an explicit 'Use when...' clause, leaving the invocation trigger only implied. Adding a trigger clause would raise completeness and distinctiveness.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when you need to collect reviews, ratings, or brand mentions across social, travel, or map platforms via Apify Actors.'

Include common synonyms or file/output cues users might say (e.g. 'sentiment', 'scrape reviews from Google Maps', 'export ratings').

Name the concrete output ('exported monitoring results and a reputation summary') to sharpen the 'what'.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Scrape reviews, ratings, and brand mentions') and names the tool ('Apify Actors') and domain ('multiple platforms'), but coverage of the action space is broad rather than exhaustive.	4 / 5
Completeness	It states clearly what the skill does but has no 'Use when...' trigger clause, so the 'when' is only weakly implied and completeness is capped at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	'reviews', 'ratings', and 'brand mentions' are natural terms users would say, though synonyms and platform-specific phrasings are not enumerated.	4 / 5
Distinctiveness Conflict Risk	The Apify-Actor-based reputation-monitoring niche is mostly distinct with minimal overlap risk, though 'brand mentions' could loosely overlap with general social-listening 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/antigravity-awesome-skills
Path: skills/apify-brand-reputation-monitoring/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.