SIF Keyword Traffic & Competition Analysis Agent Skill

Analyzes Amazon keyword traffic share, top ASIN distribution, ad structures, and market competition using Wenmai SIF data.

Context cost
2.2k tokensestimated from the bundle, loaded when it triggers
Bundle
6 files · 13.1 kB2 scripts among them — read before you run
Licence
MITthe author’s own terms
Last change
—v1.0.0
Servers it uses
Noneruns standalone

What it does

SIF 关键词流量与竞争分析接口,用于查看头部 ASIN 的流量份额、自然/SP/SB/SBV 占比、集中度、竞争位置和关键词机会。当用户提到关键词竞争、流量份额、头部 ASIN、自然广告结构、关键词垄断、竞争强度或 SIF keyword traffic 时触发此技能。即使用户未明确提及 SIF,只要任务需要上述接口能力,也应触发此技能。

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

e-commerce

The skill itself

A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.

SKILL.md4.0 kB · preview
--- name: wenmai-sif-keyword-traffic metadata: author: wenmai-ai version: "1.0.0" ---
9# SIF Keyword Traffic
10
11## Overview
12
13调用 Wenmai SIF standard API market_get_keyword_competition。只调用以下固定端点,不接受动态端点或其他操作:
14
15- Endpoint: POST /wmapi/v1/sif/market-get-keyword-competition
16- Auth: Header secret-key: $WENMAI_API_KEY
17- Script: scripts/sif_keyword_traffic.py
18- API contract: [references/api.md](references/api.md)
19
20在构造请求或解释字段前阅读 references/api.md,以其中的参数、限制、响应字段和错误定义为事实来源。
21
22## Workflow
23
241. 提取并校验用户输入,保留用户指定的平台、市场、标识符和查询范围。
252. 按照 API 契约构造 JSON 请求,保留文档要求的包装层和字段层级。
263. 对照 API 契约处理数量、长度、分页、日期和枚举限制;不静默截断或添加未定义字段。
274. 运行固定脚本并保留原始 JSON 响应。
This is a preview of SKILL.md. Download or install the skill to get the whole thing.
In the file
SKILL.md166 words
Files6
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈70
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
2,105
on trigger
The instruction body and 5 supporting files, read only when the skill fires.
1.1%
of a 200k window
Ten skills this size would take about 11% of the window before you open a file.
050k100k150k200k context window

2.2k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Middling. Fine to keep on in a project where you use it weekly, worth unloading in one where you never do.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

Its SKILL.md does not declare which tools it asks the agent for, so what it touches is whatever the instructions themselves ask for — read them before you install it.

What it asks for
Writes filesnot declared
Network accessnot declared

This SKILL.md carries no allowed-tools line, so neither is declared. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

6 files, 13.1 kB on disk. Mostly text — the instructions the model reads — with 2 scripts in it that your client would run only if the instructions tell it to.

  • SKILL.md4.0 kB
  • skill-card.md1.1 kB
  • agents/openai.yaml0.3 kB
  • references/api.md3.3 kB
  • scripts/_wenmai_api.py4.0 kB
  • scripts/sif_keyword_traffic.py0.4 kB
What is not in it

A skill installs nothing and depends on nothing: it is a folder your client reads. This one carries 2 scripts beside the text, so the bundle is 6 files you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# SIF Keyword Traffic & Competition Analysis · 2.2k tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/sif-keyword-traffic-competition-analysis/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/sif-keyword-traffic-competition-analysis" ] && { [ ! -e .claude/skills/sif-keyword-traffic-competition-analysis ] || { mv .claude/skills/sif-keyword-traffic-competition-analysis "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/sif-keyword-traffic-competition-analysis" .claude/skills/ && echo "Installed .claude/skills/sif-keyword-traffic-competition-analysis"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add wenmai-ai/sif-keyword-traffic-competition-analysis

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/sif-keyword-traffic-competition-analysis/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/sif-keyword-traffic-competition-analysis/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/sif-keyword-traffic-competition-analysis" ] && { [ ! -e ~/.claude/skills/sif-keyword-traffic-competition-analysis ] || { mv ~/.claude/skills/sif-keyword-traffic-competition-analysis "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/sif-keyword-traffic-competition-analysis" ~/.claude/skills/ && echo "Installed ~/.claude/skills/sif-keyword-traffic-competition-analysis" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/sif-keyword-traffic-competition-analysis/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where. It appears as wenmai-sif-keyword-traffic in Gemini CLI, Codex, Copilot and Grok (its own name); Claude Code lists it by the folder name, sif-keyword-traffic-competition-analysis.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Version1.0.0
Publishedno release date on file
PriceFree
Referencewenmai-ai/sif-keyword-traffic-competition-analysis

Versions

v1.0.0 is what is on the shelf; no release here carries a date. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v1.0.0
  • No earlier releases have been published to the marketplace.
Pinning

The install command always fetches the release that is current the day you run it — v1.0.0 today — and cannot ask for an earlier one. The copy on your disk does not change until you run it again.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Publisher
Servers0
Claim this skill