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?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/antigravity-awesome-skills-claude/skills/apify-lead-generation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

64%

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 comprehensive Actor selection table and executable commands. Its main weaknesses are the lack of validation checkpoints in the workflow (e.g., verifying schema fetch results, validating inputs before running, handling empty results) and some verbosity in boilerplate sections. The progressive disclosure would benefit from bundle files being present to support the referenced script paths.

Suggestions

Add validation checkpoints after Step 2 (verify schema was fetched successfully) and after Step 4 (check if results are empty or contain expected fields) to create feedback loops for error recovery.

Move the large Actor selection table to a separate reference file (e.g., ACTORS.md) and keep only the most common 4-5 actors inline, linking to the full table.

Remove or significantly trim the 'Limitations' boilerplate section and 'When to Use' section, as these are generic and don't add skill-specific value.

DimensionReasoningScore

Conciseness

The content is mostly efficient but includes some unnecessary elements like the boilerplate limitations section and the 'When to Use' section that largely restates what Claude could infer. The Actor table is comprehensive and useful, but the overall document could be tightened.

2 / 3

Actionability

Provides fully executable bash commands for each step, a comprehensive Actor selection table with specific IDs, concrete CLI invocations with all flags, and clear error handling with specific error messages and fixes. The commands are copy-paste ready with clear placeholder substitution.

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 if the run produces unexpected or empty results. The error handling section is separate rather than integrated into the workflow.

2 / 3

Progressive Disclosure

The skill references scripts at `${CLAUDE_PLUGIN_ROOT}/reference/scripts/run_actor.js` but no bundle files are provided to verify these exist. The content is reasonably structured with clear sections, but the large Actor table could potentially be in a separate reference file, and there are no links to additional documentation for advanced usage patterns.

2 / 3

Total

9

/

12

Passed

Description

32%

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 too brief and lacks both specific concrete actions and explicit trigger guidance. While it correctly identifies the tool (Apify Actors) and general purpose (lead scraping), it fails to enumerate specific capabilities, supported platforms, or conditions under which Claude should select this skill.

Suggestions

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

List specific concrete actions such as 'extract contact information, company details, email addresses, and social profiles from platforms like LinkedIn, Google Maps, and Twitter using Apify Actors'.

Include common user-facing synonyms and variations like 'lead gen', 'prospect extraction', 'web scraping for contacts' to improve 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 emails, phone numbers, company info, or which platforms are supported.

2 / 3

Completeness

Describes what it does (scrape leads using Apify Actors) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also thin, warranting 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

Mentioning 'Apify Actors' provides some distinctiveness from generic scraping skills, but 'scrape leads from multiple platforms' is broad enough to potentially 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
sickn33/antigravity-awesome-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.