apify-ecommerce

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is highly actionable and concise, with strong examples and error handling. Its main gaps are a missing validation checkpoint for batch operations and a monolithic structure that underuses progressive disclosure.

Suggestions

Add an explicit validation/verification step in the extraction workflow (e.g., inspect result count and spot-check fields before exporting or summarizing), creating a validate→fix→retry feedback loop for batch runs.

Move the long marketplace enumeration and per-workflow detail into separate reference files (e.g., MARKETPLACES.md, WORKFLOWS.md) and keep SKILL.md as an overview with clearly signaled one-level-deep links.

Confirm the referenced script path exists in a `references/scripts/` bundle (the body uses `reference/scripts/`) so the link is not broken.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it does not explain what e-commerce or scraping is, and each section delivers actionable content with minimal padding.	3 / 3
Actionability	Provides fully executable `node --env-file=…` commands, concrete JSON input examples per workflow, documented output fields, and a structured error-handling table — copy-paste ready with clearly marked placeholders.	3 / 3
Workflow Clarity	Sequencing is clear (progress checklist, Workflow Selection table, numbered extraction steps), but batch extraction of hundreds of items has no explicit validation/verification checkpoint before summarizing, which caps workflow clarity at 2 per the rubric.	2 / 3
Progressive Disclosure	Well-organized into clear sections, but it is a monolithic ~270-line document with all three workflows, marketplace enumerations, and examples inline; the referenced `$SKILL_PATH/reference/scripts/run_actor.js` has no corresponding bundle file, and content that could be split (marketplace list, per-workflow detail) is not separated out.	2 / 3
	Total	10 / 12 Passed

Description

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 specific and occupies a distinctive niche, but it omits explicit trigger guidance, leaving Claude without a clear 'when to use this' signal.

Suggestions

Add a 'Use when…' clause listing natural trigger situations (e.g., 'Use when monitoring prices, analyzing product reviews, comparing competitors, or finding sellers across e-commerce sites').

Broaden trigger terms to include common user phrasings like 'scrape products', 'price monitoring', 'competitor comparison', and 'MAP enforcement'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Extract product data, prices, reviews, and seller information' — naming four distinct capabilities rather than vague language.	3 / 3
Completeness	Clearly answers what the skill does, but the 'when' is missing — there is no 'Use when…' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	Contains relevant natural terms (prices, reviews, product data, seller information) but omits common variations users would say (scrape, price monitoring, competitor analysis, MAP) and has no explicit 'Use when…' trigger phrasing.	2 / 3
Distinctiveness Conflict Risk	Targets a clear niche ('Apify's E-commerce Scraping Tool' on 'any e-commerce platform') with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Commit: 2aaaf59

Reviewed: about 6 hours ago

Table of Contents

Discovery Implementation Validation

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.