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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/apify-ecommerce/SKILL.md

The canonical home for this skill is apify-ecommerce in sickn33/agentic-awesome-skills

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 JSON inputs and copy-paste commands for all three workflows, a clear step sequence with progress tracking, and practical error handling. The main improvements are structural — offloading reference material (marketplace list, field tables) to separate files — and adding an explicit output-verification checkpoint.

Suggestions

Move the supported-marketplaces list (and optionally the per-workflow input-field tables) to a references/ file (e.g. references/marketplaces.md) and link to it, keeping SKILL.md as a lean overview — this is the weakest dimension.

Consolidate the three near-identical bash invocations into one command with documented flags (--output, --format) to trim redundancy.

Add an explicit verification checkpoint before summarizing, e.g. "Check the output/file is non-empty; if 0 items, consult the error table before reporting" — important for batch actor runs.

DimensionReasoningScore

Conciseness

The body is dense with tables, JSON examples, and bash commands, with no explanations of concepts Claude already knows; the marketplace list and input-field tables carry non-obvious exact values that earn their tokens. Minor trimming is possible — three near-identical bash invocations could be one template with flags — matching anchor 4 ('efficient; minor instances that could be trimmed') rather than 5's every-token-earns-its-place.

4 / 5

Actionability

Every workflow has complete, concrete JSON input examples, and the run section provides copy-paste bash commands (including --env-file handling, output filename, and format flags) plus an error-to-solution table. The examples cover the common cases (product URLs, keyword search, reviews, seller discovery), matching anchor 5 ('fully executable; copy-paste ready code or commands').

5 / 5

Workflow Clarity

A five-step progress checklist, a sequenced run section, and a summarize step that reports item counts and workflow-specific insights give a clear sequence, and the error-handling table provides an error-recovery loop. It stays at anchor 4 rather than 5 because validation is reactive (handled via the error table) rather than an explicit checkpoint before reporting results — notable since actor runs are batch operations.

4 / 5

Progressive Disclosure

Section structure is good, but this is a single ~260-line SKILL.md with only one referenced file (reference/scripts/run_actor.js, which is not present in the provided bundle). Reference material — the 30-line supported-marketplaces list and the per-workflow field tables — is inlined rather than split into separate files, fitting anchor 3 ('some structure but... content that should be separate is inline') rather than 4's mostly-appropriate placement.

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.

A solid, third-person description with concrete actions and a distinct Apify/e-commerce niche. Its main weakness is the absence of any 'Use when...' trigger clause, which both caps completeness and leaves natural trigger phrasing (marketplace names, competitor/price-monitoring language) underexploited.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to scrape or monitor product prices, reviews, or seller data from e-commerce marketplaces like Amazon, Walmart, or Google Shopping."

Include a few natural synonyms users would actually say — "competitor prices", "price monitoring", "Amazon reviews", "scrape products" — to strengthen trigger_term_quality.

Mention the export capability (CSV/JSON files) to round out coverage of what the skill does.

DimensionReasoningScore

Specificity

"Extract product data, prices, reviews, and seller information" lists several concrete actions that map directly to the skill's three workflows, but coverage has minor gaps (no mention of CSV/JSON export, keyword search, or AI-generated insights). This matches anchor 4 ('lists several specific actions; minor gaps in coverage') rather than 5, which would require comprehensive coverage of all capabilities.

4 / 5

Completeness

The description has a clear 'what' but no 'Use when...' clause or equivalent explicit trigger guidance, which the rubric says caps completeness at 3. It clearly explains anchor 3 ('has a clear what but when is missing or only weakly implied') and does not reach 4, which requires both what and when.

3 / 5

Trigger Term Quality

Natural terms users would say are present: "product data", "prices", "reviews", "seller information", "e-commerce", "scraping". A few common variations are missing — no marketplace names (Amazon, Walmart), no "competitor" or "price monitoring" phrasing — so it fits anchor 4 ('good keyword coverage; a few natural terms missing') rather than 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"Apify's E-commerce Scraping Tool" carves out a clear niche, but "from any e-commerce platform" is broad and could overlap with generic web-scraping or price-tracking skills. This fits anchor 4 ('mostly distinct; minor overlap risk with closely related skills') rather than 5's minimal conflict risk.

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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/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.