apify-ecommerce
Extract product data, prices, reviews, and seller information from any e-commerce platform using Apify's E-commerce Scraping Tool.
77
72%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/apify-ecommerce/SKILL.mdQuality
Discovery
67%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 strong in specificity and distinctiveness, clearly naming concrete data types and the specific tool (Apify). However, it lacks an explicit 'Use when...' trigger clause, which limits completeness, and could benefit from more natural user-facing trigger terms like specific platform names or common synonyms.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user wants to scrape product listings, compare prices, or gather reviews from online stores.'
Include common trigger variations such as specific platform names (Amazon, eBay, Shopify) and synonyms like 'scrape', 'online store', 'product listings', 'shopping data'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Extract product data, prices, reviews, and seller information' — these are distinct, concrete data types rather than vague abstractions. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (extract product data, prices, reviews, seller info from e-commerce platforms), but lacks an explicit 'Use when...' clause specifying when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes good terms like 'product data', 'prices', 'reviews', 'seller information', and 'e-commerce', but misses common user variations like 'scrape Amazon', 'product listings', 'online store', 'shopping', or specific platform names. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of e-commerce scraping, Apify tool reference, and specific data types (prices, reviews, seller info) creates a clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with clear workflows, executable examples, and good error handling. Its main weakness is length — the extensive marketplace listings and audience descriptions add tokens without proportional value, and the content would benefit from splitting detailed reference material into separate files. The workflow clarity is excellent with a progress checklist and clear decision matrix.
Suggestions
Move the full marketplace listing to a separate reference file (e.g., MARKETPLACES.md) and keep only a brief mention of supported platforms in the main skill.
Remove 'Best for' audience descriptions (e.g., 'Pricing analysts, product managers') — Claude doesn't need to know the target persona to execute the workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is generally well-structured but includes some unnecessary verbosity, such as 'Best for' audience descriptions (e.g., 'Pricing analysts, product managers, market researchers') that Claude doesn't need, and the extensive marketplace listing that could be in a reference file. The workflow selection table and use case descriptions add moderate bloat. | 2 / 3 |
Actionability | Provides fully executable JSON input examples for each workflow, concrete bash commands for running the extraction, specific field names for output, and clear error handling. The examples are copy-paste ready with realistic data. | 3 / 3 |
Workflow Clarity | Clear multi-step workflow with explicit sequencing (select workflow → configure input → ask preferences → run extraction → summarize results), a progress tracking checklist, and a workflow selection table. The three workflows are well-differentiated with clear decision criteria. Error handling table provides recovery guidance. | 3 / 3 |
Progressive Disclosure | The skill is quite long (~250 lines) and includes content that could be split into reference files, particularly the full marketplace listing and detailed workflow examples. It references a script path but doesn't link to separate detailed docs for advanced features. The structure within the file is good with clear sections, but the monolithic nature reduces discoverability. | 2 / 3 |
Total | 10 / 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
1a9f5ac
- 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.