CtrlK
BlogDocsLog inGet started
Tessl Logo

apify-ecommerce

Extract product data, prices, reviews, and seller information from any e-commerce platform using Apify's E-commerce Scraping Tool.

61

Quality

72%

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 ./skills/apify-ecommerce/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 well-structured, highly actionable skill with clear workflows, concrete JSON examples, and executable commands. Its main weakness is length — the supported marketplaces section and some audience-targeting language ('Best for: Brand managers...') add bulk without adding value for Claude. The content would benefit from offloading reference material like marketplace lists to separate files.

Suggestions

Move the full supported marketplaces listing to a separate reference file (e.g., MARKETPLACES.md) and link to it, keeping only a brief mention in the main skill.

Remove 'Best for' audience descriptions from each workflow — Claude doesn't need to know the job titles of intended users to execute the workflow correctly.

DimensionReasoningScore

Conciseness

The skill is reasonably well-structured but includes some unnecessary verbosity, such as 'Best for' audience descriptions (Claude doesn't need to know who the audience is), the 'When to Use' section restating what's obvious from context, and the full marketplace listing which could be in a reference file. The supported marketplaces section alone is quite lengthy.

2 / 3

Actionability

The skill provides fully executable JSON input configurations, concrete bash commands with proper flags, specific field names and their meanings, and clear examples for each workflow. The commands are copy-paste ready with appropriate variable substitution patterns.

3 / 3

Workflow Clarity

Each workflow has a clear sequence from input configuration through execution to summarization. The progress tracking checklist provides explicit steps, the error handling table covers common failure modes with solutions, and the 'Step 1-2-3' execution section provides a clear sequence with a summarization/validation step at the end.

3 / 3

Progressive Disclosure

The content is well-organized with clear sections and tables, but the supported marketplaces list (40+ lines) and detailed workflow configurations make this a long monolithic document. The marketplace list and possibly the detailed input examples could be split into reference files. No bundle files are provided to offload content to, and no references to external files are made except the script path.

2 / 3

Total

10

/

12

Passed

Description

67%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 strong in specificity and distinctiveness, clearly naming concrete data types and the specific tool (Apify). However, it lacks an explicit 'Use when...' clause which limits its completeness score, and could benefit from additional natural trigger terms that users might actually say when requesting this capability.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user wants to scrape product listings, compare prices, gather reviews, or extract data from online stores.'

Include common trigger term variations such as specific platform names ('Amazon', 'eBay', 'Shopify'), synonyms ('online store', 'shopping site', 'product listings'), and file/format references users might mention.

DimensionReasoningScore

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 relevant terms like 'product data', 'prices', 'reviews', 'e-commerce', and 'scraping', but misses common user variations like 'Amazon', 'shopping', 'product listings', 'web scraping', or specific platform names users might mention.

2 / 3

Distinctiveness Conflict Risk

The combination of 'e-commerce', 'Apify', and specific data types (prices, reviews, seller information) creates a clear niche that is unlikely to conflict with other skills.

3 / 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

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.