amazon-analysis
Skill77 starsChanged 8 months agoMITView on GitHub
Amazon-domain general analysis and multi-endpoint research engine. Handles broad or composite Amazon research requests that span multiple data dimensions or have no single specialized angle. For focused category-market discovery, market-entry evaluation, or category trends, use amazon-market-analysis. Use when: - user asks for multi-endpoint Amazon research or composite reports - user asks "what kind of Amazon analysis can I run" or wants an overview of available Amazon insights - user wants broad Amazon data exploration with no single specific deliverable in mind Uses {skill_base_dir}/scripts/zoodata.py. Requires ZOODATA_API_KEY.
- Reads credentials
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- amazon-competitor-intelligence-monitorSkill
- amazon-daily-market-radarSkill
- amazon-keyword-traffic-analysisSkill
- amazon-listing-audit-proSkill
- amazon-market-analysisSkill
- amazon-pricing-command-centerSkill
- amazon-review-intelligence-extractorSkill
- web-extractSkill
- zoodataSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 30
Read references/cli-contract.md before selecting or invoking a command.
- Very specific: line 31
Read references/reference.md for endpoint fields and local CLI options.
- Very specific: line 45
Before selecting or invoking the first command, read and apply the local references/cli-contract.md.
- Very specific: line 49
Use the failure rendering in references/execution-guide.md.
- Distinctive: line 55
Treat seller budget, experience, risk tolerance, and other profile text as local interpretation inputs.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ZooData — Amazon Seller Data Analysis
Respond in the user's language. Use this skill for broad or composite Amazon research without a single specialized deliverable. Route a focused market-entry, market-discovery, or category-trend request to amazon-market-analysis; route a focused keyword, listing, pricing, review, or competitor request to its dedicated skill.
Start here
- Classify the user's question. For a single data point, use the quick path in
references/execution-guide.md; for multi-endpoint research, load its full workflow. - Read
references/cli-contract.mdbefore selecting or invoking a command. Inspect the bundled CLI's top-level and selected subcommand help. - Read
references/reference.mdfor endpoint fields and local CLI options. Load the applicable scenario module:scenarios-composite.mdfor broad cross-validation,scenarios-eval.mdfor product evaluation,scenarios-expand.mdfor expansion,scenarios-listing.mdfor listing context,scenarios-ops.mdfor operations, orscenarios-pricing.mdfor pricing context. - Apply the shared interpretation and reporting rules in
references/execution-guide.md; use the selected scenario for its specific evidence and conclusion scope.
Source-of-truth boundaries
- This
SKILL.mdowns trigger routing, module loading, the responsibility map, and non-negotiable runtime boundaries. It does not define product presets, thresholds, endpoint fields, procedures, or report templates. references/cli-contract.mdowns shared CLI invocation, command identity, result classification, retries, and terminal or partial-result handling.references/reference.mdowns endpoint availability, request and response fields, CLI parameter mapping, data shapes, and field identity. It does not set analytical thresholds.references/execution-guide.mdowns shared workflow steps, product-preset selection, market-health interpretation, cross-endpoint analysis, and user-facing output rules. It does not redefine endpoint fields.- Scenario modules own the evidence selection, conclusions, and scenario-specific report sections for their named task. They may narrow shared workflow rules but cannot redefine endpoint contracts or shared output rules.
{skill_base_dir}/scripts/zoodata.pyowns local preset expansion, request construction, transport metadata, and credential handling; it does not issue business conclusions.
Shared CLI Contract
Before selecting or invoking the first command, read and apply the local references/cli-contract.md. Reapply it after every granular or composite result and before any fallback, additional call, state write, interpretation, or report. The local references/execution-guide.md owns user-facing failure rendering.
Local Interface Failure Output
Use the failure rendering in references/execution-guide.md; direct a user with exhausted credits to https://zoodata.ai/en/pricing.
Non-negotiable boundaries
- Require
ZOODATA_API_KEY; use the bundled CLI and the local command manifest. The credential-onlycheckpath precedes evidence calls. Stop and follow the shared CLI contract on credential, credit, validation, or terminal interface failures; do not invent missing evidence. - Resolve and preserve a category path or ID before category-scoped comparisons. Distinguish inferred category paths from direct matches. Preserve marketplace, date, category scope, sample type, and the difference between full-category and selected Top 100 SPU metrics.
- Treat seller budget, experience, risk tolerance, and other profile text as local interpretation inputs. Send only the documented category/product identifiers and numeric filters to the API.
- State estimated credit cost before a broad multi-call scan. Require the user's explicit monitoring request before creating recurring work or saved baselines.
Capabilities and data flow
- Network: the bundled CLI sends authenticated requests to
https://api.zoodata.aiand refuses an untrustedZOODATA_BASE_URL. - Execution: Python 3 standard-library shared CLI at
{skill_base_dir}/scripts/zoodata.py. - Local files: reads optional
~/.zoodata/config.json; review fallback may use a private temporary directory. - Sent to the API: keywords, category paths/IDs, ASINs, marketplace, dates, and numeric filters. Seller profile text remains local.
- Credits: evidence calls consume account credits; the credential-only
checkpath does not.
Execution entry
python {skill_base_dir}/scripts/zoodata.py <documented-subcommand> ...This skill allows categories, market, market-profile, market-price-distributions, market-rating-distributions, market-rating-count-distributions, market-listing-age-distributions, market-fulfillment-distributions, market-seller-country-distributions, market-content-distributions, market-top-product-concentrations, market-brand-concentrations, market-seller-concentrations, market-listing-launch-trend, market-history, products, competitors, product, analyze, report, opportunity, history, brand-overview, brand-detail, price-band-overview, price-band-detail, check, reviews-raw, review-tag-prompt, review-reduce-prompt, and review-aggregate.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

