{"id":"83469994-7f4b-4547-a6bf-abe51a46b4f1","entityType":"agent","slug":"clawhub-leooooooow-hijack-defender","name":"Hijack Defender","canonicalUrl":"https://www.xpersona.co/agent/clawhub-leooooooow-hijack-defender","canonicalPath":"/agent/clawhub-leooooooow-hijack-defender","generatedAt":"2026-10-13T20:52:22.837Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T21:02:02.665Z","emptyReason":null},"description":"Detect, document, and remove unauthorized third-party sellers hijacking your Amazon listings or ecommerce product pages — with step-by-step enforcement workf...","descriptionLabel":"Source description","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 993 downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s17974h9acjg4h7h5djv1hg51d83hcca:hijack-defender","sourceUrl":"https://clawhub.ai/leooooooow/hijack-defender","homepage":"https://clawhub.ai/leooooooow/skills/hijack-defender","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/leooooooow/hijack-defender","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/leooooooow/skills/hijack-defender","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":60,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Hijack Defender technical dossier on Xpersona with agent coverage, OPENCLEW support, and live trust metadata."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T21:02:02.665Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T21:02:02.665Z","emptyReason":null},"stars":null,"forks":null,"downloads":993,"likes":null,"task":null,"library":null,"packageName":null,"latestVersion":"1.1.0","tractionLabel":"993 downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T21:02:02.652Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T21:02:02.665Z","lastCrawledAt":"2026-10-11T21:02:02.652Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T21:02:02.652Z","lastVerifiedAt":null,"highlights":[{"version":"1.1.0","createdAt":"2026-06-06T14:44:17.046Z","changelog":"No changes detected in version 1.0.2. - No updates have been made to the skill files. - All functionality and documentation remain the same as the previous version.","fileCount":7,"zipByteSize":15320},{"version":"1.0.1","createdAt":"2026-06-06T14:41:28.651Z","changelog":"Hijack Defender v1.0.1 — Adds dedicated resources and workflow templates for streamlined Amazon listing hijacker response. - Added evidence collection guide, enforcement checklist, cease-and-desist template, and output template for systematic hijacking response. - Enhanced documentation with detailed step-by-step workflows for detection, evidence gathering, enforcement, and prevention. - Removed outdated skill-card.md in favor of new actionable reference materials. - Refined playbook to emphasize evidence standards, rapid enforcement, and proactive protection.","fileCount":7,"zipByteSize":15417},{"version":"1.0.0","createdAt":"2026-04-16T03:22:19.454Z","changelog":"Initial release.","fileCount":3,"zipByteSize":3928}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17974h9acjg4h7h5djv1hg51d83hcca:hijack-defender","setupComplexity":"low","setupSteps":["Install using `clawhub skill install s17974h9acjg4h7h5djv1hg51d83hcca:hijack-defender` in an isolated environment before connecting it to live workloads.","No published capability contract is available yet, so validate auth and request/response behavior manually.","Review the upstream CLAWHUB listing at https://clawhub.ai/leooooooow/hijack-defender before using production credentials."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-leooooooow-hijack-defender/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-leooooooow-hijack-defender/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-leooooooow-hijack-defender/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-leooooooow-hijack-defender/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-leooooooow-hijack-defender/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-leooooooow-hijack-defender/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-13T20:52:22.836Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-leooooooow-hijack-defender/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-leooooooow-hijack-defender/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-leooooooow-hijack-defender/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-leooooooow-hijack-defender/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T21:02:02.665Z","emptyReason":null},"readme":"Skill: Hijack Defender\n\nOwner: leooooooow\n\nSummary: Detect, document, and remove unauthorized third-party sellers hijacking your Amazon listings or ecommerce product pages — with step-by-step enforcement workf...\n\nTags: latest:1.1.0\n\nVersion history:\n\nv1.1.0 | 2026-06-06T14:44:17.046Z | user\n\nNo changes detected in version 1.0.2.\n\n- No updates have been made to the skill files.\n- All functionality and documentation remain the same as the previous version.\n\nv1.0.1 | 2026-06-06T14:41:28.651Z | user\n\nHijack Defender v1.0.1 — Adds dedicated resources and workflow templates for streamlined Amazon listing hijacker response.\n\n- Added evidence collection guide, enforcement checklist, cease-and-desist template, and output template for systematic hijacking response.\n- Enhanced documentation with detailed step-by-step workflows for detection, evidence gathering, enforcement, and prevention.\n- Removed outdated skill-card.md in favor of new actionable reference materials.\n- Refined playbook to emphasize evidence standards, rapid enforcement, and proactive protection.\n\nv1.0.0 | 2026-04-16T03:22:19.454Z | user\n\nInitial release.\n\nArchive index:\n\nArchive v1.1.0: 7 files, 15320 bytes\n\nFiles: cease-and-desist-template.md (5851b), checklist.md (3607b), evidence-collection-guide.md (6720b), output-template.md (3212b), skill-card.md (2305b), SKILL.md (11648b), _meta.json (134b)\n\nFile v1.1.0:SKILL.md\n\n---\nname: Hijack Defender\ndescription: Detect, document, and remove unauthorized third-party sellers hijacking your Amazon listings or ecommerce product pages — with step-by-step enforcement workflows for brand registry, cease-and-desist, and test buy procedures.\n---\n\n# Hijack Defender\n\nListing hijacking happens when an unauthorized seller attaches to your Amazon ASIN (or copies your product page on other marketplaces) and sells counterfeit, unauthorized, or gray-market goods under your brand name. It destroys customer trust, tanks your reviews, and can get your listing suppressed when Amazon receives complaints about products you didn't sell. This skill walks you through detecting hijackers, documenting the violation, submitting enforcement actions, and preventing future attacks.\n\n## Quick Reference\n\n| Decision | Strong | Acceptable | Weak |\n|----------|--------|------------|------|\n| Detection method | Automated monitoring + daily alerts | Weekly manual checks | Reactive (noticing after damage is done) |\n| Evidence standard | Test buy + photos + invoices vs. yours | Photos only | Screenshots only |\n| Enforcement route | Amazon Brand Registry IP report | Case to Seller Support | Public seller feedback only |\n| Cease-and-desist | Attorney-reviewed template | DIY template | Verbal warning only |\n| Time to action | Within 24h of detection | 2–3 days | Week+ |\n| Prevention | Transparency program + brand registry | Brand registry only | No proactive measures |\n\n## Solves\n\n1. **Lost Buy Box** — Hijackers who undercut your price steal the Buy Box, diverting sales from your account to theirs.\n2. **Review bombing** — Counterfeit products generate bad reviews on your ASIN that damage your conversion rate and BSR.\n3. **Account suspension risk** — If Amazon receives too many A-to-Z claims about products \"from your listing\" that you didn't sell, your account can be suspended.\n4. **Brand reputation damage** — Customers who receive counterfeit or sub-standard goods associate the poor experience with your brand.\n5. **Price erosion** — Hijackers selling unauthorized inventory (often gray-market or end-of-life units) at deep discounts undermine your MAP pricing and devalue the brand.\n6. **Slow enforcement loops** — Without documented evidence, enforcement cases get rejected or delayed. This skill builds an evidence package that gets cases resolved.\n7. **Recurrence** — Without prevention systems (Transparency, brand gating), the same hijackers return after removal. This skill closes that loop.\n\n## Workflow\n\n### Step 1 — Set Up Monitoring\nBefore a hijacker appears, set up automated detection:\n- **Amazon Brand Registry**: Use the Brand Dashboard to monitor your ASINs for new sellers.\n- **Seller monitoring tools**: Bindwise, Helium 10 Alerts, or SellerApp send alerts when a new seller appears on your listing.\n- **Manual check** (if no tools): Search your product on Amazon → click the \"New & Used\" offers → record current seller count and seller names.\n\nSet a monitoring cadence: daily for high-volume ASINs, weekly for slower-moving products.\n\n### Step 2 — Identify and Classify the Hijacker\nWhen a new seller appears, classify the violation type:\n- **Counterfeit seller**: Selling fake/replica versions of your product with your brand name.\n- **Unauthorized reseller**: Selling genuine product but without authorization (gray market, overstock, diverted distribution).\n- **Listing pirate**: Created a new listing that copies your images, title, and description to steal your keyword ranking.\n- **ASIN piggyback**: Attached to your ASIN as a third-party seller without any product.\n\nCheck the seller's other listings, feedback history, and location (many hijackers are overseas sellers with new accounts).\n\n### Step 3 — Conduct a Test Buy\nA test buy is the strongest evidence for enforcement. Order the hijacker's product:\n- Use a separate Amazon account (not your brand account)\n- Ship to a neutral address (not your business address)\n- Document everything: order confirmation, shipping details, package arrival photos, product photos vs. your authentic product\n- Keep the packaging, inserts, and product intact for comparison\n\n*Test buys cost money but are often required for Amazon counterfeit enforcement and cease-and-desist legal actions.*\n\n### Step 4 — Build Your Evidence Package\nCompile the following before submitting any enforcement action:\n1. Screenshot of hijacker's offer (including seller name, price, and \"Sold by\" field)\n2. Screenshot of your original listing showing you as the brand owner\n3. Test buy order confirmation and tracking information\n4. Photos: hijacker's product packaging vs. your authentic product\n5. Your trademark registration number (or brand registry enrollment confirmation)\n6. Any proof of MAP violation if the hijacker is an authorized reseller selling below MAP\n\n### Step 5 — Submit Amazon Brand Registry IP Report\nGo to: brand.amazon.com → Report a Violation:\n- Violation type: \"Counterfeit\" for fake products, \"Trademark\" for unauthorized use of your brand name\n- ASIN of the affected listing\n- Infringing seller name/ID\n- Attach evidence (photos, order ID from test buy)\n- Provide trademark registration number\n\nAmazon typically reviews IP reports within 1–5 business days. Counterfeit reports backed by test buys are resolved fastest.\n\n### Step 6 — Send a Cease-and-Desist Letter\nIn parallel with the Brand Registry report, send a C&D to the hijacker:\n- Find seller contact: go to their storefront → click the seller name → \"Ask a question\" (this reaches them via Amazon's messaging system)\n- For the letter: use the template in references/cease-and-desist-template.md\n- State: your trademark rights, the violation, a demand to remove the offer within 48 hours, and consequences of non-compliance\n- CC your legal team or trademark attorney if available\n\n### Step 7 — Escalate if Needed\nIf Amazon's initial enforcement action is rejected or delayed:\n- Re-submit with additional evidence (especially a test buy result if you didn't have one initially)\n- Request escalation to the Amazon Counterfeit Crimes Unit (for repeat offenders)\n- File a DMCA takedown if they've copied your copyrighted images or text\n- Consider sending a formal cease-and-desist from a licensed attorney (carries more weight than self-sent)\n- If the hijacker is a U.S.-based company, a federal trademark infringement letter via certified mail is appropriate\n\n### Step 8 — Implement Prevention Measures\nAfter removing the hijacker, close the loop:\n- **Amazon Transparency**: Enroll products to apply serialized codes to every unit. Unauthorized sellers can't fulfill orders without codes. (Cost: ~$0.01–0.05 per unit)\n- **Brand Gating**: Request Amazon to gate your ASIN — requires approval to list. Available to brand-registered sellers.\n- **Authorized Reseller Policy**: Publish a clear authorized reseller list and make it accessible on your website and Amazon brand store.\n- **MAP Policy**: Establish and enforce a minimum advertised price policy with all authorized resellers.\n\n## Examples\n\n### Example 1 — Counterfeit Seller on Amazon (Electronics Accessory Brand)\n\n**Situation:** Brand selling proprietary phone cases at $24.99. Monitoring alert triggers: 3 new sellers appear on the listing, all pricing at $14.99–16.99.\n\n**Detection:** Seller profiles show all 3 created within the last 60 days, ship from the same region, and have nearly identical feedback text.\n\n**Test buy result:** Products arrive with slightly different packaging, no authenticity card, logo color slightly off, and packaging material noticeably cheaper. Clearly counterfeit.\n\n**Evidence package:**\n- Test buy order ID: 114-XXXXXXX-XXXXXXX\n- Side-by-side product photos showing packaging differences\n- Authentic product invoice from manufacturer\n- Trademark registration #5,XXX,XXX\n\n**Outcome:** Amazon Brand Registry report submitted → All 3 sellers removed within 72 hours. Amazon's Counterfeit Crimes Unit notified due to coordinated nature of attack.\n\n**Prevention added:** Amazon Transparency codes applied to all future production runs.\n\n---\n\n### Example 2 — Unauthorized Reseller Violating MAP (Kitchenware Brand)\n\n**Situation:** Brand sells through 12 authorized retailers. An unauthorized seller appears on Amazon listing at $31.99 — 25% below MAP of $42.99.\n\n**Investigation:** Seller has 4-year history and positive feedback — clearly an unauthorized but legitimate reseller, not a counterfeiter. Likely purchased through a distributor or liquidator.\n\n**Action taken:**\n1. No test buy needed (authentic product, not counterfeit)\n2. Sent Amazon message to seller citing MAP policy and requesting offer removal\n3. Investigated supply chain: traced unauthorized inventory to a regional distributor who sold excess stock to a liquidator\n\n**Outcome:** Seller removed offer within 5 days after receiving the message. Supply chain leak identified and closed by amending distributor agreement to include resale restrictions.\n\n**Note:** Amazon does not enforce MAP directly. Enforcement must come through seller communication and supply chain control — not Brand Registry IP reports (MAP violations alone are not a trademark issue).\n\n---\n\n## Common Mistakes\n\n1. **Reporting without evidence.** Amazon rejects vague reports. You need ASIN, seller ID, specific violation type, and ideally a test buy or trademark registration.\n\n2. **Waiting too long to act.** Hijackers who hold the Buy Box for weeks can generate enough bad reviews to permanently damage your listing's conversion rate.\n\n3. **Confusing MAP violations with counterfeit enforcement.** Amazon doesn't enforce MAP. If an unauthorized reseller is selling authentic goods below MAP, your enforcement path is through seller communication and supply chain control — not trademark reports.\n\n4. **Using your brand account for test buys.** Amazon can see who placed the order. Use a separate personal account.\n\n5. **Ignoring the supply chain leak.** If a legitimate reseller is selling your product without authorization, finding and closing the supply chain leak is more important than the removal itself. Otherwise the inventory keeps appearing.\n\n6. **Not following up after initial removal.** Many hijackers simply return after removal. Monitor the listing for 30 days post-action and be ready to re-file.\n\n7. **Skipping cease-and-desist for counterfeit sellers.** For overseas counterfeiters, a legal letter may not be effective — but it creates a paper trail needed if you escalate to Amazon's Counterfeit Crimes Unit or pursue legal action.\n\n8. **Ignoring review damage from the hijack.** After removing the hijacker, check recent reviews for complaints about product quality that were about counterfeit units. You may be able to request Amazon review removal for reviews about products you didn't sell.\n\n9. **Not enrolling in Amazon Transparency.** It's the only truly preventive solution for Amazon counterfeiting. Without it, hijackers can always return.\n\n10. **Assuming one report is enough for repeat offenders.** Organized counterfeit operations create new seller accounts regularly. Sustained monitoring and repeat reporting is necessary until they give up.\n\n## Resources\n\n- [Output Template](references/output-template.md) — Hijack incident report and enforcement tracker\n- [Cease-and-Desist Template](references/cease-and-desist-template.md) — Draft enforcement letter template\n- [Evidence Collection Guide](references/evidence-collection-guide.md) — Test buy and documentation procedures\n- [Quality Checklist](assets/checklist.md) — Enforcement action readiness checklist\n\nFile v1.1.0:_meta.json\n\n{\n  \"ownerId\": \"kn70fv0ehp50emedet9tx3fekd82pw3b\",\n  \"slug\": \"hijack-defender\",\n  \"version\": \"1.1.0\",\n  \"publishedAt\": 1780757057046\n}\n\nFile v1.1.0:cease-and-desist-template.md\n\n# Cease-and-Desist Letter Templates\n\n## Template A — Amazon Buyer-Seller Messaging (Counterfeit)\n\n**Send via:** Amazon Buyer-Seller Messages (go to seller's storefront → \"Ask a question\")\n\n---\n\nSubject: Notice of Intellectual Property Infringement — Immediate Action Required\n\nDear [Seller Name / Amazon Store Name],\n\nIt has come to our attention that your Amazon seller account ([Seller ID]) is currently offering products on ASIN [ASIN] under the brand name [Your Brand Name] without authorization from [Your Company Name].\n\nWe are the owner of the registered trademark [TRADEMARK NAME], Registration No. [TM NUMBER], registered with the United States Patent and Trademark Office (USPTO). Your listing and/or products constitute:\n\n- Trademark infringement (use of our registered mark without authorization)\n- Unfair competition\n- [If applicable: Counterfeiting of our product and/or packaging]\n\nWe have documented evidence of this infringement, including a test purchase conducted on [DATE], which confirmed the product sold under our brand name does not meet our authenticity standards.\n\n**We demand that you:**\n1. Immediately remove your offer from ASIN [ASIN] and all related listings\n2. Cease all sales of [BRAND NAME] products not purchased from [Your Company Name] or our authorized distributors\n3. Provide written confirmation of compliance within 48 hours of this notice\n\nFailure to comply will result in formal trademark infringement claims filed with Amazon Brand Registry, as well as potential legal action including claims for actual damages, statutory damages of up to $2,000,000 per counterfeit mark under 15 U.S.C. § 1117, attorney's fees, and injunctive relief.\n\nThis letter is not a complete statement of all rights or claims we may have, all of which are expressly reserved.\n\nSincerely,\n\n[Your Name]\n[Title]\n[Company Name]\n[Contact Email]\n[Date]\n\n---\n\n## Template B — Amazon Messaging (Unauthorized Reseller / MAP Violation)\n\nSubject: Unauthorized Resale of [Brand Name] Products\n\nDear [Seller Name],\n\nWe have identified that your Amazon seller account is currently listing [Brand Name] products on ASIN [ASIN] at a price of $[PRICE], which is below our Minimum Advertised Price (MAP) of $[MAP PRICE] and/or without authorization to resell [Brand Name] products.\n\n[Brand Name] products are sold exclusively through our authorized retail partners. Your account does not appear on our list of authorized resellers.\n\nWe request that you:\n1. Immediately remove your offer from ASIN [ASIN]\n2. Provide information about the source of your [Brand Name] inventory (invoice or purchase records)\n\nWe are actively investigating the source of unauthorized [Brand Name] inventory in the market and will take appropriate steps to address supply chain violations. Your cooperation in identifying your source will be taken into account.\n\nPlease respond within 48 hours.\n\nSincerely,\n\n[Your Name]\n[Company Name]\n[Contact Email]\n[Date]\n\n---\n\n## Template C — Formal Legal Letter (Attorney-Ready Template)\n\n*Note: Have this reviewed by a licensed trademark attorney before sending. This version is appropriate for serious or repeat infringers, U.S.-based sellers, or when legal action is imminent.*\n\n---\n\n[ATTORNEY LETTERHEAD OR COMPANY LETTERHEAD]\n[Date]\n\nVIA CERTIFIED MAIL / EMAIL\n\n[Seller/Company Name]\n[Address if known]\n[Email if known]\n\n**RE: Trademark Infringement and Demand for Immediate Cessation — [BRAND NAME]**\n\nTo Whom It May Concern:\n\nThis firm represents [Client Company Name] (\"Client\"), the owner of the registered trademark [TRADEMARK NAME] (U.S. Trademark Registration No. [NUMBER]) for use in connection with [product category].\n\nIt has come to our client's attention that [Infringer Name] (\"You\") has been selling, offering for sale, and/or distributing products under the [BRAND NAME] trademark via Amazon.com (ASIN: [ASIN]) and/or through [other channels] without authorization from our client.\n\n**Your actions constitute:**\n1. Federal trademark infringement under 15 U.S.C. § 1114\n2. Unfair competition under 15 U.S.C. § 1125(a)\n3. [If applicable] Counterfeiting under 15 U.S.C. § 1116(d)\n4. [State law claims as applicable]\n\nOur client has conducted a test purchase and confirmed that the product sold under the [BRAND NAME] trademark is [counterfeit / not authorized / otherwise in violation]. Documentation is maintained.\n\n**Pursuant to this letter, we demand that you:**\n1. Immediately cease all sales, offers for sale, advertising, or distribution of any product bearing the [BRAND NAME] mark\n2. Destroy or return all [BRAND NAME]-branded inventory in your possession\n3. Provide within 10 business days: (a) an accounting of all sales of [BRAND NAME] products, (b) the source of your [BRAND NAME] inventory, and (c) written confirmation of compliance with the above demands\n4. Pay all profits derived from your unauthorized use of our client's trademark\n\nOur client reserves all rights, including the right to seek statutory damages of up to $2,000,000 per counterfeit mark, actual damages, disgorgement of profits, attorney's fees, and injunctive relief.\n\nThis demand is not exhaustive of our client's rights or claims, all of which are expressly reserved. Please govern yourself accordingly.\n\nSincerely,\n\n[Attorney Name]\n[Law Firm Name]\n[State Bar Number]\n[Contact Information]\n\n---\n\n## Notes on Template Selection\n\n| Scenario | Recommended Template |\n|---------|---------------------|\n| First contact with suspected counterfeiter via Amazon | Template A |\n| First contact with unauthorized reseller | Template B |\n| Repeat infringer who ignored Template A | Template C (attorney review recommended) |\n| Overseas seller | Template A + Amazon Brand Registry IP report (legal letters less effective cross-border) |\n| High-volume infringement causing significant revenue loss | Template C + legal action |\n\nFile v1.1.0:checklist.md\n\n# Hijack Defender — Enforcement Readiness Checklist\n\nUse this checklist before submitting any enforcement action. Incomplete evidence packages lead to rejected cases and allow the hijacker to continue operating.\n\n---\n\n## 1. Detection & Classification (5 items)\n- [ ] Hijacker identified with full seller name and seller ID captured\n- [ ] Violation type classified: Counterfeit / Unauthorized Reseller / Listing Copy / ASIN Piggyback\n- [ ] Hijacker's price vs. your price documented\n- [ ] Hijacker's seller account age and feedback rating noted\n- [ ] Detection date logged (for measuring time-to-resolution later)\n\n## 2. Evidence — Listing Documentation (6 items)\n- [ ] Screenshot of hijacker's offer page (seller name, price, \"Sold by\" field visible)\n- [ ] Screenshot of your listing showing you as brand owner\n- [ ] Screenshot of \"All Offers\" display showing the specific hijacker offer\n- [ ] Hijacker's seller profile and feedback page captured\n- [ ] Date/timestamp visible in all screenshots\n- [ ] All screenshots labeled with ASIN, seller name, and date\n\n## 3. Evidence — Brand Documentation (4 items)\n- [ ] Trademark registration number confirmed (USPTO TESS or equivalent)\n- [ ] Brand Registry enrollment confirmation on hand\n- [ ] Manufacturer invoice or purchase order confirming you as authorized seller\n- [ ] Authorized reseller list reviewed (is this seller on it? If yes, investigate MAP/contract violation separately)\n\n## 4. Test Buy (for Counterfeit Cases) (7 items)\n- [ ] Test buy placed from a separate non-brand Amazon account\n- [ ] Order shipped to a neutral address (not brand business address)\n- [ ] Order ID documented\n- [ ] Package exterior photographed upon arrival\n- [ ] Side-by-side product comparison photos taken (authentic vs. received)\n- [ ] Packaging, inserts, and all materials preserved\n- [ ] Comparison photos clearly labeled: \"authentic\" vs. \"hijacker\"\n\n## 5. Amazon Brand Registry Report (6 items)\n- [ ] Report submitted at brand.amazon.com → Report a Violation\n- [ ] Correct violation type selected (Counterfeit vs. Trademark)\n- [ ] ASIN and infringing seller URL provided\n- [ ] Trademark registration number included\n- [ ] Evidence photos attached (4–8 photos, clearly labeled)\n- [ ] Case reference number saved\n\n## 6. Cease-and-Desist (4 items)\n- [ ] C&D message sent via Amazon Buyer-Seller Messaging to hijacker\n- [ ] Template customized with ASIN, trademark number, and specific violation details\n- [ ] 48-hour deadline stated in the message\n- [ ] Copy of sent message saved (screenshot or download)\n\n## 7. Post-Resolution (6 items)\n- [ ] Hijacker's offer confirmed removed from listing\n- [ ] Reviews posted during hijack period reviewed for counterfeit complaints\n- [ ] Review removal requests filed for reviews about products seller didn't ship\n- [ ] Monitoring continued for 30 days post-removal (hijacker may return)\n- [ ] Estimated revenue lost during hijack period calculated\n- [ ] Incident logged in tracker with resolution date and method\n\n## 8. Prevention (5 items)\n- [ ] Amazon Transparency enrollment status reviewed / initiated\n- [ ] Brand Gating request filed for affected ASIN (if not already gated)\n- [ ] Supply chain investigation launched (how did the unauthorized inventory get there?)\n- [ ] Supply chain leak closed (distributor agreement, liquidation channel, etc.)\n- [ ] Authorized reseller policy published and accessible\n\n---\n\n**Total items: 43**\n**Minimum before submitting a counterfeit report: Sections 1–4 complete**\n**Minimum before submitting an unauthorized reseller report: Sections 1–3 complete (no test buy required)**\n\nFile v1.1.0:evidence-collection-guide.md\n\n# Evidence Collection Guide — Listing Hijack Cases\n\n## Why Evidence Quality Determines Enforcement Speed\n\nAmazon resolves IP complaints on a tiered basis:\n- **Tier 1 (resolved in 1–3 days):** Trademark + test buy + photos showing clear counterfeiting\n- **Tier 2 (resolved in 3–7 days):** Trademark + screenshots showing unauthorized brand use\n- **Tier 3 (resolved in 7–30 days or rejected):** Screenshots only, no trademark, vague description\n\nBuild Tier 1 evidence packages for every counterfeit case.\n\n---\n\n## Test Buy Protocol\n\n### Before the Purchase\n1. Create a dedicated \"test buy\" Amazon account separate from your brand account and any personal accounts. Use a neutral email address.\n2. Use a shipping address that is not your business address (team member's home, P.O. Box, or package forwarding service).\n3. Screenshot the listing before purchasing: show seller name, price, \"Sold by\" field, all listing images, and the date in the URL bar.\n4. Note the specific offer you're buying (if multiple sellers exist, select the hijacker's offer explicitly).\n\n### During the Order\n- Screenshot the checkout screen showing: seller name, price, and estimated delivery.\n- Note the order ID (format: 114-XXXXXXX-XXXXXXX).\n- Screenshot the order confirmation email.\n\n### Upon Delivery\nDocument the following the moment the package arrives — do not open fully until you're ready to photograph:\n\n**Package exterior:**\n- Photo of the package as received (all sides)\n- Photo showing return address label (seller's ship-from location)\n- Photo showing your order confirmation number on the packing slip\n\n**Product comparison photos (authentic vs. hijacker):**\n- Side-by-side packaging (front, back, sides)\n- Logo comparison (color accuracy, font, placement)\n- Barcode / UPC comparison (they often match but product inside differs)\n- Any authentication features: holographic stickers, serial numbers, QR codes\n- Inner packaging: foam, inserts, accessories, documentation\n- Product itself: material quality, construction, color accuracy\n- Any authenticity cards or certificates (present in authentic, absent or different in counterfeit)\n\n**Product testing (if safe and applicable):**\n- Weight comparison (counterfeits are often lighter)\n- Performance test documentation (e.g., battery life, output quality)\n- Ingredient or material discrepancy (for consumables or skincare)\n\n### What to Preserve\n- The entire package, product, and all materials in the original received state\n- Digital photos organized by category (see above)\n- Order confirmation email as PDF\n- Tracking information from delivery\n\n*Do NOT dispose of any test buy materials until the enforcement case is fully resolved and any legal threats have passed.*\n\n---\n\n## Screenshot Documentation Checklist\n\nFor every hijack incident, capture and label the following screenshots:\n\n### Listing Screenshots\n- [ ] Full listing page showing: title, brand, images, price, \"Sold by [Hijacker Name]\" field\n- [ ] \"All Offers\" display showing the hijacker's offer selected\n- [ ] Hijacker's seller profile page (storefront)\n- [ ] Hijacker's feedback page (account age, feedback count, rating, recent reviews)\n- [ ] Date visible in browser: use URL bar or open a second tab with google.com → search today's date\n\n### Your Brand Documentation\n- [ ] Your Amazon Brand Registry enrollment page (or confirmation email)\n- [ ] Your product's ASIN on Amazon with you as the listed brand\n- [ ] Your trademark registration certificate (from USPTO TESS or equivalent)\n- [ ] Your product's manufacturer invoice or purchase order (shows you as the authorized seller)\n\n### Post-Submission\n- [ ] Amazon Brand Registry report submission confirmation (case number)\n- [ ] Any Amazon responses to the case\n- [ ] Seller's response to your cease-and-desist message (screenshot from Amazon messaging)\n\n---\n\n## Organizing Your Evidence Package\n\n### Folder Structure\n```\n/hijack-evidence/\n  /[ASIN]-[SellerName]-[Date]/\n    /listing-screenshots/\n      listing-overview.png\n      all-offers.png\n      seller-profile.png\n      seller-feedback.png\n    /test-buy/\n      order-confirmation.pdf\n      package-exterior.jpg\n      product-comparison-front.jpg\n      product-comparison-back.jpg\n      logo-closeup-authentic-vs-counterfeit.jpg\n      [additional comparison photos]\n    /brand-documentation/\n      trademark-registration.pdf\n      brand-registry-enrollment.pdf\n      manufacturer-invoice.pdf\n    /enforcement/\n      amazon-report-confirmation.pdf\n      cease-and-desist-sent.pdf\n      amazon-responses.pdf\n```\n\n### Naming Convention\n`[ASIN]_[SellerID]_[Date]_[EvidenceType]`\n\nExample: `B08XYZ1234_A3SELLER987_2026-06-06_listing-screenshot.png`\n\n---\n\n## Amazon Brand Registry IP Report — Field Guide\n\n**Where:** brand.amazon.com → Protect → Report a Violation\n\n| Field | What to Enter |\n|-------|---------------|\n| Violation type | \"Counterfeit\" if product is fake; \"Trademark\" if brand name is used without authorization |\n| ASIN | The ASIN of your listing being hijacked |\n| Infringing product URL | Direct URL to the hijacker's offer page (copy from \"All Offers\" display) |\n| Seller name | Exact seller name as shown on Amazon |\n| Your trademark | Enter your U.S. trademark registration number (or international equivalent) |\n| Evidence description | Brief factual description: \"Test purchase conducted [date], order [ID]. Product received differs from authentic product in [specific ways]. Photos attached.\" |\n| Attachments | Upload: listing screenshot, comparison photos, order confirmation |\n\n**Tips for faster resolution:**\n- Keep the description factual and specific — avoid vague language like \"looks fake\"\n- Reference the test buy order ID explicitly\n- Upload 4–6 clearly labeled photos, not 20 unlabeled images\n- Submit separate reports for each seller (don't combine multiple sellers in one report)\n\n---\n\n## Escalation Paths\n\n| Situation | Escalation Action |\n|-----------|------------------|\n| Amazon report rejected (no TM found) | Confirm TM registration status on USPTO.gov; resubmit with registration certificate attached |\n| Amazon report rejected (insufficient evidence) | Conduct test buy, resubmit with test buy evidence |\n| Case resolved but seller returns within 30 days | Resubmit with note \"Repeat infringer — previously removed on [case #]\" |\n| Multiple sellers on same listing (organized attack) | Flag as potential coordinated infringement ring; request Counterfeit Crimes Unit referral |\n| Seller is large enough to have legal representation | Escalate to your trademark attorney; consider federal court filing |\n| Product appears on Alibaba/AliExpress as well | File separate takedown on those platforms; may indicate factory-level counterfeiting |\n\nFile v1.1.0:output-template.md\n\n# Hijack Defender — Incident Report & Enforcement Tracker\n\n## Incident Overview\n**Brand:** [Brand Name]\n**ASIN(s) Affected:** [ASIN]\n**Product Name:** [Product Name]\n**Detection Date:** [Date]\n**Detection Method:** [Alert tool / Manual check]\n**Incident Severity:** [Critical / High / Medium / Low]\n\n---\n\n## Hijacker Profile\n\n| Field | Details |\n|-------|---------|\n| Seller Name | [Name] |\n| Seller ID | [ID] |\n| Marketplace | amazon.com / amazon.co.uk / [other] |\n| Listing Price | $[N] |\n| Your Price | $[N] |\n| Price Difference | −$[N] ([%] below) |\n| Seller Account Age | [N] months/years |\n| Seller Feedback Count | [N] |\n| Seller Feedback Rating | [%] |\n| Seller Location (if visible) | [Country/Region] |\n| Violation Type | Counterfeit / Unauthorized Reseller / Listing Copy / ASIN Piggyback |\n\n---\n\n## Evidence Log\n\n| Evidence Item | Status | Date Captured | Notes |\n|--------------|--------|---------------|-------|\n| Screenshot: hijacker's offer page | ✅ / ❌ | [Date] | |\n| Screenshot: your original listing (brand owner) | ✅ / ❌ | [Date] | |\n| Test buy placed | ✅ / ❌ | [Date] | Order ID: [ID] |\n| Test buy received | ✅ / ❌ | [Date] | |\n| Counterfeit product photos (vs. authentic) | ✅ / ❌ | [Date] | |\n| Authentic product invoice from manufacturer | ✅ / ❌ | [Date] | |\n| Trademark registration number | ✅ / ❌ | [Date] | TM #[N] |\n| Brand Registry enrollment confirmation | ✅ / ❌ | [Date] | |\n\n---\n\n## Enforcement Actions Log\n\n| Action | Date | Status | Case/Reference # | Notes |\n|--------|------|--------|-----------------|-------|\n| Amazon Brand Registry IP Report submitted | [Date] | Pending / Resolved / Rejected | [Case #] | |\n| Cease-and-desist sent to seller | [Date] | Sent / Acknowledged / Ignored | | |\n| DMCA takedown (if images copied) | [Date] | Pending / Resolved | | |\n| Escalation to Counterfeit Crimes Unit | [Date] | Pending / Resolved | | |\n| Legal team notified | [Date] | Yes / No | | |\n| Supply chain investigation launched | [Date] | Pending / Resolved | | |\n\n---\n\n## Resolution\n\n| Field | Details |\n|-------|---------|\n| Date hijacker removed | [Date] |\n| Method of removal | Brand Registry / Seller self-removed / Amazon action / Other |\n| Days from detection to removal | [N] |\n| Reviews affected (bad reviews during hijack period) | [N] reviews, avg [rating] |\n| Review removal requests filed | [Y/N] |\n| Estimated lost sales during hijack | [N] units × $[AOV] = $[N] |\n\n---\n\n## Post-Incident Prevention Actions\n\n| Prevention Measure | Status | Target Date |\n|-------------------|--------|-------------|\n| Amazon Transparency enrollment | Enrolled / In Progress / Not started | [Date] |\n| Brand Gating request submitted | Yes / No | [Date] |\n| Supply chain leak identified | Yes / No / Under investigation | [Date] |\n| Supply chain leak closed | Yes / No | [Date] |\n| Authorized reseller list updated/published | Yes / No | [Date] |\n| MAP policy reinforced with all distributors | Yes / No | [Date] |\n\n---\n\n## Open Incidents Tracker\n\n| ASIN | Product | Hijacker | Detected | Status | Priority |\n|------|---------|---------|----------|--------|----------|\n| [ASIN] | [Name] | [Seller] | [Date] | Active / Resolved | High / Med / Low |\n\nFile v1.1.0:skill-card.md\n\n## Description:\n\nDetect, document, and remove unauthorized third-party sellers hijacking your Amazon listings or ecommerce product pages - with step-by-step enforcement workflows for brand registry, cease-and-desist, and test buy procedures.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[leooooooow](https://clawhub.ai/user/leooooooow)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nBrands, ecommerce operators, and authorized sellers use this skill to detect listing hijacks, assemble evidence packages, pursue marketplace enforcement, prepare cease-and-desist communications, and reduce recurrence.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Test buys, marketplace reports, and cease-and-desist workflows can create legal or policy compliance risk if used without proper authority or review.\n\nMitigation: Use only accounts, addresses, trademarks, listings, and evidence you are authorized to control; verify marketplace policy and consult legal counsel before sending enforcement letters.\n\nRisk: Evidence packages may contain customer, seller, address, order, or product data that requires careful handling.\n\nMitigation: Store evidence with restricted access, redact sensitive details where possible, and define retention and deletion practices before sharing.\n\n## Reference(s):\n\n- [Hijack Incident Report and Enforcement Tracker](artifact/output-template.md)\n- [Cease-and-Desist Letter Templates](artifact/cease-and-desist-template.md)\n- [Evidence Collection Guide](artifact/evidence-collection-guide.md)\n- [Enforcement Readiness Checklist](artifact/checklist.md)\n\n## Skill Output:\n\n**Output Type(s):** [guidance, markdown, text]\n\n**Output Format:** [Markdown guidance, checklists, incident tracking tables, and letter templates]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Produces user-filled enforcement documentation and procedural guidance; does not call tools or APIs.]\n\n## Skill Version(s):\n\n1.1.0 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.1: 7 files, 15417 bytes\n\nFiles: cease-and-desist-template.md (5851b), checklist.md (3607b), evidence-collection-guide.md (6720b), output-template.md (3212b), skill-card.md (2653b), SKILL.md (11648b), _meta.json (134b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: Hijack Defender\ndescription: Detect, document, and remove unauthorized third-party sellers hijacking your Amazon listings or ecommerce product pages — with step-by-step enforcement workflows for brand registry, cease-and-desist, and test buy procedures.\n---\n\n# Hijack Defender\n\nListing hijacking happens when an unauthorized seller attaches to your Amazon ASIN (or copies your product page on other marketplaces) and sells counterfeit, unauthorized, or gray-market goods under your brand name. It destroys customer trust, tanks your reviews, and can get your listing suppressed when Amazon receives complaints about products you didn't sell. This skill walks you through detecting hijackers, documenting the violation, submitting enforcement actions, and preventing future attacks.\n\n## Quick Reference\n\n| Decision | Strong | Acceptable | Weak |\n|----------|--------|------------|------|\n| Detection method | Automated monitoring + daily alerts | Weekly manual checks | Reactive (noticing after damage is done) |\n| Evidence standard | Test buy + photos + invoices vs. yours | Photos only | Screenshots only |\n| Enforcement route | Amazon Brand Registry IP report | Case to Seller Support | Public seller feedback only |\n| Cease-and-desist | Attorney-reviewed template | DIY template | Verbal warning only |\n| Time to action | Within 24h of detection | 2–3 days | Week+ |\n| Prevention | Transparency program + brand registry | Brand registry only | No proactive measures |\n\n## Solves\n\n1. **Lost Buy Box** — Hijackers who undercut your price steal the Buy Box, diverting sales from your account to theirs.\n2. **Review bombing** — Counterfeit products generate bad reviews on your ASIN that damage your conversion rate and BSR.\n3. **Account suspension risk** — If Amazon receives too many A-to-Z claims about products \"from your listing\" that you didn't sell, your account can be suspended.\n4. **Brand reputation damage** — Customers who receive counterfeit or sub-standard goods associate the poor experience with your brand.\n5. **Price erosion** — Hijackers selling unauthorized inventory (often gray-market or end-of-life units) at deep discounts undermine your MAP pricing and devalue the brand.\n6. **Slow enforcement loops** — Without documented evidence, enforcement cases get rejected or delayed. This skill builds an evidence package that gets cases resolved.\n7. **Recurrence** — Without prevention systems (Transparency, brand gating), the same hijackers return after removal. This skill closes that loop.\n\n## Workflow\n\n### Step 1 — Set Up Monitoring\nBefore a hijacker appears, set up automated detection:\n- **Amazon Brand Registry**: Use the Brand Dashboard to monitor your ASINs for new sellers.\n- **Seller monitoring tools**: Bindwise, Helium 10 Alerts, or SellerApp send alerts when a new seller appears on your listing.\n- **Manual check** (if no tools): Search your product on Amazon → click the \"New & Used\" offers → record current seller count and seller names.\n\nSet a monitoring cadence: daily for high-volume ASINs, weekly for slower-moving products.\n\n### Step 2 — Identify and Classify the Hijacker\nWhen a new seller appears, classify the violation type:\n- **Counterfeit seller**: Selling fake/replica versions of your product with your brand name.\n- **Unauthorized reseller**: Selling genuine product but without authorization (gray market, overstock, diverted distribution).\n- **Listing pirate**: Created a new listing that copies your images, title, and description to steal your keyword ranking.\n- **ASIN piggyback**: Attached to your ASIN as a third-party seller without any product.\n\nCheck the seller's other listings, feedback history, and location (many hijackers are overseas sellers with new accounts).\n\n### Step 3 — Conduct a Test Buy\nA test buy is the strongest evidence for enforcement. Order the hijacker's product:\n- Use a separate Amazon account (not your brand account)\n- Ship to a neutral address (not your business address)\n- Document everything: order confirmation, shipping details, package arrival photos, product photos vs. your authentic product\n- Keep the packaging, inserts, and product intact for comparison\n\n*Test buys cost money but are often required for Amazon counterfeit enforcement and cease-and-desist legal actions.*\n\n### Step 4 — Build Your Evidence Package\nCompile the following before submitting any enforcement action:\n1. Screenshot of hijacker's offer (including seller name, price, and \"Sold by\" field)\n2. Screenshot of your original listing showing you as the brand owner\n3. Test buy order confirmation and tracking information\n4. Photos: hijacker's product packaging vs. your authentic product\n5. Your trademark registration number (or brand registry enrollment confirmation)\n6. Any proof of MAP violation if the hijacker is an authorized reseller selling below MAP\n\n### Step 5 — Submit Amazon Brand Registry IP Report\nGo to: brand.amazon.com → Report a Violation:\n- Violation type: \"Counterfeit\" for fake products, \"Trademark\" for unauthorized use of your brand name\n- ASIN of the affected listing\n- Infringing seller name/ID\n- Attach evidence (photos, order ID from test buy)\n- Provide trademark registration number\n\nAmazon typically reviews IP reports within 1–5 business days. Counterfeit reports backed by test buys are resolved fastest.\n\n### Step 6 — Send a Cease-and-Desist Letter\nIn parallel with the Brand Registry report, send a C&D to the hijacker:\n- Find seller contact: go to their storefront → click the seller name → \"Ask a question\" (this reaches them via Amazon's messaging system)\n- For the letter: use the template in references/cease-and-desist-template.md\n- State: your trademark rights, the violation, a demand to remove the offer within 48 hours, and consequences of non-compliance\n- CC your legal team or trademark attorney if available\n\n### Step 7 — Escalate if Needed\nIf Amazon's initial enforcement action is rejected or delayed:\n- Re-submit with additional evidence (especially a test buy result if you didn't have one initially)\n- Request escalation to the Amazon Counterfeit Crimes Unit (for repeat offenders)\n- File a DMCA takedown if they've copied your copyrighted images or text\n- Consider sending a formal cease-and-desist from a licensed attorney (carries more weight than self-sent)\n- If the hijacker is a U.S.-based company, a federal trademark infringement letter via certified mail is appropriate\n\n### Step 8 — Implement Prevention Measures\nAfter removing the hijacker, close the loop:\n- **Amazon Transparency**: Enroll products to apply serialized codes to every unit. Unauthorized sellers can't fulfill orders without codes. (Cost: ~$0.01–0.05 per unit)\n- **Brand Gating**: Request Amazon to gate your ASIN — requires approval to list. Available to brand-registered sellers.\n- **Authorized Reseller Policy**: Publish a clear authorized reseller list and make it accessible on your website and Amazon brand store.\n- **MAP Policy**: Establish and enforce a minimum advertised price policy with all authorized resellers.\n\n## Examples\n\n### Example 1 — Counterfeit Seller on Amazon (Electronics Accessory Brand)\n\n**Situation:** Brand selling proprietary phone cases at $24.99. Monitoring alert triggers: 3 new sellers appear on the listing, all pricing at $14.99–16.99.\n\n**Detection:** Seller profiles show all 3 created within the last 60 days, ship from the same region, and have nearly identical feedback text.\n\n**Test buy result:** Products arrive with slightly different packaging, no authenticity card, logo color slightly off, and packaging material noticeably cheaper. Clearly counterfeit.\n\n**Evidence package:**\n- Test buy order ID: 114-XXXXXXX-XXXXXXX\n- Side-by-side product photos showing packaging differences\n- Authentic product invoice from manufacturer\n- Trademark registration #5,XXX,XXX\n\n**Outcome:** Amazon Brand Registry report submitted → All 3 sellers removed within 72 hours. Amazon's Counterfeit Crimes Unit notified due to coordinated nature of attack.\n\n**Prevention added:** Amazon Transparency codes applied to all future production runs.\n\n---\n\n### Example 2 — Unauthorized Reseller Violating MAP (Kitchenware Brand)\n\n**Situation:** Brand sells through 12 authorized retailers. An unauthorized seller appears on Amazon listing at $31.99 — 25% below MAP of $42.99.\n\n**Investigation:** Seller has 4-year history and positive feedback — clearly an unauthorized but legitimate reseller, not a counterfeiter. Likely purchased through a distributor or liquidator.\n\n**Action taken:**\n1. No test buy needed (authentic product, not counterfeit)\n2. Sent Amazon message to seller citing MAP policy and requesting offer removal\n3. Investigated supply chain: traced unauthorized inventory to a regional distributor who sold excess stock to a liquidator\n\n**Outcome:** Seller removed offer within 5 days after receiving the message. Supply chain leak identified and closed by amending distributor agreement to include resale restrictions.\n\n**Note:** Amazon does not enforce MAP directly. Enforcement must come through seller communication and supply chain control — not Brand Registry IP reports (MAP violations alone are not a trademark issue).\n\n---\n\n## Common Mistakes\n\n1. **Reporting without evidence.** Amazon rejects vague reports. You need ASIN, seller ID, specific violation type, and ideally a test buy or trademark registration.\n\n2. **Waiting too long to act.** Hijackers who hold the Buy Box for weeks can generate enough bad reviews to permanently damage your listing's conversion rate.\n\n3. **Confusing MAP violations with counterfeit enforcement.** Amazon doesn't enforce MAP. If an unauthorized reseller is selling authentic goods below MAP, your enforcement path is through seller communication and supply chain control — not trademark reports.\n\n4. **Using your brand account for test buys.** Amazon can see who placed the order. Use a separate personal account.\n\n5. **Ignoring the supply chain leak.** If a legitimate reseller is selling your product without authorization, finding and closing the supply chain leak is more important than the removal itself. Otherwise the inventory keeps appearing.\n\n6. **Not following up after initial removal.** Many hijackers simply return after removal. Monitor the listing for 30 days post-action and be ready to re-file.\n\n7. **Skipping cease-and-desist for counterfeit sellers.** For overseas counterfeiters, a legal letter may not be effective — but it creates a paper trail needed if you escalate to Amazon's Counterfeit Crimes Unit or pursue legal action.\n\n8. **Ignoring review damage from the hijack.** After removing the hijacker, check recent reviews for complaints about product quality that were about counterfeit units. You may be able to request Amazon review removal for reviews about products you didn't sell.\n\n9. **Not enrolling in Amazon Transparency.** It's the only truly preventive solution for Amazon counterfeiting. Without it, hijackers can always return.\n\n10. **Assuming one report is enough for repeat offenders.** Organized counterfeit operations create new seller accounts regularly. Sustained monitoring and repeat reporting is necessary until they give up.\n\n## Resources\n\n- [Output Template](references/output-template.md) — Hijack incident report and enforcement tracker\n- [Cease-and-Desist Template](references/cease-and-desist-template.md) — Draft enforcement letter template\n- [Evidence Collection Guide](references/evidence-collection-guide.md) — Test buy and documentation procedures\n- [Quality Checklist](assets/checklist.md) — Enforcement action readiness checklist\n\nFile v1.0.1:_meta.json\n\n{\n  \"ownerId\": \"kn70fv0ehp50emedet9tx3fekd82pw3b\",\n  \"slug\": \"hijack-defender\",\n  \"version\": \"1.0.1\",\n  \"publishedAt\": 1780756888651\n}\n\nFile v1.0.1:cease-and-desist-template.md\n\n# Cease-and-Desist Letter Templates\n\n## Template A — Amazon Buyer-Seller Messaging (Counterfeit)\n\n**Send via:** Amazon Buyer-Seller Messages (go to seller's storefront → \"Ask a question\")\n\n---\n\nSubject: Notice of Intellectual Property Infringement — Immediate Action Required\n\nDear [Seller Name / Amazon Store Name],\n\nIt has come to our attention that your Amazon seller account ([Seller ID]) is currently offering products on ASIN [ASIN] under the brand name [Your Brand Name] without authorization from [Your Company Name].\n\nWe are the owner of the registered trademark [TRADEMARK NAME], Registration No. [TM NUMBER], registered with the United States Patent and Trademark Office (USPTO). Your listing and/or products constitute:\n\n- Trademark infringement (use of our registered mark without authorization)\n- Unfair competition\n- [If applicable: Counterfeiting of our product and/or packaging]\n\nWe have documented evidence of this infringement, including a test purchase conducted on [DATE], which confirmed the product sold under our brand name does not meet our authenticity standards.\n\n**We demand that you:**\n1. Immediately remove your offer from ASIN [ASIN] and all related listings\n2. Cease all sales of [BRAND NAME] products not purchased from [Your Company Name] or our authorized distributors\n3. Provide written confirmation of compliance within 48 hours of this notice\n\nFailure to comply will result in formal trademark infringement claims filed with Amazon Brand Registry, as well as potential legal action including claims for actual damages, statutory damages of up to $2,000,000 per counterfeit mark under 15 U.S.C. § 1117, attorney's fees, and injunctive relief.\n\nThis letter is not a complete statement of all rights or claims we may have, all of which are expressly reserved.\n\nSincerely,\n\n[Your Name]\n[Title]\n[Company Name]\n[Contact Email]\n[Date]\n\n---\n\n## Template B — Amazon Messaging (Unauthorized Reseller / MAP Violation)\n\nSubject: Unauthorized Resale of [Brand Name] Products\n\nDear [Seller Name],\n\nWe have identified that your Amazon seller account is currently listing [Brand Name] products on ASIN [ASIN] at a price of $[PRICE], which is below our Minimum Advertised Price (MAP) of $[MAP PRICE] and/or without authorization to resell [Brand Name] products.\n\n[Brand Name] products are sold exclusively through our authorized retail partners. Your account does not appear on our list of authorized resellers.\n\nWe request that you:\n1. Immediately remove your offer from ASIN [ASIN]\n2. Provide information about the source of your [Brand Name] inventory (invoice or purchase records)\n\nWe are actively investigating the source of unauthorized [Brand Name] inventory in the market and will take appropriate steps to address supply chain violations. Your cooperation in identifying your source will be taken into account.\n\nPlease respond within 48 hours.\n\nSincerely,\n\n[Your Name]\n[Company Name]\n[Contact Email]\n[Date]\n\n---\n\n## Template C — Formal Legal Letter (Attorney-Ready Template)\n\n*Note: Have this reviewed by a licensed trademark attorney before sending. This version is appropriate for serious or repeat infringers, U.S.-based sellers, or when legal action is imminent.*\n\n---\n\n[ATTORNEY LETTERHEAD OR COMPANY LETTERHEAD]\n[Date]\n\nVIA CERTIFIED MAIL / EMAIL\n\n[Seller/Company Name]\n[Address if known]\n[Email if known]\n\n**RE: Trademark Infringement and Demand for Immediate Cessation — [BRAND NAME]**\n\nTo Whom It May Concern:\n\nThis firm represents [Client Company Name] (\"Client\"), the owner of the registered trademark [TRADEMARK NAME] (U.S. Trademark Registration No. [NUMBER]) for use in connection with [product category].\n\nIt has come to our client's attention that [Infringer Name] (\"You\") has been selling, offering for sale, and/or distributing products under the [BRAND NAME] trademark via Amazon.com (ASIN: [ASIN]) and/or through [other channels] without authorization from our client.\n\n**Your actions constitute:**\n1. Federal trademark infringement under 15 U.S.C. § 1114\n2. Unfair competition under 15 U.S.C. § 1125(a)\n3. [If applicable] Counterfeiting under 15 U.S.C. § 1116(d)\n4. [State law claims as applicable]\n\nOur client has conducted a test purchase and confirmed that the product sold under the [BRAND NAME] trademark is [counterfeit / not authorized / otherwise in violation]. Documentation is maintained.\n\n**Pursuant to this letter, we demand that you:**\n1. Immediately cease all sales, offers for sale, advertising, or distribution of any product bearing the [BRAND NAME] mark\n2. Destroy or return all [BRAND NAME]-branded inventory in your possession\n3. Provide within 10 business days: (a) an accounting of all sales of [BRAND NAME] products, (b) the source of your [BRAND NAME] inventory, and (c) written confirmation of compliance with the above demands\n4. Pay all profits derived from your unauthorized use of our client's trademark\n\nOur client reserves all rights, including the right to seek statutory damages of up to $2,000,000 per counterfeit mark, actual damages, disgorgement of profits, attorney's fees, and injunctive relief.\n\nThis demand is not exhaustive of our client's rights or claims, all of which are expressly reserved. Please govern yourself accordingly.\n\nSincerely,\n\n[Attorney Name]\n[Law Firm Name]\n[State Bar Number]\n[Contact Information]\n\n---\n\n## Notes on Template Selection\n\n| Scenario | Recommended Template |\n|---------|---------------------|\n| First contact with suspected counterfeiter via Amazon | Template A |\n| First contact with unauthorized reseller | Template B |\n| Repeat infringer who ignored Template A | Template C (attorney review recommended) |\n| Overseas seller | Template A + Amazon Brand Registry IP report (legal letters less effective cross-border) |\n| High-volume infringement causing significant revenue loss | Template C + legal action |\n\nFile v1.0.1:checklist.md\n\n# Hijack Defender — Enforcement Readiness Checklist\n\nUse this checklist before submitting any enforcement action. Incomplete evidence packages lead to rejected cases and allow the hijacker to continue operating.\n\n---\n\n## 1. Detection & Classification (5 items)\n- [ ] Hijacker identified with full seller name and seller ID captured\n- [ ] Violation type classified: Counterfeit / Unauthorized Reseller / Listing Copy / ASIN Piggyback\n- [ ] Hijacker's price vs. your price documented\n- [ ] Hijacker's seller account age and feedback rating noted\n- [ ] Detection date logged (for measuring time-to-resolution later)\n\n## 2. Evidence — Listing Documentation (6 items)\n- [ ] Screenshot of hijacker's offer page (seller name, price, \"Sold by\" field visible)\n- [ ] Screenshot of your listing showing you as brand owner\n- [ ] Screenshot of \"All Offers\" display showing the specific hijacker offer\n- [ ] Hijacker's seller profile and feedback page captured\n- [ ] Date/timestamp visible in all screenshots\n- [ ] All screenshots labeled with ASIN, seller name, and date\n\n## 3. Evidence — Brand Documentation (4 items)\n- [ ] Trademark registration number confirmed (USPTO TESS or equivalent)\n- [ ] Brand Registry enrollment confirmation on hand\n- [ ] Manufacturer invoice or purchase order confirming you as authorized seller\n- [ ] Authorized reseller list reviewed (is this seller on it? If yes, investigate MAP/contract violation separately)\n\n## 4. Test Buy (for Counterfeit Cases) (7 items)\n- [ ] Test buy placed from a separate non-brand Amazon account\n- [ ] Order shipped to a neutral address (not brand business address)\n- [ ] Order ID documented\n- [ ] Package exterior photographed upon arrival\n- [ ] Side-by-side product comparison photos taken (authentic vs. received)\n- [ ] Packaging, inserts, and all materials preserved\n- [ ] Comparison photos clearly labeled: \"authentic\" vs. \"hijacker\"\n\n## 5. Amazon Brand Registry Report (6 items)\n- [ ] Report submitted at brand.amazon.com → Report a Violation\n- [ ] Correct violation type selected (Counterfeit vs. Trademark)\n- [ ] ASIN and infringing seller URL provided\n- [ ] Trademark registration number included\n- [ ] Evidence photos attached (4–8 photos, clearly labeled)\n- [ ] Case reference number saved\n\n## 6. Cease-and-Desist (4 items)\n- [ ] C&D message sent via Amazon Buyer-Seller Messaging to hijacker\n- [ ] Template customized with ASIN, trademark number, and specific violation details\n- [ ] 48-hour deadline stated in the message\n- [ ] Copy of sent message saved (screenshot or download)\n\n## 7. Post-Resolution (6 items)\n- [ ] Hijacker's offer confirmed removed from listing\n- [ ] Reviews posted during hijack period reviewed for counterfeit complaints\n- [ ] Review removal requests filed for reviews about products seller didn't ship\n- [ ] Monitoring continued for 30 days post-removal (hijacker may return)\n- [ ] Estimated revenue lost during hijack period calculated\n- [ ] Incident logged in tracker with resolution date and method\n\n## 8. Prevention (5 items)\n- [ ] Amazon Transparency enrollment status reviewed / initiated\n- [ ] Brand Gating request filed for affected ASIN (if not already gated)\n- [ ] Supply chain investigation launched (how did the unauthorized inventory get there?)\n- [ ] Supply chain leak closed (distributor agreement, liquidation channel, etc.)\n- [ ] Authorized reseller policy published and accessible\n\n---\n\n**Total items: 43**\n**Minimum before submitting a counterfeit report: Sections 1–4 complete**\n**Minimum before submitting an unauthorized reseller report: Sections 1–3 complete (no test buy required)**\n\nFile v1.0.1:evidence-collection-guide.md\n\n# Evidence Collection Guide — Listing Hijack Cases\n\n## Why Evidence Quality Determines Enforcement Speed\n\nAmazon resolves IP complaints on a tiered basis:\n- **Tier 1 (resolved in 1–3 days):** Trademark + test buy + photos showing clear counterfeiting\n- **Tier 2 (resolved in 3–7 days):** Trademark + screenshots showing unauthorized brand use\n- **Tier 3 (resolved in 7–30 days or rejected):** Screenshots only, no trademark, vague description\n\nBuild Tier 1 evidence packages for every counterfeit case.\n\n---\n\n## Test Buy Protocol\n\n### Before the Purchase\n1. Create a dedicated \"test buy\" Amazon account separate from your brand account and any personal accounts. Use a neutral email address.\n2. Use a shipping address that is not your business address (team member's home, P.O. Box, or package forwarding service).\n3. Screenshot the listing before purchasing: show seller name, price, \"Sold by\" field, all listing images, and the date in the URL bar.\n4. Note the specific offer you're buying (if multiple sellers exist, select the hijacker's offer explicitly).\n\n### During the Order\n- Screenshot the checkout screen showing: seller name, price, and estimated delivery.\n- Note the order ID (format: 114-XXXXXXX-XXXXXXX).\n- Screenshot the order confirmation email.\n\n### Upon Delivery\nDocument the following the moment the package arrives — do not open fully until you're ready to photograph:\n\n**Package exterior:**\n- Photo of the package as received (all sides)\n- Photo showing return address label (seller's ship-from location)\n- Photo showing your order confirmation number on the packing slip\n\n**Product comparison photos (authentic vs. hijacker):**\n- Side-by-side packaging (front, back, sides)\n- Logo comparison (color accuracy, font, placement)\n- Barcode / UPC comparison (they often match but product inside differs)\n- Any authentication features: holographic stickers, serial numbers, QR codes\n- Inner packaging: foam, inserts, accessories, documentation\n- Product itself: material quality, construction, color accuracy\n- Any authenticity cards or certificates (present in authentic, absent or different in counterfeit)\n\n**Product testing (if safe and applicable):**\n- Weight comparison (counterfeits are often lighter)\n- Performance test documentation (e.g., battery life, output quality)\n- Ingredient or material discrepancy (for consumables or skincare)\n\n### What to Preserve\n- The entire package, product, and all materials in the original received state\n- Digital photos organized by category (see above)\n- Order confirmation email as PDF\n- Tracking information from delivery\n\n*Do NOT dispose of any test buy materials until the enforcement case is fully resolved and any legal threats have passed.*\n\n---\n\n## Screenshot Documentation Checklist\n\nFor every hijack incident, capture and label the following screenshots:\n\n### Listing Screenshots\n- [ ] Full listing page showing: title, brand, images, price, \"Sold by [Hijacker Name]\" field\n- [ ] \"All Offers\" display showing the hijacker's offer selected\n- [ ] Hijacker's seller profile page (storefront)\n- [ ] Hijacker's feedback page (account age, feedback count, rating, recent reviews)\n- [ ] Date visible in browser: use URL bar or open a second tab with google.com → search today's date\n\n### Your Brand Documentation\n- [ ] Your Amazon Brand Registry enrollment page (or confirmation email)\n- [ ] Your product's ASIN on Amazon with you as the listed brand\n- [ ] Your trademark registration certificate (from USPTO TESS or equivalent)\n- [ ] Your product's manufacturer invoice or purchase order (shows you as the authorized seller)\n\n### Post-Submission\n- [ ] Amazon Brand Registry report submission confirmation (case number)\n- [ ] Any Amazon responses to the case\n- [ ] Seller's response to your cease-and-desist message (screenshot from Amazon messaging)\n\n---\n\n## Organizing Your Evidence Package\n\n### Folder Structure\n```\n/hijack-evidence/\n  /[ASIN]-[SellerName]-[Date]/\n    /listing-screenshots/\n      listing-overview.png\n      all-offers.png\n      seller-profile.png\n      seller-feedback.png\n    /test-buy/\n      order-confirmation.pdf\n      package-exterior.jpg\n      product-comparison-front.jpg\n      product-comparison-back.jpg\n      logo-closeup-authentic-vs-counterfeit.jpg\n      [additional comparison photos]\n    /brand-documentation/\n      trademark-registration.pdf\n      brand-registry-enrollment.pdf\n      manufacturer-invoice.pdf\n    /enforcement/\n      amazon-report-confirmation.pdf\n      cease-and-desist-sent.pdf\n      amazon-responses.pdf\n```\n\n### Naming Convention\n`[ASIN]_[SellerID]_[Date]_[EvidenceType]`\n\nExample: `B08XYZ1234_A3SELLER987_2026-06-06_listing-screenshot.png`\n\n---\n\n## Amazon Brand Registry IP Report — Field Guide\n\n**Where:** brand.amazon.com → Protect → Report a Violation\n\n| Field | What to Enter |\n|-------|---------------|\n| Violation type | \"Counterfeit\" if product is fake; \"Trademark\" if brand name is used without authorization |\n| ASIN | The ASIN of your listing being hijacked |\n| Infringing product URL | Direct URL to the hijacker's offer page (copy from \"All Offers\" display) |\n| Seller name | Exact seller name as shown on Amazon |\n| Your trademark | Enter your U.S. trademark registration number (or international equivalent) |\n| Evidence description | Brief factual description: \"Test purchase conducted [date], order [ID]. Product received differs from authentic product in [specific ways]. Photos attached.\" |\n| Attachments | Upload: listing screenshot, comparison photos, order confirmation |\n\n**Tips for faster resolution:**\n- Keep the description factual and specific — avoid vague language like \"looks fake\"\n- Reference the test buy order ID explicitly\n- Upload 4–6 clearly labeled photos, not 20 unlabeled images\n- Submit separate reports for each seller (don't combine multiple sellers in one report)\n\n---\n\n## Escalation Paths\n\n| Situation | Escalation Action |\n|-----------|------------------|\n| Amazon report rejected (no TM found) | Confirm TM registration status on USPTO.gov; resubmit with registration certificate attached |\n| Amazon report rejected (insufficient evidence) | Conduct test buy, resubmit with test buy evidence |\n| Case resolved but seller returns within 30 days | Resubmit with note \"Repeat infringer — previously removed on [case #]\" |\n| Multiple sellers on same listing (organized attack) | Flag as potential coordinated infringement ring; request Counterfeit Crimes Unit referral |\n| Seller is large enough to have legal representation | Escalate to your trademark attorney; consider federal court filing |\n| Product appears on Alibaba/AliExpress as well | File separate takedown on those platforms; may indicate factory-level counterfeiting |\n\nFile v1.0.1:output-template.md\n\n# Hijack Defender — Incident Report & Enforcement Tracker\n\n## Incident Overview\n**Brand:** [Brand Name]\n**ASIN(s) Affected:** [ASIN]\n**Product Name:** [Product Name]\n**Detection Date:** [Date]\n**Detection Method:** [Alert tool / Manual check]\n**Incident Severity:** [Critical / High / Medium / Low]\n\n---\n\n## Hijacker Profile\n\n| Field | Details |\n|-------|---------|\n| Seller Name | [Name] |\n| Seller ID | [ID] |\n| Marketplace | amazon.com / amazon.co.uk / [other] |\n| Listing Price | $[N] |\n| Your Price | $[N] |\n| Price Difference | −$[N] ([%] below) |\n| Seller Account Age | [N] months/years |\n| Seller Feedback Count | [N] |\n| Seller Feedback Rating | [%] |\n| Seller Location (if visible) | [Country/Region] |\n| Violation Type | Counterfeit / Unauthorized Reseller / Listing Copy / ASIN Piggyback |\n\n---\n\n## Evidence Log\n\n| Evidence Item | Status | Date Captured | Notes |\n|--------------|--------|---------------|-------|\n| Screenshot: hijacker's offer page | ✅ / ❌ | [Date] | |\n| Screenshot: your original listing (brand owner) | ✅ / ❌ | [Date] | |\n| Test buy placed | ✅ / ❌ | [Date] | Order ID: [ID] |\n| Test buy received | ✅ / ❌ | [Date] | |\n| Counterfeit product photos (vs. authentic) | ✅ / ❌ | [Date] | |\n| Authentic product invoice from manufacturer | ✅ / ❌ | [Date] | |\n| Trademark registration number | ✅ / ❌ | [Date] | TM #[N] |\n| Brand Registry enrollment confirmation | ✅ / ❌ | [Date] | |\n\n---\n\n## Enforcement Actions Log\n\n| Action | Date | Status | Case/Reference # | Notes |\n|--------|------|--------|-----------------|-------|\n| Amazon Brand Registry IP Report submitted | [Date] | Pending / Resolved / Rejected | [Case #] | |\n| Cease-and-desist sent to seller | [Date] | Sent / Acknowledged / Ignored | | |\n| DMCA takedown (if images copied) | [Date] | Pending / Resolved | | |\n| Escalation to Counterfeit Crimes Unit | [Date] | Pending / Resolved | | |\n| Legal team notified | [Date] | Yes / No | | |\n| Supply chain investigation launched | [Date] | Pending / Resolved | | |\n\n---\n\n## Resolution\n\n| Field | Details |\n|-------|---------|\n| Date hijacker removed | [Date] |\n| Method of removal | Brand Registry / Seller self-removed / Amazon action / Other |\n| Days from detection to removal | [N] |\n| Reviews affected (bad reviews during hijack period) | [N] reviews, avg [rating] |\n| Review removal requests filed | [Y/N] |\n| Estimated lost sales during hijack | [N] units × $[AOV] = $[N] |\n\n---\n\n## Post-Incident Prevention Actions\n\n| Prevention Measure | Status | Target Date |\n|-------------------|--------|-------------|\n| Amazon Transparency enrollment | Enrolled / In Progress / Not started | [Date] |\n| Brand Gating request submitted | Yes / No | [Date] |\n| Supply chain leak identified | Yes / No / Under investigation | [Date] |\n| Supply chain leak closed | Yes / No | [Date] |\n| Authorized reseller list updated/published | Yes / No | [Date] |\n| MAP policy reinforced with all distributors | Yes / No | [Date] |\n\n---\n\n## Open Incidents Tracker\n\n| ASIN | Product | Hijacker | Detected | Status | Priority |\n|------|---------|---------|----------|--------|----------|\n| [ASIN] | [Name] | [Seller] | [Date] | Active / Resolved | High / Med / Low |\n\nFile v1.0.1:skill-card.md\n\n## Description: <br>\nDetect, document, and remove unauthorized third-party sellers hijacking your Amazon listings or ecommerce product pages with step-by-step enforcement workflows for brand registry, cease-and-desist, and test buy procedures. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[leooooooow](https://clawhub.ai/user/leooooooow) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nExternal brand owners, ecommerce operators, and marketplace enforcement teams use this skill to detect listing hijackers, organize evidence, submit marketplace enforcement actions, and prepare cease-and-desist communications. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Users may treat enforcement templates or marketplace reporting guidance as legal advice. <br>\nMitigation: Have legal or compliance staff review cease-and-desist letters, DMCA claims, marketplace reports, and escalation decisions before sending. <br>\nRisk: Test buys and evidence packages can expose personal addresses, account details, order identifiers, or other sensitive information. <br>\nMitigation: Use approved investigation accounts and company-controlled or consent-based delivery locations, and redact or restrict PII in evidence files. <br>\nRisk: Incomplete or poorly labeled evidence can delay or weaken marketplace enforcement actions. <br>\nMitigation: Follow the evidence collection guide and readiness checklist before submitting reports or contacting sellers. <br>\n\n\n## Reference(s): <br>\n- [Hijack Defender Skill](SKILL.md) <br>\n- [Incident Report and Enforcement Tracker](output-template.md) <br>\n- [Cease-and-Desist Letter Templates](cease-and-desist-template.md) <br>\n- [Evidence Collection Guide](evidence-collection-guide.md) <br>\n- [Enforcement Readiness Checklist](checklist.md) <br>\n- [ClawHub Skill Page](https://clawhub.ai/leooooooow/hijack-defender) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, guidance] <br>\n**Output Format:** [Markdown guidance, checklists, and reusable enforcement templates] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Documentation-only workflow; no tool calls, shell commands, or code execution are required.] <br>\n\n## Skill Version(s): <br>\n1.0.1 (source: server-resolved release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.0: 3 files, 3928 bytes\n\nFiles: skill-card.md (2557b), SKILL.md (5085b), _meta.json (134b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: hijack-defender\ndescription: Create a monitoring and response plan for Amazon listing hijacking, including detection triggers, Brand Registry escalation steps, and counterfeit removal procedures via Project Zero and Transparency.\n---\n\n# Hijack Defender\n\nListing hijacking on Amazon — where unauthorized sellers attach themselves to your ASIN and sell counterfeit or grey-market products — erodes your brand, tanks your reviews, and steals your Buy Box. Hijack Defender builds a complete monitoring and rapid-response playbook so you can detect hijackers early, remove them through the correct Amazon enforcement channels, and put preventive measures in place to stop it from happening again.\n\n## Use when\n\n- You discover an unknown seller has appeared on one of your Amazon ASINs and is winning the Buy Box with a suspiciously low price or shipping counterfeit units\n- You want to build a proactive hijack monitoring system before a problem occurs, especially if you sell high-demand products in categories prone to counterfeiting\n- You are enrolled in Amazon Brand Registry and need a step-by-step escalation workflow for filing IP complaints, using Project Zero self-service removal, or enrolling ASINs in the Transparency program\n- Your customer reviews have suddenly started mentioning quality issues or wrong items received, which may indicate a hijacker is fulfilling orders with inferior products under your listing\n\n## What this skill does\n\nThis skill generates a comprehensive anti-hijacking playbook tailored to your brand and catalog. It covers three phases: detection, response, and prevention. For detection, it defines what monitoring signals to watch (new seller appearances, Buy Box loss, review sentiment shifts, pricing anomalies) and how to set up alerts. For response, it produces step-by-step escalation procedures through Amazon Brand Registry Report a Violation tool, Project Zero counterfeit removal, and Transparency program enrollment. For prevention, it recommends long-term protective measures including unique product identifiers, packaging authentication, and legal cease-and-desist templates. The playbook is specific to your ASINs, brand registry status, and the type of hijacking you are experiencing or want to prevent.\n\n## Inputs required\n\n- **Brand name and ASIN list** (required): Your brand name as registered in Amazon Brand Registry and the ASINs you want to protect or that are currently being hijacked. Example: \"Brand: AquaPure, ASINs: B08XYZ1234, B09ABC5678\"\n- **Brand Registry status** (required): Whether you are enrolled in Amazon Brand Registry (and which tier), Project Zero, or Transparency. Example: \"Brand Registry 2.0 enrolled, not yet on Project Zero or Transparency\"\n- **Current hijacking situation** (optional): Details about any active hijacking incident — the unauthorized seller name, what they are selling, pricing differences, and any customer complaints. Example: \"Seller 'BestDeals99' appeared on B08XYZ1234 two days ago, priced $5 below our MAP, and three customers reported receiving a different product\"\n- **Product category and price range** (optional): Helps tailor the risk assessment and prevention recommendations. Example: \"Health supplements, $25-45 per unit\"\n\n## Output format\n\nThe output is a structured Hijack Defense Playbook divided into four major sections. First, a **Risk Assessment** that evaluates your current exposure based on product category, price point, and existing protections, assigning a risk level (high, medium, low) to each ASIN. Second, a **Detection Protocol** with specific monitoring steps including how to set up automated alerts for new seller appearances on your ASINs, Buy Box monitoring cadence, and review sentiment tripwires, with recommended free and paid tools for each. Third, a **Response Escalation Ladder** with exact step-by-step instructions for each enforcement channel — starting with a direct seller warning, then Brand Registry Report a Violation filing (with field-by-field guidance), Project Zero self-service takedown procedures, Transparency enrollment steps, and when to escalate to Amazon Seller Support or pursue legal action. Fourth, a **Prevention Checklist** covering Transparency barcode enrollment, unique packaging markers, MAP policy enforcement, authorized reseller agreements, and ongoing monitoring cadence to keep your listings clean long-term.\n\n## Scope\n\n- Designed for: Amazon private label sellers, brand owners, and brand protection managers\n- Platform context: Amazon (US, EU, and other Amazon marketplaces with Brand Registry support)\n- Language: English\n\n## Limitations\n\n- Cannot file Brand Registry complaints, Project Zero removals, or Transparency enrollments on your behalf; the playbook provides instructions you execute in Seller Central\n- Does not provide legal advice; cease-and-desist templates are starting points and should be reviewed by an attorney before sending\n- Detection recommendations rely on tools and manual checks; this skill does not connect to live Amazon data or monitor your listings in real time\n\nFile v1.0.0:_meta.json\n\n{\n  \"ownerId\": \"kn70fv0ehp50emedet9tx3fekd82pw3b\",\n  \"slug\": \"hijack-defender\",\n  \"version\": \"1.0.0\",\n  \"publishedAt\": 1776309739454\n}\n\nFile v1.0.0:skill-card.md\n\n## Description: <br>\nCreate a monitoring and response plan for Amazon listing hijacking, including detection triggers, Brand Registry escalation steps, and counterfeit removal procedures via Project Zero and Transparency. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[leooooooow](https://clawhub.ai/user/leooooooow) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nAmazon private label sellers, brand owners, and brand protection managers use this skill to create a tailored playbook for detecting listing hijackers, escalating through Amazon enforcement channels, and planning longer-term prevention steps. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Prompts for this skill may include sensitive Amazon account, customer, or incident details. <br>\nMitigation: Use sanitized ASIN and incident details and do not include Amazon credentials, session tokens, private account screenshots, or sensitive customer data. <br>\nRisk: The playbook may include enforcement or legal-language guidance that can become outdated or may not fit a specific dispute. <br>\nMitigation: Verify Amazon procedure steps against current Seller Central and Brand Registry workflows, and have cease-and-desist language reviewed by qualified legal counsel before use. <br>\nRisk: The skill cannot file complaints, remove sellers, enroll ASINs, or monitor Amazon listings in real time. <br>\nMitigation: Treat the output as a planning aid and execute any Brand Registry, Project Zero, Transparency, Seller Support, or monitoring actions through the appropriate Amazon tools. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/leooooooow/hijack-defender) <br>\n- [Publisher profile](https://clawhub.ai/user/leooooooow) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Analysis, Markdown, Guidance, Configuration] <br>\n**Output Format:** [Structured Markdown playbook] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Produces a risk assessment, detection protocol, response escalation ladder, and prevention checklist; it does not take action in Amazon Seller Central.] <br>\n\n## Skill Version(s): <br>\n1.0.0 (source: server release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>","readmeExcerpt":"Skill: Hijack Defender Owner: leooooooow Summary: Detect, document, and remove unauthorized third-party sellers hijacking your Amazon listings or ecommerce product pages — with step-by-step enforcement workf... Tags: latest:1.1.0 Version history: v1.1.0 | 2026-06-06T14:44:17.046Z | user No changes detected in version 1.0.2. - No updates have been made to the skill files. - All functionality and documentation remain t","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"/hijack-evidence/\n  /[ASIN]-[SellerName]-[Date]/\n    /listing-screenshots/\n      listing-overview.png\n      all-offers.png\n      seller-profile.png\n      seller-feedback.png\n    /test-buy/\n      order-confirmation.pdf\n      package-exterior.jpg\n      product-comparison-front.jpg\n      product-comparison-back.jpg\n      logo-closeup-authentic-vs-counterfeit.jpg\n      [additional comparison photos]\n    /brand-documentation/\n      trademark-registration.pdf\n      brand-registry-enrollment.pdf\n      manufacturer-invoice.pdf\n    /enforcement/\n      amazon-report-confirmation.pdf\n      cease-and-desist-sent.pdf\n      amazon-responses.pdf"},{"language":"text","snippet":"/hijack-evidence/\n  /[ASIN]-[SellerName]-[Date]/\n    /listing-screenshots/\n      listing-overview.png\n      all-offers.png\n      seller-profile.png\n      seller-feedback.png\n    /test-buy/\n      order-confirmation.pdf\n      package-exterior.jpg\n      product-comparison-front.jpg\n      product-comparison-back.jpg\n      logo-closeup-authentic-vs-counterfeit.jpg\n      [additional comparison photos]\n    /brand-documentation/\n      trademark-registration.pdf\n      brand-registry-enrollment.pdf\n      manufacturer-invoice.pdf\n    /enforcement/\n      amazon-report-confirmation.pdf\n      cease-and-desist-sent.pdf\n      amazon-responses.pdf"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: Hijack Defender\ndescription: Detect, document, and remove unauthorized third-party sellers hijacking your Amazon listings or ecommerce product pages — with step-by-step enforcement workflows for brand registry, cease-and-desist, and test buy procedures.\n---\n\n# Hijack Defender\n\nListing hijacking happens when an unauthorized seller attaches to your Amazon ASIN (or copies your product page on other marketplaces) and sells counterfeit, unauthorized, or gray-market goods under your brand name. It destroys customer trust, tanks your reviews, and can get your listing suppressed when Amazon receives complaints about products you didn't sell. This skill walks you through detecting hijackers, documenting the violation, submitting enforcement actions, and preventing future attacks.\n\n## Quick Reference\n\n| Decision | Strong | Acceptable | Weak |\n|----------|--------|------------|------|\n| Detection method | Automated monitoring + daily alerts | Weekly manual checks | Reactive (noticing after damage is done) |\n| Evidence standard | Test buy + photos + invoices vs. yours | Photos only | Screenshots only |\n| Enforcement route | Amazon Brand Registry IP report | Case to Seller Support | Public seller feedback only |\n| Cease-and-desist | Attorney-reviewed template | DIY template | Verbal warning only |\n| Time to action | Within 24h of detection | 2–3 days | Week+ |\n| Prevention | Transparency program + brand registry | Brand registry only | No proactive measures |\n\n## Solves\n\n1. **Lost Buy Box** — Hijackers who undercut your price steal the Buy Box, diverting sales from your account to theirs.\n2. **Review bombing** — Counterfeit products generate bad reviews on your ASIN that damage your conversion rate and BSR.\n3. **Account suspension risk** — If Amazon receives too many A-to-Z claims about products \"from your listing\" that you didn't sell, your account can be suspended.\n4. **Brand reputation damage** — Customers who receive counterfeit or sub-standard goods associate the poor experience with your brand.\n5. **Price erosion** — Hijackers selling unauthorized inventory (often gray-market or end-of-life units) at deep discounts undermine your MAP pricing and devalue the brand.\n6. **Slow enforcement loops** — Without documented evidence, enforcement cases get rejected or delayed. This skill builds an evidence package that gets cases resolved.\n7. **Recurrence** — Without prevention systems (Transparency, brand gating), the same hijackers return after removal. This skill closes that loop.\n\n## Workflow\n\n### Step 1 — Set Up Monitoring\nBefore a hijacker appears, set up automated detection:\n- **Amazon Brand Registry**: Use the Brand Dashboard to monitor your ASINs for new sellers.\n- **Seller monitoring tools**: Bindwise, Helium 10 Alerts, or SellerApp send alerts when a new seller appears on your listing.\n- **Manual check** (if no tools): Search your product on Amazon → click the \"New & Used\" offers → record current seller count and seller names.\n\nSet a monitorin"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn70fv0ehp50emedet9tx3fekd82pw3b\",\n  \"slug\": \"hijack-defender\",\n  \"version\": \"1.1.0\",\n  \"publishedAt\": 1780757057046\n}"},{"path":"cease-and-desist-template.md","content":"# Cease-and-Desist Letter Templates\n\n## Template A — Amazon Buyer-Seller Messaging (Counterfeit)\n\n**Send via:** Amazon Buyer-Seller Messages (go to seller's storefront → \"Ask a question\")\n\n---\n\nSubject: Notice of Intellectual Property Infringement — Immediate Action Required\n\nDear [Seller Name / Amazon Store Name],\n\nIt has come to our attention that your Amazon seller account ([Seller ID]) is currently offering products on ASIN [ASIN] under the brand name [Your Brand Name] without authorization from [Your Company Name].\n\nWe are the owner of the registered trademark [TRADEMARK NAME], Registration No. [TM NUMBER], registered with the United States Patent and Trademark Office (USPTO). Your listing and/or products constitute:\n\n- Trademark infringement (use of our registered mark without authorization)\n- Unfair competition\n- [If applicable: Counterfeiting of our product and/or packaging]\n\nWe have documented evidence of this infringement, including a test purchase conducted on [DATE], which confirmed the product sold under our brand name does not meet our authenticity standards.\n\n**We demand that you:**\n1. Immediately remove your offer from ASIN [ASIN] and all related listings\n2. Cease all sales of [BRAND NAME] products not purchased from [Your Company Name] or our authorized distributors\n3. Provide written confirmation of compliance within 48 hours of this notice\n\nFailure to comply will result in formal trademark infringement claims filed with Amazon Brand Registry, as well as potential legal action including claims for actual damages, statutory damages of up to $2,000,000 per counterfeit mark under 15 U.S.C. § 1117, attorney's fees, and injunctive relief.\n\nThis letter is not a complete statement of all rights or claims we may have, all of which are expressly reserved.\n\nSincerely,\n\n[Your Name]\n[Title]\n[Company Name]\n[Contact Email]\n[Date]\n\n---\n\n## Template B — Amazon Messaging (Unauthorized Reseller / MAP Violation)\n\nSubject: Unauthorized Resale of [Brand Name] Products\n\nDear [Seller Name],\n\nWe have identified that your Amazon seller account is currently listing [Brand Name] products on ASIN [ASIN] at a price of $[PRICE], which is below our Minimum Advertised Price (MAP) of $[MAP PRICE] and/or without authorization to resell [Brand Name] products.\n\n[Brand Name] products are sold exclusively through our authorized retail partners. Your account does not appear on our list of authorized resellers.\n\nWe request that you:\n1. Immediately remove your offer from ASIN [ASIN]\n2. Provide information about the source of your [Brand Name] inventory (invoice or purchase records)\n\nWe are actively investigating the source of unauthorized [Brand Name] inventory in the market and will take appropriate steps to address supply chain violations. Your cooperation in identifying your source will be taken into account.\n\nPlease respond within 48 hours.\n\nSincerely,\n\n[Your Name]\n[Company Name]\n[Contact Email]\n[Date]\n\n---\n\n## Template C — Formal Legal Letter (Attorney-Ready Templ"},{"path":"checklist.md","content":"# Hijack Defender — Enforcement Readiness Checklist\n\nUse this checklist before submitting any enforcement action. Incomplete evidence packages lead to rejected cases and allow the hijacker to continue operating.\n\n---\n\n## 1. Detection & Classification (5 items)\n- [ ] Hijacker identified with full seller name and seller ID captured\n- [ ] Violation type classified: Counterfeit / Unauthorized Reseller / Listing Copy / ASIN Piggyback\n- [ ] Hijacker's price vs. your price documented\n- [ ] Hijacker's seller account age and feedback rating noted\n- [ ] Detection date logged (for measuring time-to-resolution later)\n\n## 2. Evidence — Listing Documentation (6 items)\n- [ ] Screenshot of hijacker's offer page (seller name, price, \"Sold by\" field visible)\n- [ ] Screenshot of your listing showing you as brand owner\n- [ ] Screenshot of \"All Offers\" display showing the specific hijacker offer\n- [ ] Hijacker's seller profile and feedback page captured\n- [ ] Date/timestamp visible in all screenshots\n- [ ] All screenshots labeled with ASIN, seller name, and date\n\n## 3. Evidence — Brand Documentation (4 items)\n- [ ] Trademark registration number confirmed (USPTO TESS or equivalent)\n- [ ] Brand Registry enrollment confirmation on hand\n- [ ] Manufacturer invoice or purchase order confirming you as authorized seller\n- [ ] Authorized reseller list reviewed (is this seller on it? If yes, investigate MAP/contract violation separately)\n\n## 4. Test Buy (for Counterfeit Cases) (7 items)\n- [ ] Test buy placed from a separate non-brand Amazon account\n- [ ] Order shipped to a neutral address (not brand business address)\n- [ ] Order ID documented\n- [ ] Package exterior photographed upon arrival\n- [ ] Side-by-side product comparison photos taken (authentic vs. received)\n- [ ] Packaging, inserts, and all materials preserved\n- [ ] Comparison photos clearly labeled: \"authentic\" vs. \"hijacker\"\n\n## 5. Amazon Brand Registry Report (6 items)\n- [ ] Report submitted at brand.amazon.com → Report a Violation\n- [ ] Correct violation type selected (Counterfeit vs. Trademark)\n- [ ] ASIN and infringing seller URL provided\n- [ ] Trademark registration number included\n- [ ] Evidence photos attached (4–8 photos, clearly labeled)\n- [ ] Case reference number saved\n\n## 6. Cease-and-Desist (4 items)\n- [ ] C&D message sent via Amazon Buyer-Seller Messaging to hijacker\n- [ ] Template customized with ASIN, trademark number, and specific violation details\n- [ ] 48-hour deadline stated in the message\n- [ ] Copy of sent message saved (screenshot or download)\n\n## 7. Post-Resolution (6 items)\n- [ ] Hijacker's offer confirmed removed from listing\n- [ ] Reviews posted during hijack period reviewed for counterfeit complaints\n- [ ] Review removal requests filed for reviews about products seller didn't ship\n- [ ] Monitoring continued for 30 days post-removal (hijacker may return)\n- [ ] Estimated revenue lost during hijack period calculated\n- [ ] Incident logged in tracker with resolution date and method\n\n## 8. Preve"},{"path":"evidence-collection-guide.md","content":"# Evidence Collection Guide — Listing Hijack Cases\n\n## Why Evidence Quality Determines Enforcement Speed\n\nAmazon resolves IP complaints on a tiered basis:\n- **Tier 1 (resolved in 1–3 days):** Trademark + test buy + photos showing clear counterfeiting\n- **Tier 2 (resolved in 3–7 days):** Trademark + screenshots showing unauthorized brand use\n- **Tier 3 (resolved in 7–30 days or rejected):** Screenshots only, no trademark, vague description\n\nBuild Tier 1 evidence packages for every counterfeit case.\n\n---\n\n## Test Buy Protocol\n\n### Before the Purchase\n1. Create a dedicated \"test buy\" Amazon account separate from your brand account and any personal accounts. Use a neutral email address.\n2. Use a shipping address that is not your business address (team member's home, P.O. Box, or package forwarding service).\n3. Screenshot the listing before purchasing: show seller name, price, \"Sold by\" field, all listing images, and the date in the URL bar.\n4. Note the specific offer you're buying (if multiple sellers exist, select the hijacker's offer explicitly).\n\n### During the Order\n- Screenshot the checkout screen showing: seller name, price, and estimated delivery.\n- Note the order ID (format: 114-XXXXXXX-XXXXXXX).\n- Screenshot the order confirmation email.\n\n### Upon Delivery\nDocument the following the moment the package arrives — do not open fully until you're ready to photograph:\n\n**Package exterior:**\n- Photo of the package as received (all sides)\n- Photo showing return address label (seller's ship-from location)\n- Photo showing your order confirmation number on the packing slip\n\n**Product comparison photos (authentic vs. hijacker):**\n- Side-by-side packaging (front, back, sides)\n- Logo comparison (color accuracy, font, placement)\n- Barcode / UPC comparison (they often match but product inside differs)\n- Any authentication features: holographic stickers, serial numbers, QR codes\n- Inner packaging: foam, inserts, accessories, documentation\n- Product itself: material quality, construction, color accuracy\n- Any authenticity cards or certificates (present in authentic, absent or different in counterfeit)\n\n**Product testing (if safe and applicable):**\n- Weight comparison (counterfeits are often lighter)\n- Performance test documentation (e.g., battery life, output quality)\n- Ingredient or material discrepancy (for consumables or skincare)\n\n### What to Preserve\n- The entire package, product, and all materials in the original received state\n- Digital photos organized by category (see above)\n- Order confirmation email as PDF\n- Tracking information from delivery\n\n*Do NOT dispose of any test buy materials until the enforcement case is fully resolved and any legal threats have passed.*\n\n---\n\n## Screenshot Documentation Checklist\n\nFor every hijack incident, capture and label the following screenshots:\n\n### Listing Screenshots\n- [ ] Full listing page showing: title, brand, images, price, \"Sold by [Hijacker Name]\" field\n- [ ] \"All Offers\" display showing the hijacker's off"}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":null,"editorialQuality":{"score":100,"threshold":65,"status":"thin","wordCount":2073,"uniquenessScore":44,"reasons":["uniqueness-below-45"]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T21:02:02.665Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T21:02:02.665Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-13T20:52:22.837Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}