apify-lead-generation
Scrape leads from multiple platforms using Apify Actors.
46
48%
Does it follow best practices?
Impact
—
No eval scenarios have been run
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.mdQuality
Discovery
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 brief and identifies the core domain (lead scraping via Apify Actors) but lacks specificity about concrete actions, supported platforms, and output formats. The absence of a 'Use when...' clause significantly weakens its utility for skill selection, and the trigger terms are too narrow to capture the variety of ways users might request this functionality.
Suggestions
Add a 'Use when...' clause with trigger terms like 'scrape leads', 'lead generation', 'prospect list', 'Apify', 'contact extraction', or specific platform names (e.g., LinkedIn, Google Maps).
List specific concrete actions such as 'extract contact emails, phone numbers, and company details from LinkedIn, Google Maps, and other platforms using Apify Actors'.
Include common user-facing synonyms and variations like 'lead gen', 'prospecting', 'web scraping for contacts' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
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' specifically adds some distinctiveness, but 'scrape leads from multiple platforms' is broad enough to potentially overlap with other scraping or lead generation skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
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 concrete commands and a well-organized Actor lookup table. Its main weaknesses are the lack of validation/feedback loops in the workflow (e.g., checking if an Actor run succeeded before summarizing) and some verbosity in boilerplate sections. The referenced script paths cannot be verified since no bundle files were provided.
Suggestions
Add a validation checkpoint after Step 4 (e.g., check exit code or output for errors before proceeding to summarize), and integrate error handling as a feedback loop within the workflow rather than a separate section.
Move the Actor lookup table to a separate reference file (e.g., ACTORS.md) and link to it from the main skill to improve progressive disclosure and reduce SKILL.md length.
Remove the generic 'Limitations' boilerplate at the bottom — these are general agent instructions Claude already knows, not skill-specific constraints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary sections like the generic 'Limitations' boilerplate and the 'When to Use' section that largely restates the description. The Actor table is comprehensive but could be more concise. The prerequisites note '(No need to check it upfront)' is oddly placed. | 2 / 3 |
Actionability | Provides fully executable bash commands for every step, concrete Actor IDs in a lookup table, specific CLI flags and options, and clear input/output patterns. The commands are copy-paste ready with clear placeholder substitution. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced with a progress checklist, but there are no validation checkpoints between steps. After running the actor (Step 4), there's no verification that the run succeeded before summarizing. The error handling section exists but isn't integrated into the workflow as feedback loops. | 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 Actor table is quite long and could potentially be split into a reference file. The content is reasonably structured with clear sections but the inline Actor table makes the document lengthy. | 2 / 3 |
Total | 9 / 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
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
4cc48db
- 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.