CtrlK
BlogDocsLog inGet started
Tessl Logo

apify-lead-generation

Scrape leads from multiple platforms using Apify Actors.

46

Quality

48%

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/skills/apify-lead-generation/SKILL.md

The canonical home for this skill is apify-lead-generation in sickn33/agentic-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 is a solid, actionable skill with clear executable commands and a well-structured multi-step workflow. Its main weaknesses are the lack of validation checkpoints between workflow steps (e.g., verifying schema fetch success before proceeding) and the large inline Actor table that could be split into a reference file. The error handling section is useful but disconnected from the workflow steps where errors would actually occur.

Suggestions

Add validation checkpoints within the workflow, e.g., after Step 2 verify the schema was fetched successfully before proceeding, and after Step 4 check the script exit code before summarizing.

Move the Actor lookup table to a separate reference file (e.g., ACTORS.md) and link to it from the main skill to improve conciseness and progressive disclosure.

Integrate error handling into the relevant workflow steps rather than listing it as a separate section at the end.

DimensionReasoningScore

Conciseness

The content is mostly efficient but includes some redundancy—the large Actor table could arguably be in a reference file, and the three nearly identical command examples (quick answer, CSV, JSON) differ only by flags, which could be condensed. However, it avoids explaining basic concepts Claude already knows.

2 / 3

Actionability

Provides fully executable bash commands with concrete flags, a clear Actor selection table, and specific script invocations with real argument patterns. The mcpc command for fetching schemas is copy-paste ready with only the Actor ID needing substitution.

3 / 3

Workflow Clarity

The 5-step workflow is clearly sequenced with a progress checklist, but there are no validation checkpoints between steps—no verification that the Actor schema was fetched correctly, no check that the script ran successfully before summarizing, and no feedback loop for error recovery within the workflow itself. Error handling is listed separately without integration into the workflow steps.

2 / 3

Progressive Disclosure

The skill references external scripts (run_actor.js) appropriately, but the large Actor lookup table (17 rows) bloats the main file and would be better placed in a reference file. The content is reasonably structured with clear sections but doesn't leverage external files for the detailed reference material.

2 / 3

Total

9

/

12

Passed

Description

32%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 brief and identifies the core domain (lead scraping via Apify Actors) but lacks specificity about what actions are performed, which platforms are targeted, and critically omits any 'Use when...' guidance. It would benefit from listing concrete capabilities and explicit trigger conditions to help Claude select it appropriately.

Suggestions

Add a 'Use when...' clause with trigger terms like 'scrape leads', 'lead generation', 'Apify', 'prospect list', 'contact extraction'.

List specific concrete actions such as 'extract contact emails, phone numbers, and company details from LinkedIn, Google Maps, and other platforms'.

Mention specific platform names or file formats to improve distinctiveness and reduce overlap with generic scraping skills.

DimensionReasoningScore

Specificity

Names the domain (lead scraping) and a key tool (Apify Actors), but doesn't list specific concrete actions like extracting emails, phone numbers, company info, or which platforms are supported.

2 / 3

Completeness

Describes what it does (scrape leads using Apify Actors) but has no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 2, and the 'what' itself is also thin, bringing this to a 1.

1 / 3

Trigger Term Quality

Includes relevant keywords like 'scrape', 'leads', and 'Apify Actors', but misses common user variations such as 'lead generation', 'prospect list', 'contact extraction', 'LinkedIn', 'web scraping', or specific platform names.

2 / 3

Distinctiveness Conflict Risk

The mention of 'Apify Actors' adds some distinctiveness, but 'scrape leads from multiple platforms' is broad enough to overlap with other web scraping or lead generation skills.

2 / 3

Total

7

/

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.