Find and evaluate influencers for brand partnerships, verify authenticity, and track collaboration performance across Instagram, Facebook, YouTube, and TikTok.
77
66%
Does it follow best practices?
Impact
99%
6.60xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/antigravity-awesome-skills-claude/skills/apify-influencer-discovery/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. Its main weaknesses are the absence of an explicit 'Use when...' clause and missing some natural trigger term variations that users might employ when seeking influencer marketing assistance.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user asks about influencer marketing, finding creators for campaigns, or evaluating social media partnerships.'
Include additional natural trigger terms like 'creator', 'KOL', 'sponsorship', 'influencer marketing', 'engagement rate', and 'campaign ROI' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'find and evaluate influencers', 'verify authenticity', 'track collaboration performance', and names 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 dimension at 2 per the rubric. | 2 / 3 |
Trigger Term Quality | Includes good keywords like 'influencers', 'brand partnerships', 'Instagram', 'YouTube', 'TikTok', but misses common user variations like 'creator', 'KOL', 'sponsorship', 'influencer marketing', 'engagement rate', or 'follower count'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of influencer discovery, authenticity verification, and collaboration tracking across named social platforms creates a clear, distinct niche that is unlikely to conflict with other skills. | 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 for influencer discovery across multiple platforms. Its main weaknesses are the lack of validation checkpoints in the workflow (e.g., verifying schema fetch, validating inputs before execution) and some verbosity in the Actor table and boilerplate limitations section. The progressive disclosure could be improved by offloading the large reference table to a separate file.
Suggestions
Add explicit validation checkpoints after Step 2 (verify schema was fetched successfully) and after Step 4 (verify the run completed and output file exists before summarizing).
Move the 16-row Actor selection table to a separate reference file (e.g., ACTORS.md) and keep only the most common 4-5 entries inline with a link to the full list.
Remove the generic 'Limitations' section — these are boilerplate guardrails Claude already follows and waste tokens.
Integrate error handling into the relevant workflow steps rather than listing them separately at the end.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary content. The large Actor table with 16 entries is useful but could be trimmed. The limitations section contains generic boilerplate that doesn't add value. The prerequisites note '(No need to check it upfront)' is odd filler. | 2 / 3 |
Actionability | Provides fully executable bash commands with clear argument patterns, a concrete Actor selection table, and specific error handling guidance. The commands are copy-paste ready with clear placeholder substitution patterns. | 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 schema was fetched correctly, no validation of the JSON input before running, and no feedback loop for handling partial or unexpected results. The error handling section is separate rather than integrated into the workflow. | 2 / 3 |
Progressive Disclosure | The content references `${CLAUDE_PLUGIN_ROOT}/reference/scripts/run_actor.js` but no bundle files are provided to verify this exists. The skill is somewhat monolithic — the 16-row Actor table could be in a separate reference file. However, the section structure is clear and navigable. | 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 | |
4cc48db
Table of Contents
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.