apify-brand-reputation-monitoring
Scrape reviews, ratings, and brand mentions from multiple platforms using Apify Actors.
57
66%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/antigravity-awesome-skills-claude/skills/apify-brand-reputation-monitoring/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 concise and specific about what the skill does, naming concrete data types and the tool used. However, it lacks an explicit 'Use when...' clause, which limits Claude's ability to know when to select it, and could benefit from more natural trigger terms and platform examples.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user wants to scrape or collect reviews, ratings, or brand mentions from websites, or mentions Apify.'
Include common user trigger terms and platform examples, e.g., 'web scraping, crawling, Yelp reviews, Amazon ratings, Google Reviews, social media mentions, sentiment data.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'scrape reviews, ratings, and brand mentions from multiple platforms using Apify Actors.' This names the domain (web scraping), the specific data types (reviews, ratings, brand mentions), and the tool (Apify Actors). | 3 / 3 |
Completeness | Clearly answers 'what does this do' (scrape reviews, ratings, brand mentions using Apify Actors), but lacks an explicit 'Use when...' clause or equivalent trigger guidance for when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'reviews', 'ratings', 'brand mentions', 'scrape', and 'Apify Actors', but misses common user variations such as 'sentiment', 'feedback', 'web scraping', 'crawl', or specific platform names (e.g., 'Yelp', 'Amazon', 'Google Reviews'). | 2 / 3 |
Distinctiveness Conflict Risk | The combination of scraping reviews/ratings/brand mentions specifically via Apify Actors creates a clear niche that is unlikely to conflict with other skills. The mention of 'Apify Actors' as the specific tooling makes it highly distinctive. | 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 skill provides solid actionable guidance with executable commands and a comprehensive Actor selection table, making it practical for brand reputation monitoring tasks. Its main weaknesses are the lack of validation/feedback loops in the workflow (especially important since Actor runs can fail) and the somewhat verbose Actor table that could benefit from being in a separate reference file. The boilerplate Limitations section adds little value.
Suggestions
Add a validation step after Step 4 to check if the Actor run succeeded (e.g., check exit code or output) before proceeding to summarization, with a retry loop for failures.
Move the large Actor selection table to a separate reference file (e.g., ACTORS.md) and keep only the most common 4-5 actors inline with a link to the full list.
Remove or significantly trim the generic Limitations section, which contains boilerplate advice Claude already knows.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary content. The massive Actor table (18 rows) could be more concise, and the Limitations section contains generic boilerplate that doesn't add value. The workflow checklist and step structure are well-organized but slightly verbose. | 2 / 3 |
Actionability | The skill provides fully executable bash commands for each step, concrete Actor IDs in the selection table, specific CLI flags and options, and clear error handling with resolutions. Commands are copy-paste ready with clear placeholder substitution. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced with a progress checklist, but lacks validation checkpoints. There's no step to verify the Actor run succeeded before summarizing, no feedback loop for retrying failed runs, and no validation between fetching the schema and constructing the input JSON. | 2 / 3 |
Progressive Disclosure | The skill references scripts at `${CLAUDE_PLUGIN_ROOT}/reference/scripts/run_actor.js` but no bundle files are provided to verify these exist. The Actor table is quite long and could be split into a reference file. The content is structured with clear sections but is somewhat monolithic for its length. | 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
4cc48db
- 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.