CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

apify-influencer-discovery

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

Quality

73%

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 ./skills/apify-influencer-discovery/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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.

A well-sequenced, checkpoint-rich workflow with genuinely strong error recovery and pre-paid-run validation, delivered concisely. Its critical defect is that the invoked runner script is not bundled, leaving the commands non-executable and the only external reference dangling.

Suggestions

Bundle the referenced runner script (e.g. under scripts/run_actor.js) and correct the path in all three Step 4 command blocks so the commands are executable as shipped.

State the script's expected CLI contract (flags, defaults like the --max-items 1000 mentioned only in Run Boundaries) in or near Step 4 so the placeholder values can be filled confidently.

Tighten the Run Boundaries and Limitations sections — move billing/scope caveats into a short bulleted list and drop the generic boilerplate lines.

DimensionReasoningScore

Conciseness

The body is dense and purposeful with no explanations of concepts Claude already knows — no padding around the Actor table, commands, or error handling. Minor instances could be trimmed (the generic boilerplate in 'Limitations' and the meandering 'Run Boundaries' paragraph), matching the 'efficient; minor instances of over-explanation' anchor rather than the every-token-earns-its-place level.

4 / 5

Actionability

The workflow provides concrete command templates (node --env-file=.env ... --actor ... --input ... --output ... --format ...), but they rely on placeholders ('ACTOR_ID', 'JSON_INPUT', '<resolved-skill-directory>') and, decisively, the invoked script 'reference/scripts/run_actor.js' does not exist in the skill bundle (no references/, scripts/, or assets/ directories are present), so the commands are not executable as shipped — matching 'some concrete guidance but incomplete'.

3 / 5

Workflow Clarity

The five-step sequence is explicit and tracked via a copyable checklist, with validation checkpoints throughout: 'Verify prerequisites before any paid run', fetching the Actor schema before calling it, confirming 'the selected Actor, authorized public-data scope, current input schema, result limits and pricing' before launch, and an error-handling table with recovery loops (e.g. on timeout, 'Inspect the printed run ID in Console before retrying to avoid duplicate charges') — matching the explicit-validation-plus-feedback-loops anchor.

5 / 5

Progressive Disclosure

Internal structure is good (clear When to Use / Prerequisites / Workflow / Error Handling / Run Boundaries / Limitations sections), but scored against the actual bundle structure the single external reference — 'reference/scripts/run_actor.js' — is a dangling path with no bundled file behind it, so navigation to the actual tooling fails and the split is incomplete.

3 / 5

Total

15

/

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.

A solid, third-person description with several concrete capabilities and natural trigger terms covering the four platforms. Its main deficiency is the complete absence of an explicit 'Use when...' trigger clause, which both caps completeness and weakens distinctiveness.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks to find influencers or creators, vet candidates for brand partnerships or sponsorships, or analyze follower/engagement signals on Instagram, Facebook, YouTube, or TikTok.'

Add common synonyms users naturally say — 'creators', 'social media', 'campaign', 'outreach', 'engagement' — to broaden trigger-term coverage.

Make the capability objects more concrete (e.g. mention scraping profiles/hashtags, exporting shortlists, or comparing engagement metrics) to close the specificity gap.

DimensionReasoningScore

Specificity

The description lists several concrete actions ('Find and evaluate influencers for brand partnerships, assess public authenticity signals, and track collaboration performance') across four named platforms, but the actions' objects stay somewhat abstract (no scraping, shortlisting, or export specifics), matching the 'several specific actions; minor gaps' anchor rather than comprehensive coverage.

4 / 5

Completeness

It clearly answers 'what' (find, evaluate, assess, track influencers) but contains no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines; the 'when' is entirely absent rather than weakly implied, so it cannot score 4.

3 / 5

Trigger Term Quality

Natural user phrases are present ('influencers', 'brand partnerships', 'Instagram, Facebook, YouTube, and TikTok', 'authenticity'), giving good keyword coverage; common synonyms like 'creators', 'social media', 'campaign', 'outreach', or 'engagement' are missing, so it falls just short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

'Influencers for brand partnerships' plus the four platform names carves a mostly distinct niche with minor overlap risk against generic social-media scraping or marketing analytics skills; it is not fully distinctive because no trigger phrases delineate it from adjacent skills.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

sickn33/agentic-awesome-skills

Path

skills/apify-influencer-discovery/SKILL.md

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.