e commerce

Data Community

Skill notes

General Patterns

Check for sitemap.xml first -- many stores list all product URLs Look for /products.json, /api/products, or similar API endpoints before scraping HTML Product listing pages usually paginate: look for ?page=N, ?offset=N, or "Load more" buttons Always check the total count shown on the page vs what you've extracted

Product Data Checklist

Name, brand, SKU/ID Price (current, original/compare-at, currency) Variants (size, color, etc.) with per-variant pricing and availability Images (primary + gallery) Description (short + long)

Pagination

Check for: next/prev links, page numbers, "showing X of Y" text For infinite scroll: use interact to scroll and load more Keep count: if page says "200 products" and you have 24, keep going

JS-Heavy Sites

Use interact for sites that require JavaScript rendering Look for XHR/API calls in the page that return JSON -- often easier than parsing HTML Single-page apps often have internal APIs at predictable paths

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Data
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@firecrawl · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# E-commerce Extraction

## General Patterns
- Check for sitemap.xml first -- many stores list all product URLs
- Look for /products.json, /api/products, or similar API endpoints before scraping HTML
- Product listing pages usually paginate: look for ?page=N, ?offset=N, or "Load more" buttons
- Always check the total count shown on the page vs what you've extracted

## Product Data Checklist
- Name, brand, SKU/ID
- Price (current, original/compare-at, currency)
- Variants (size, color, etc.) with per-variant pricing and availability
- Images (primary + gallery)
- Description (short + long)
- Category/breadcrumb path
- Availability/stock status
- Ratings and review count

## Pagination
- Check for: next/prev links, page numbers, "showing X of Y" text
- For infinite scroll: use interact to scroll and load more
- Keep count: if page says "200 products" and you have 24, keep going

## JS-Heavy Sites
- Use interact for sites that require JavaScript rendering
- Look for XHR/API calls in the page that return JSON -- often easier than parsing HTML
- Single-page apps often have internal APIs at predictable paths

## Site-specific playbooks are in the sites/ directory

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.