AgentStack
SKILL verified MIT Self-run

Clawec Amazon Report Hijacker

skill-clawec-clawec-agents-clawec-amazon-report-hijacker · by clawEC

Drafts professional Amazon Seller Central case messages to report unauthorized sellers or listing violations commonly referred to as 跟卖, addressed to Seller Support with store name and ASIN. Use for 举报跟卖, 跟卖投诉, hijacker report, unauthorized seller, listing infringement case, or Seller Support escalation when policy allows. Output is template text only; Amazon decides based on policy, Brand Regist…

No reviews yet
0 installs
5 views
0.0% view→install

Install

$ agentstack add skill-clawec-clawec-agents-clawec-amazon-report-hijacker

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Clawec Amazon Report Hijacker? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

举报跟卖邮件(Seller Support 案例稿)

何时使用本技能

在卖家拟通过 Amazon Seller Central → Seller Support / 适用举报入口特定 ASIN 上的跟卖/未经授权销售等行为提交说明时使用(具体可走的路径以账户权限、是否 Brand Registry、问题类型为准)。本技能只生成英文案例正文与主题草稿(亚马逊全球支持常用英文);不保证下架或处罚结果。

输入项(与表单一致,两项均必填)

| 字段 | 必填 | 说明 | |------|------|------| | 跟卖者的店铺名 | 是 | Listing 上显示的卖家名称或店铺标识(与用户截图一致);若有多名跟卖,可分条描述或让用户分次生成。 | | ASIN | 是 | 被跟卖的商品 ASIN(B0 开头等格式);一信一案可只写一个 ASIN,多个 ASIN 在正文中编号列出。 |

一键粘贴模板

跟卖者的店铺名(必填):
ASIN(必填):

核心原则

  1. 事实与政策:仅基于用户提供的真实信息撰写;陈述可验证项(ASIN、卖家显示名、观察到的 offers 情况),避免辱骂与无证指控(如「必是假货」若无依据请改为「请求依政策核查」)。
  2. 渠道提示:不同情形可能对应 Report a Violation、Brand Registry、Project Zero、Transparency 等工具;若仅适用 Seller Support Case,正文保持一案一焦点,附件与证据类型在 checklist 中列出。
  3. 合规边界:滥用举报可能导致己方账户风险;不在稿中教唆捏造销量损失、伪造聊天记录或冒充权利。

硬性输出要求

同一回复内按顺序给出:

  1. Routing note(简短):根据用户是否提到品牌备案/商标,提示应优先核对的官方入口;若信息不足,写「需用户自扫路径」而非瞎编。
  2. Case title / Subject(英文):简洁含 ASIN 关键词。
  3. Case body(英文):可粘贴至 Seller Support 的正文—含礼貌开头、ASIN、跟卖者店铺名、时间线占位、已采取措施、请求平台动作、附件说明占位。
  4. Evidence checklist:建议准备的截图/订单号/品牌证书等(用户脱敏后上传)。
  5. 中文操作摘要(3–6 句):团队内部用,说明草稿用途与限制。
  6. 无 Emoji;句中可用 [ORDER_ID][DATE_FIRST_NOTICED] 等占位符补全用户未填项。

合规与禁忌

  • 禁止虚假举报、打击竞品、无权利基础却声称侵权。
  • 不保证「删跟卖」话术;不写违法威胁第三方内容。

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.