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/antigravity-awesome-skills-claude/skills/apify-lead-generation/SKILL.md
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 a well-organized workflow and comprehensive Actor selection table. Its main weaknesses are the lack of validation checkpoints in the workflow (e.g., verifying schema fetch, validating input JSON) and some unnecessary boilerplate content. The executable commands are well-structured with clear patterns for different output formats.

Suggestions

Add a validation step after fetching the Actor schema (Step 2) to verify the response contains expected fields before proceeding, and add input JSON validation before running the script.

Remove the generic 'Limitations' boilerplate section and trim the 'When to Use' section, as these add tokens without adding actionable guidance Claude wouldn't already infer.

Consider moving the large Actor selection table to a separate reference file (e.g., ACTORS.md) and keeping only the most common 4-5 actors inline.

DimensionReasoningScore

Conciseness

The content is mostly efficient with good use of tables and structured steps, but includes some unnecessary sections like the generic 'Limitations' boilerplate and the 'When to Use' section that largely restates what Claude could infer. The Actor table is comprehensive but could be more concise.

2 / 3

Actionability

Provides fully executable bash commands with clear argument patterns, a comprehensive Actor selection table with specific IDs, and concrete 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 that the input JSON is well-formed before running, and no feedback loop for handling partial results or retrying failed runs.

2 / 3

Progressive Disclosure

The skill references scripts at `${CLAUDE_PLUGIN_ROOT}/reference/scripts/run_actor.js` suggesting a bundle structure exists, but no bundle files were provided for evaluation. The content is reasonably structured with sections but the Actor table is quite long inline and could potentially be split into a reference file.

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 concise but underdeveloped. It identifies the core domain (lead scraping via Apify) but lacks specific actions, explicit trigger guidance, and natural keyword variations that would help Claude reliably select this skill. Adding a 'Use when...' clause and more concrete capabilities would significantly improve it.

Suggestions

Add a 'Use when...' clause with trigger terms like 'scrape leads', 'lead generation', 'Apify', 'prospect list', 'contact extraction', or specific platform names (e.g., LinkedIn, Google Maps).

List specific concrete actions such as 'extract contact information, build prospect lists, export leads to CSV/JSON, configure Apify Actors for targeted scraping'.

Mention specific platforms or data types (e.g., 'LinkedIn profiles, Google Maps businesses, website directories') to improve distinctiveness and trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain (lead scraping) and a key tool (Apify Actors), but doesn't list specific concrete actions like extracting contact info, filtering leads, exporting to CSV, etc. 'Scrape leads' is a single action rather than multiple specific capabilities.

2 / 3

Completeness

Describes what it does (scrape leads using Apify Actors) but has no 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also fairly thin, warranting a 1.

1 / 3

Trigger Term Quality

Includes relevant keywords like 'scrape', 'leads', 'Apify', and 'platforms', but misses common user variations such as 'lead generation', 'prospect list', 'contact scraping', 'web scraping', or specific platform names (LinkedIn, Google Maps, etc.).

2 / 3

Distinctiveness Conflict Risk

The mention of 'Apify Actors' provides some distinctiveness, but 'scrape leads from multiple platforms' is broad enough to potentially overlap with other web scraping or lead generation skills. Specifying which platforms or data types would improve distinctiveness.

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.

Validation — 10 / 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
popey/claude-code-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.