Apify Ecommerce
majiayu000/claude-skill-registry
Extract product data, prices, reviews, and seller information from any e-commerce platform using Apify's E-commerce Scraping Tool.
Collect Apify debug evidence for support tickets and troubleshooting.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill apify-debug-bundle -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace apify-debug-bundle --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/apify-debug-bundle .claude/skills/apify-debug-bundle && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "apify-debug-bundle" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/apify-debug-bundle into .claude/skills/apify-debug-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "apify-debug-bundle", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/apify-debug-bundleType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill apify-debug-bundle -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace apify-debug-bundle --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.curated/apify-debug-bundle .agents/skills/apify-debug-bundle && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "apify-debug-bundle" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/apify-debug-bundle into .agents/skills/apify-debug-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "apify-debug-bundle", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill apify-debug-bundle -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace apify-debug-bundle --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.curated/apify-debug-bundle .cursor/skills/apify-debug-bundle && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "apify-debug-bundle" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/apify-debug-bundle into .cursor/skills/apify-debug-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "apify-debug-bundle", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path skills/.curated/apify-debug-bundle--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill apify-debug-bundle -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace apify-debug-bundle --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.curated/apify-debug-bundle .gemini/skills/apify-debug-bundle && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "apify-debug-bundle" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/apify-debug-bundle into .gemini/skills/apify-debug-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "apify-debug-bundle", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace apify-debug-bundleInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill apify-debug-bundle -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.curated/apify-debug-bundle .github/skills/apify-debug-bundle && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "apify-debug-bundle" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/apify-debug-bundle into .github/skills/apify-debug-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "apify-debug-bundle", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill apify-debug-bundle -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace apify-debug-bundle --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.curated/apify-debug-bundle .opencode/skills/apify-debug-bundle && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "apify-debug-bundle" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/apify-debug-bundle into .opencode/skills/apify-debug-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "apify-debug-bundle", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
apify-debug-bundleCollect Apify debug evidence for support tickets and troubleshooting.
Apify Debug Bundle is an agent skill from jeremylongshore/tons-of-skills-marketplace. Collect Apify debug evidence for support tickets and troubleshooting. Use when an Actor run has failed, is stuck, or produced empty output and you need to gather run metadata, logs, dataset samples, and environment info before opening a support ticket. Trigger with "apify debug", "apify support bundle", "collect apify logs", "apify diagnostic", "apify run failed why".
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/examples.md` and `references/implementation.md`). Compatibility notes: Designed for Claude Code
It sits in Sales & Support, covering Web scraping and Customer support. It works with Apify. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 23ea8d4. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadBash(curl:*)Bash(npm:*)Bash(node:*)Bash(tar:*)Bash(apify:*)GrepFrom allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript and bash).
From the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
console.apify.comdocs.apify.comstatus.apify.comFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
APIFY_TOKENFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Designed for Claude Code
From compatibility in the SKILL.md frontmatter.
Apify Debug Bundle loads about 1.3k tokens when it runs, and up to ~3.3k if it reads all its reference files. Until then it costs about 97 tokens; SKILL.md has 502 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
script redacts any local `.env` before packaging, and the platform auto-redactskey-value store keys, a redacted `.env`, and platform health, then packages| `env-redacted.txt` | Local `.env` with all values redacted |Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from jeremylongshore/tons-of-skills-marketplace at commit 23ea8d4, republished under its MIT licence (© jeremylongshore). 502 words, ~1,328 tokens.
.claude/skills/apify-debug-bundle/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.Collect all diagnostic information needed to troubleshoot failed Actor runs and prepare Apify support tickets. Pulls run metadata, logs, dataset samples, and environment info into a single bundle so a support engineer (or you) can diagnose the failure without live access to your account.
apify-client installedAPIFY_TOKEN configuredAll API calls authenticate with the APIFY_TOKEN as a Bearer header
(Authorization: Bearer $APIFY_TOKEN), and the SDK reads the same token from
process.env.APIFY_TOKEN. Get the token from the Apify Console under
Settings → Integrations → Personal API tokens. Never commit it — the bundle
script redacts any local .env before packaging, and the platform auto-redacts
secrets inside run logs.
The workflow has four steps. The skeleton below is enough to run it; each step's full implementation lives in implementation.md.
Investigate the failed run — pull run summary, dataset stats, and the log tail via the SDK. The core call:
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.run(runId).get();
const log = await client.run(runId).log().get();Create the debug bundle — run apify-debug-bundle.sh <RUN_ID>. It
collects environment info, run details, log, a 5-item dataset sample,
key-value store keys, a redacted .env, and platform health, then packages
everything into a timestamped .tar.gz. Full script in
implementation.md.
Compare against a good run (optional) — diff a successful and failed run
field-by-field to spot the delta (compareRuns(successId, failId)).
Live-tail a running Actor (optional) — stream logs when the final log is not yet available.
For copy-pasteable code for every step, see implementation.md.
A single timestamped tarball, apify-debug-YYYYMMDD-HHMMSS.tar.gz, containing:
| File | Contents |
|---|---|
environment.txt | Node/npm versions, installed Apify packages, CLI version |
run-details.json | Run status, options, stats, usage, cost |
run-log.txt | Full run log (secrets auto-redacted by the platform) |
dataset-sample.json | First 5 dataset items |
kv-store-keys.json | Key-value store key listing |
env-redacted.txt | Local .env with all values redacted |
platform-health.json | Apify platform health snapshot |
Attach the tarball directly to an Apify support ticket.
Always redact before sharing:
apify_api_*)Safe to include:
| Issue | Cause | Solution |
|---|---|---|
Run not found | Invalid run ID or expired | Unnamed runs expire after 7 days |
Log unavailable | Run still in progress | Wait for completion or stream live |
| Empty dataset | Actor produced no output | Check failedRequestHandler in code |
| High CU usage | Memory too high or slow execution | Reduce memory, optimize code |
Four worked scenarios — a plain FAILED run, an "it worked yesterday"
regression diff, an empty-dataset investigation, and live-tailing a hung run —
are in examples.md. The quickest path:
export APIFY_TOKEN="apify_api_..."
./apify-debug-bundle.sh abc123DEF # → apify-debug-20260717-142530.tar.gz
tar -xzf apify-debug-*.tar.gz && tail -40 apify-debug-*/run-log.txtSee examples.md for the full walkthroughs, including reading the comparison output and interpreting a live tail.
For rate limit issues, see the apify-rate-limits skill.
© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 2 other files (references) in skills/.curated/apify-debug-bundle of jeremylongshore/tons-of-skills-marketplace.
Open the folder on GitHubat commit 23ea8d4
Apify Debug Bundle next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Apify Debug Bundle this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.3k | Automated safety check: Notes | MIT | |
| Apify Ecommercemajiayu000/claude-skill-registry | 666 | 3 repos | ~2.3k | Automated safety check: Notes | MIT | |
| Etsy Shop Sales Historysickn33/agentic-awesome-skills | 47k | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Ops LeadgenLifecycle-Innovations-Limited/claude-ops | 540 | — | ~990 | Automated safety check: Notes | MIT | |
| Tech Stack Teardownmajiayu000/claude-skill-registry | 666 | 2 repos | ~3.1k | Automated safety check: Notes | MIT | |
| Voice Of Customer Synthesizermajiayu000/claude-skill-registry | 666 | 2 repos | ~2.4k | Automated safety check: Pass | MIT |
majiayu000/claude-skill-registry
Extract product data, prices, reviews, and seller information from any e-commerce platform using Apify's E-commerce Scraping Tool.
sickn33/agentic-awesome-skills
Read Etsy shop sales counters, deltas, and breakout flags from Apify Actor publicrecords/etsy-shop-velocity (MCP panel snapshot).
Lifecycle-Innovations-Limited/claude-ops
OPS on-demand: This skill should be used when the user asks to "leadgen drafts", "cold email approve"…
majiayu000/claude-skill-registry
Reverse-engineer a company's sales and marketing tech stack from public signals.
majiayu000/claude-skill-registry
Aggregate customer feedback from multiple sources — support tickets, NPS comments, Slack messages, G2 reviews, call transcripts, survey responses — into a unified VoC report with theme clustering…
apify/awesome-skills
Scrape e-commerce data for pricing, reviews, bestsellers, and seller discovery across 30+ platforms including Amazon, Walmart, eBay, Shopify, WooCommerce, and more.
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to perform natural language processing and text analysis using the nlp-text-analyzer plugin.
jeremylongshore/tons-of-skills-marketplace
Execute this skill allows AI assistant to construct and configure neural network architectures using the neural-network-builder plugin.
jeremylongshore/tons-of-skills-marketplace
Process identify anomalies and outliers in datasets using machine learning algorithms.
jeremylongshore/tons-of-skills-marketplace
Build this skill enables AI assistant to provide interpretability and explainability for machine learning models.
jeremylongshore/tons-of-skills-marketplace
Execute this skill optimizes prompts for large language models (llms) to reduce token usage, lower costs, and improve performance.
Works with
Categories
Collect Apify debug evidence for support tickets and troubleshooting. Apify Debug Bundle is an agent skill from jeremylongshore/tons-of-skills-marketplace. Collect Apify debug evidence for support tickets and troubleshooting.
Apify Debug Bundle fits situations like: an Actor run has failed; produced empty output and you need to gather run metadata; dataset samples; environment info before opening a support ticket.
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill apify-debug-bundle -a claude-code`. Or copy the skill folder (skills/.curated/apify-debug-bundle in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/apify-debug-bundle in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill apify-debug-bundle -a codex`. Or copy the skill folder (skills/.curated/apify-debug-bundle in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/apify-debug-bundle in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill apify-debug-bundle -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/apify-debug-bundle, .gemini/skills/apify-debug-bundle, .github/skills/apify-debug-bundle and .opencode/skills/apify-debug-bundle in your project.
Going by SKILL.md and its folder, Apify Debug Bundle needs credentials named APIFY_TOKEN. Our summary lists: A credential in APIFY_TOKEN. Its frontmatter pre-approves these tools: Read, Bash(curl:*), Bash(npm:*), Bash(node:*), Bash(tar:*), Bash(apify:*), Grep. Compatibility (from SKILL.md): Designed for Claude Code.
SKILL.md names 3 domains. As links in the text: console.apify.com, docs.apify.com and status.apify.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Apify Debug Bundle is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Apify Debug Bundle: Apify Ecommerce (majiayu000/claude-skill-registry, 666 stars), Etsy Shop Sales History (sickn33/agentic-awesome-skills, 47k stars), Ops Leadgen (Lifecycle-Innovations-Limited/claude-ops, 540 stars) and Tech Stack Teardown (majiayu000/claude-skill-registry, 666 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,821 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 8, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.