CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

apify-ecommerce

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

Quality

77%

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

78%Weight 40%Scale 1-5

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

A highly actionable, well-structured skill: concrete commands, complete JSON examples, and genuinely useful operational caveats (charges, pagination limits, run reconciliation) with almost no filler. Its main weaknesses are the missing 'Use when' guidance in the description and monolithic inline reference data (marketplace lists, per-workflow schemas) that belongs in a separate reference file.

Suggestions

Move the exhaustive marketplace domain lists and the per-workflow input schema tables into a one-level-deep reference file (e.g. references/marketplaces.md), keeping only a few representative examples inline in SKILL.md.

Add an explicit validation checkpoint between running the script and summarizing results — e.g. verify the item count and spot-check exported records — to complete the feedback loop for this batch, billable operation.

Clarify the script location convention (reference/scripts/ vs references/scripts/) and confirm the referenced run_actor.js ships with the skill bundle.

DimensionReasoningScore

Conciseness

The body is efficient — tight tables, JSON snippets, and an error/solution table with no explanations of concepts Claude already knows — with only minor trimmable padding such as the "Best for" audience lines and the ~60 inline marketplace domain names.

4 / 5

Actionability

Bash commands are copy-paste ready with exact flags (--actor, --input, --output, --format), each workflow has complete executable JSON input examples, output fields and sort options are enumerated, and the error table maps concrete failures to solutions, covering the common cases.

5 / 5

Workflow Clarity

A progress-tracking checklist, a workflow-selection table, and Steps 1–3 give a clear sequence, and the error-handling table plus "keep its run ID, inspect/reconcile status" guidance provide most checkpoints; the gap is no explicit verify-output checkpoint before summarizing, which keeps it below anchor 5.

4 / 5

Progressive Disclosure

Headers organize the content well and the script path is clearly signaled, but no bundle files exist, and bulk reference material (60+ marketplace domains, full per-workflow input schemas) is inlined in SKILL.md instead of being split into a one-level-deep reference file.

3 / 5

Total

16

/

20

Passed

Description

66%Weight 40%Scale 1-5

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, honest about its scope, and clearly anchored to a named tool, but it omits any explicit 'when to use this' trigger guidance. Adding a 'Use when...' clause with natural trigger phrases (scraping, price monitoring, competitor analysis, Amazon/Walmart data) would lift both completeness and trigger term quality.

Suggestions

Append a trigger clause, e.g. "Use when the user needs product, price, review, stock, or seller data from e-commerce sites, or mentions scraping Amazon, Walmart, Google Shopping, price monitoring, or competitor analysis."

Include natural synonyms users would say — "scrape", "price monitoring", "MAP compliance", marketplace names like Amazon/Walmart — to improve trigger term coverage and distinctiveness from generic web-scraping skills.

Soften or exemplify the over-claim "any e-commerce platform" by naming the major supported marketplaces, which also sharpens specificity.

DimensionReasoningScore

Specificity

"Extract product data, prices, reviews, and seller information ... using Apify's E-commerce Scraping Tool" names four concrete data objects and a specific tool, matching 'several specific actions; minor gaps' — one generic item ("product data") and a single verb keep it below the comprehensive anchor 5.

4 / 5

Completeness

The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3; not 2 because the 'what' is fully specific rather than vague.

3 / 5

Trigger Term Quality

Natural user terms are present ("prices", "reviews", "product", "seller information", "e-commerce"), giving good keyword coverage, but common synonyms like "scrape/scraping", specific marketplaces (Amazon, Walmart), and "price monitoring" are missing, so it falls short of anchor 5.

4 / 5

Distinctiveness Conflict Risk

Naming "Apify's E-commerce Scraping Tool" establishes a clear niche with minimal conflict risk, but the absence of distinct trigger phrases leaves minor overlap risk with generic web-scraping or other Apify skills, so it fits anchor 4 rather than 5.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

sickn33/agentic-awesome-skills

Path

skills/apify-ecommerce/SKILL.md

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.