CtrlK
BlogDocsLog inGet started
Tessl Logo

apify-influencer-discovery

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

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/apify-influencer-discovery/SKILL.md

The canonical home for this skill is apify-influencer-discovery in sickn33/antigravity-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

64%Scale 1-3

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 clear multi-platform Actor selection table. Its main weaknesses are the lack of validation checkpoints integrated into the workflow (e.g., verifying schema fetch, validating input JSON) and the monolithic structure that could benefit from splitting the Actor table and detailed examples into reference files. The error handling section is useful but would be more effective if woven into the relevant workflow steps.

Suggestions

Add validation checkpoints after Step 2 (verify schema was fetched successfully) and after Step 4 (verify the run completed and output file exists) to create feedback loops for error recovery.

Move the 16-row Actor selection table to a separate reference file (e.g., ACTORS.md) and link to it from the main skill to improve progressive disclosure and reduce token usage.

Integrate error handling into the relevant workflow steps rather than listing them separately at the bottom, so Claude encounters the right error guidance at the right time.

DimensionReasoningScore

Conciseness

The content is reasonably efficient but includes some redundancy—the large Actor table with 16 entries could be trimmed or moved to a reference file. The step-by-step structure is clear but the three nearly identical command blocks for CSV/JSON/quick answer add bulk that could be condensed.

2 / 3

Actionability

Provides fully executable bash commands with concrete flags, specific Actor IDs, and clear input/output patterns. The mcpc command for fetching schemas is copy-paste ready, and the run_actor.js invocations are specific and complete.

3 / 3

Workflow Clarity

The workflow has a clear 5-step sequence 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. Error handling is listed separately but not integrated into the workflow steps.

2 / 3

Progressive Disclosure

The content is mostly inline with no references to external documentation files. The large Actor selection table (16 rows) would benefit from being in a separate reference file. The skill references scripts in `${CLAUDE_PLUGIN_ROOT}/reference/scripts/` but doesn't link to any supplementary docs for advanced usage or Actor-specific guides.

2 / 3

Total

9

/

12

Passed

Description

67%Scale 1-3

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 weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. Trigger term coverage could also be broadened to include common user synonyms like 'creator', 'sponsorship', or 'social media marketing'.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about finding creators, vetting influencers, or measuring sponsorship ROI on social media.'

Include additional natural trigger terms users might say, such as 'creator', 'KOL', 'sponsorship', 'engagement rate', 'social media marketing', or 'influencer campaign'.

DimensionReasoningScore

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 at 2 per the rubric.

2 / 3

Trigger Term Quality

Includes good keywords like 'influencers', 'brand partnerships', 'Instagram', 'TikTok', 'YouTube', 'Facebook', but misses common user variations like 'creator', 'KOL', 'sponsorship', 'engagement rate', 'follower count', or 'social media marketing'.

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

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.