apify-influencer-discovery

Find and evaluate influencers for brand partnerships, verify authenticity, and track collaboration performance across Instagram, Facebook, YouTube, and TikTok.

5.29x

Quality

61%

Does it follow best practices?

Impact

90%

5.29x

Average score across 1 eval scenario

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/apify-influencer-discovery/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 skill is well-structured and actionable with concrete commands and a clear step sequence, but as a batch scraping operation it lacks an explicit validation checkpoint before summarizing results, and its sole script reference points to a bundle file that is not provided.

Suggestions

Add an explicit validation/verification step between running the scraper and summarizing results (e.g., confirm row count and required fields, retry or warn on empty/failed runs).

Include the referenced run_actor.js script in the bundle (reference/scripts/) or document its expected behavior inline so the cited commands are actually executable.

Specify the expected shape of the JSON input per Actor, or link to where users obtain it from the Step 2 schema fetch, to close the actionability gap.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean: a compact Actor-selection table, focused bash snippets, and a short error-handling list, with only minor instances of slack phrasing (e.g., 'Based on character of use case').	4 / 5
Actionability	Provides concrete, executable bash commands for schema fetch and run scripts with clearly labeled placeholder substitution, leaving only minor gaps around the JSON input structure.	4 / 5
Workflow Clarity	Five numbered steps are sequenced with a progress checklist, but this batch operation runs scrapers with no validation/verification checkpoint between data fetch and summarization, which caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Sections are organized and one script reference is signaled, but the referenced path (${CLAUDE_PLUGIN_ROOT}/reference/scripts/run_actor.js) has no corresponding bundle file present, leaving structure only partially realized.	3 / 5
	Total	14 / 20 Passed

Description

58%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 conveys concrete, multi-platform influencer-discovery capabilities with clear niche focus, but it lacks an explicit 'Use when...' trigger clause, which caps its completeness. Adding natural trigger phrases and synonyms would raise the trigger-term and completeness scores.

Suggestions

Append an explicit 'Use when...' clause listing concrete user triggers (e.g., 'Use when discovering influencers for outreach, evaluating creator authenticity, or planning campaigns across social platforms').

Add natural synonyms users might say ("creators", "brand ambassadors", "audience analysis") to broaden trigger-term coverage.

Clarify the 'when' by mentioning common scenarios like campaign planning, outreach shortlisting, or authenticity vetting.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ("Find and evaluate influencers", "verify authenticity", "track collaboration performance") across named platforms, with only minor coverage gaps, matching the score-4 anchor.	4 / 5
Completeness	The 'what' is clear but there is no explicit 'Use when...' or equivalent trigger clause, which the judging guidelines cap at 3 even though the action list is strong.	3 / 5
Trigger Term Quality	Contains relevant natural keywords ("influencers", "brand partnerships", "authenticity") but omits common synonyms and lacks file-extension-style terms, fitting the score-3 anchor of partial coverage.	3 / 5
Distinctiveness Conflict Risk	Targets a clear niche (influencer discovery across named social platforms) with minimal overlap risk against other skills, matching the mostly-distinct score-4 anchor.	4 / 5
	Total	14 / 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-influencer-discovery/SKILL.md
Commit: 1f67c44

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