ecommerce.amazon-traffic-keywords SKILL.md skillA
ecommerce.amazon-traffic-keywords from nexscope-ai/nexscope-ecommerce-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add nexscope-ai/nexscope-ecommerce-skills/ecommerce.amazon-traffic-keywords@git:20261009.1aae8f1Pins git:20261009.1aae8f1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- nexscope-ai/nexscope-ecommerce-skills
- Path
ecommerce-amazon-traffic-keywords/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261009.1aae8f1, committed Oct 9, 2026
- First version recorded
- Aug 28, 2026
- Size
- 5,136 bytes
- Repository stars
- 96
- License
- none declared
Query traffic keyword lists for an Amazon ASIN via Nexscope, including traffic source type, conversion type, organic rank, and ad rank with historical month and multi-dimensional sorting. Trigger when user mentions ASIN reverse traffic keywords, traffic keyword list, keyword traffic structure, organic/ad keyword analysis, keyword conversion type, Nexscope traffic keyword, Amazon traffic keywords, reverse ASIN keywords — even if "Nexscope" is not explicitly mentioned, as long as the need…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Nexscope Traffic Keyword This skill helps query and analyze traffic keyword lists for an Amazon ASIN via Nexscope. ## Core Concepts - **ASIN Reverse Keyword Lookup**: Input an ASIN to view the keyword list that drives traffic to that product. - **Traffic Share Types** (`trafficKeywordTypes`): Primary traffic keywords, precise traffic keywords, and `preciseLongTail` (labeled as "conversion loss keywords" in the tool UI) as defined in the schema. - **Conversion Types** (`conversionKeywordTypes`): Conversion-strong keywords, stable keywords, loss keywords, etc. - **Keyword Badges** (`badges`): Organic search keywords, Amazon Choice recommended keywords, etc. ## API Invocation - **API Endpoint**: `POST /sellersprite/traffic/keyword` (full parameters/response/error codes in `references/api.md`) - **Python Script**: `python scripts/amazon_traffic_keywords.py ''<JSON params>'' [--inline]` …
Read the whole file at its exact version.
How to install
mdr add nexscope-ai/nexscope-ecommerce-skills/ecommerce.amazon-traffic-keywords@sha256:da936e523ed7f733The line at the top of this page pins the label git:20261009.1aae8f1, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_lfe6xwxs2uxzfpf5)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Aug 28, 2026 and Oct 9, 2026, about one every 21 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261009.1aae8f1 latest | 2026-10-09 | 1aae8f1 | 5,136 B | A | view · diff |
| git:20260917.c57e917 | 2026-09-17 | c57e917 | 5,156 B | A | view · diff |
| git:20260828.7fb4686 | 2026-08-28 | 7fb4686 | 5,160 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5136 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nexscope-ai/nexscope-ecommerce-skills · 96 stars · license none declared · pushed 2026-10-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lfe6xwxs2uxzfpf5 GET https://markdownregistry.com/api/v1/resolve?ref=nexscope-ai/nexscope-ecommerce-skills/ecommerce.amazon-traffic-keywords GET https://markdownregistry.com/api/v1/blob/da936e523ed7f7336a60d421da43d3ea6285e21ae24c43026b3c04b47c5808a9
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.