customs-lead-sop
Skill9 starsChanged 25 days agoMITView on GitHub
Customs-data B2B lead SOP: verify HS codes, prioritize markets with trade stats, find real importers from bills of lading (esp. US) or secondary leads where BOL is not public, score buyers, translate evidence into outreach drafts. Supports manual CSV/Excel handoff when scraping hits login/anti-bot walls. Triggers: /customs-lead-sop, $customs-lead-sop, customs data, ImportYeti, UK Trade Info, Comtrade, bill of lading, find importers, 海关数据找客户, 提单反查. Pair with customs-pitfalls for QA. Runtime-agnostic: Cursor, Codex, OpenClaw, Claude Code.
In this repository42 other files it gives its agents.
- AGENTS.mdAGENTS.md
- B2B 静态站搭建Skill
- b2b-reddit-engagementSkill
- b2b-short-videoSkill
- 芯片 BOM 与型号寻源Skill
- 芯片供应商与真伪风险核验Skill
- 芯片贸易合规与交易关口Skill
- 芯片贸易入门路线Skill
- conversation-contextSkill
- customs-pitfallsSkill
- 深度研究编排Skill
- 外贸专家丙 · 品牌出海Skill
- 外贸专家丑 · 半导体销售Skill
- 外贸专家丁 · 外贸社媒Skill
- 外贸专家庚 · 聊外贸Skill
- 外贸专家癸 · 芯片生意Skill
- 外贸专家甲 · 社媒新外贸Skill
- 外贸专家己 · 外贸通Skill
- 外贸专家壬 · 出海Skill
- 外贸专家戊 · 工厂出海Skill
- 外贸专家辛 · B2BSkill
- 外贸专家寅 · 外贸实战Skill
- 外贸专家乙 · 外贸社媒Skill
- 外贸专家子 · 芯片采购Skill
- foreign-trade-researchSkill
- ft-geoSkill
- html-previewSkill
- icp-architectSkill
- image-genSkill
- knowledge-baseSkill
- SQLite 业务报表Skill
- 外联决策 · 首次触达Skill
- product-coachingSkill
- prospect-qualificationSkill
- sales-copilotSkill
- 供应商寻源与初筛Skill
- trade-buyer-checkSkill
- trade-deskSkill
- trade-follow-upSkill
- tradehotSkill
- trade-inquiry-replySkill
- trade-simulation-coachSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 14 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈14
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 93
Do not treat AI-guessed codes from Chinese names as final.
- Distinctive: line 95
Prefer (in order): historical export declarations → customer clearance docs → forwarder/broker records → comparable filed shipments → …
- Distinctive: line 98
If unconfirmed, tag later market/tariff analysis with HS risk.
- Distinctive: line 102
Use stats tools (China Customs, UN Comtrade, USITC DataWeb, Eurostat Comext, Canada CIMT).
- Distinctive: line 142
If the user has a paid customs platform covering that market, ask for export CSV/Excel and run 4c
- Distinctive: line 149
When browser/fetch hits Cloudflare, login walls, captchas, or free-tier caps:
- Distinctive: line 151
Stop scraping; do not invent buyers
- Distinctive: line 152
Ask the user to export CSV/Excel from ImportYeti / paid library / internal dump
- Distinctive: line 179
Never write: “We found you from customs data / bill of lading / ImportYeti…”
- Distinctive: line 180
Never cite container counts, named Chinese shippers, or BOL IDs in customer copy
- Distinctive: line 182
Keep provenance in CRM / report only
- Very specific: line 188
Write under output_dir (default ./hunt_result/).
- Distinctive: line 209
If these skills exist in the host workspace, you may chain them after scoring:
- Distinctive: line 223
No fake “official customs buyer list” claims
- Distinctive: line 225
Do not instruct bypassing login walls or captchas
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Customs Lead SOP(海关数据开发客户)
Portable Agent Skill ·
{baseDir}= this skill folder
Companion QA skill: siblingcustoms-pitfalls(sameskills/parent)
Goal
Answer three questions with public trade data:
- Which markets are buying? (Type B — national / HS stats)
- Which companies have actually imported? (Type A — firm-level BOL, or secondary leads where A is closed)
- Is there a supply-chain entry window now?
Customs data is a lead signal, not a closed deal. Conversion still depends on research, contacts, value prop, and follow-up.
Before every delivery, run the checklist in sibling skill customs-pitfalls.
Runtime notes
| Runtime | How to invoke |
| Cursor | /customs-lead-sop or natural language triggers |
| Codex | $customs-lead-sop or description match; see agents/openai.yaml |
| OpenClaw | Slash / skill discover; install this folder or parent skills/ |
| Claude Code / others | Load this SKILL.md + sibling customs-pitfalls |
Tools (any available): web search, web fetch, browser, read local CSV/Excel. No paid API required for the methodology.
Data types (pick before querying)
| Type | What you see | Use for | Not for |
| A. Bill / buyer-level | Importer, shipper, dates, product text, ports | Reverse-engineer competitors' buyers; cadence & supplier mix | Treating every Consignee as end-buyer; full air/land coverage |
| B. National trade stats | Country, HS, value, qty, trends | Market size, growth, China share, priority | Any company name / email — Comtrade has zero buyers |
| C. Tariff / access | MFN / bound rates, limits, quotas | Post-entry price competitiveness | Contact lists |
Hard split: Step 2 uses B; Step 4 needs A (or paid A export / secondary leads). Never invent firm names from B.
Tool map: references/tools.md
Workflow (execute in order)
Task Progress:
- [ ] 0. Collect inputs (+ optional CSV/Excel exports)
- [ ] 1. Confirm HS / HTS / CN codes
- [ ] 2. Rank markets with Type B stats (Priority / Opportunity / Caution)
- [ ] 3. Check tariff barriers
- [ ] 4. Find real buyers (Type A where public; else secondary leads / user export)
- [ ] 5. Score & tier buyers
- [ ] 6. Find contacts + translate evidence into outreach drafts
- [ ] 7. Write report to disk
- [ ] 8. QA with customs-pitfallsStep 0 — Inputs
| Field | Required | Notes |
product_name | yes | EN + ZH if available |
hs_codes | preferred | Verified codes; else produce candidates marked unconfirmed |
target_markets | yes | e.g. US / UK / CA / EU members |
competitor_names | no | English legal names for reverse lookup |
known_buyers | no | Existing accounts to diligence |
buyer_types | no | Brand / wholesale / retail chain / ecommerce / dropship / general importer |
target_buyer_count | no | Default 20 |
bol_export_files | no | User-provided CSV/Excel from ImportYeti / paid platforms / in-house export |
output_dir | no | Default ./hunt_result/ under current workspace |
Step 1 — HS codes
Do not treat AI-guessed codes from Chinese names as final.
Prefer (in order): historical export declarations → customer clearance docs → forwarder/broker records → comparable filed shipments → destination official tariff lookup.
Output: hs_codes[] + confidence (confirmed | candidate) + source.
If unconfirmed, tag later market/tariff analysis with HS risk.
Step 2 — Market priority (Type B only)
Use stats tools (China Customs, UN Comtrade, USITC DataWeb, Eurostat Comext, Canada CIMT).
Compare: import value, 3y growth, imports from China, China share, monthly seasonality, rough unit value.
| Tier | Rule of thumb |
| Priority | Large + growing + China supply competitive |
| Opportunity | Fast growth but low China share (explain tariff/cert vs white space) |
| Caution | Declining, high duty/barriers, or re-export hub mistaken for end market |
Split Europe by country. NL/BE hub imports ≠ end consumption.
Comtrade output stops here — it never feeds Step 4 company rows.
Step 3 — Tariffs
WTO Tariff & Trade Data: MFN Applied / Bound, etc. Put size and duty in one table before recommending entry.
Order-level truth = latest national tariff + FTAs + AD/CVD + broker advice. This step is screening only.
Step 4 — Real buyers
4a — Where public firm-level ocean BOL is usable
| Market | Primary | Secondary |
| US | ImportYeti (ocean manifest) | ImportInfo cross-check; user CSV export if crawl blocked |
US reverse lookup:
- Competitor English name → importers with ≥2 shipments in last 12 months
- Or diligence known accounts: continuity, origin countries, supplier concentration, product fit, arrivals in last 6 months
- Cross-check: address, name variants, affiliates, product text
- Drop / flag:
To Order, Bank, masked consignee, forwarder, customs broker (seecustoms-pitfalls)
4b — UK / EU / most markets without public firm BOL
Due to privacy regimes (e.g. GDPR), most UK/EU official sources no longer publish US-style shipment-level consignee manifests. Do not treat UK Trade Info (or similar) as ImportYeti-for-Europe.
For these markets:
- Finish Step 2–3 ranking with Type B stats
- Build company pool via secondary leads: trade shows / exhibitor lists, industry directories, LinkedIn, association members, news of openings/expansions, optional sibling B2B skills
- If the user has a paid customs platform covering that market, ask for export CSV/Excel and run 4c
- Label evidence as
secondary_leadorpaid_export, never fake “BOL confirmed”
A few jurisdictions historically publish more open firm-level trade data (coverage changes — verify before claiming). Prefer stating limits over guessing.
4c — Manual export handoff (anti-bot / login / paid tools)
When browser/fetch hits Cloudflare, login walls, captchas, or free-tier caps:
- Stop scraping; do not invent buyers
- Ask the user to export CSV/Excel from ImportYeti / paid library / internal dump
- Accept
bol_export_files(or pasted tables) → parse → dedupe → filter pitfalls → score → draft - Note in the report:
source=user_export+ filename + row count + date
This path is the preferred production path for teams that already pay for customs software: Skill owns cleaning, scoring, and drafts; the platform owns raw data.
Step 5 — Score buyers
Full rubric: references/scorecard.md
| Dimension | Max |
| Recency | 20 |
| Frequency | 20 |
| Product fit | 20 |
| Supplier structure (multi / shifting preferred) | 20 |
| Company fit (channel, scale, MOQ, certs, price band) | 20 |
Tiers: ≥80 1:1 focus · 60–79 normal follow-up · 40–59 nurture · <40 deprioritize
Secondary leads without shipment proof: cap confidence; do not invent frequency/recency scores from thin air — mark evidence_thin.
Step 6 — Contacts & outreach (translate, don’t expose)
Customs data answers “who buys”, not “who to email”. Roles: Purchasing / Buyer / Sourcing / Category / Supply Chain / Product Manager / Owner / MD.
Hard rules:
- Never write: “We found you from customs data / bill of lading / ImportYeti…”
- Never cite container counts, named Chinese shippers, or BOL IDs in customer copy
- Translate internal fields → product / replenishment / capability observations (see pitfalls Pitfall 12)
- Keep provenance in CRM / report only
Angle by buyer type: see examples/humanoid-harmonic-reducer.md (ToB) and examples/pet-products.md (consumer)
Step 7 — Report output
Write under output_dir (default ./hunt_result/).
Filename: customs-YY-MM-DD-{slug}.md (append -2 on same-day collision). Optional .jsonl / .csv of scored buyers.
# Customs Lead SOP — {product} / {markets}
## 1. HS codes
## 2. Market tiers + key metrics (Type B sources)
## 3. Tariff / access summary
## 4. Buyer list (source type A/export/secondary, evidence, score, tier, flags)
## 5. Outreach order + translated angles
## 6. Draft emails (optional, high tier only)
## 7. Risks & data limits (customs-pitfalls)
## 8. Next three actionsEach buyer needs: source_tools or source=user_export + time window + product/HS evidence + supplier-structure signal if any + flags (possible_agent_or_3pl, possible_customs_broker, consignee_masked_or_to_order, possible_reexport_hub, hs_risk, evidence_thin, …).
Optional handoffs
If these skills exist in the host workspace, you may chain them after scoring:
| Stage | Skill (optional) |
| Fill company pool (non-BOL markets) | b2b-search / b2b-trade-show-hunter |
| Contacts / emails | b2b-linkedin-outreach / b2b-lead-extract |
| Email drafts | b2b-email-craft |
| Negotiation | b2b-sales-negotiation |
| QA (required) | customs-pitfalls |
Compliance
- Public trade/BOL/stats + public web only (plus user-owned exports they already have rights to use)
- Drafts only — never auto-send email
- No fake “official customs buyer list” claims
- Free tiers are sample-limited; anti-bot is normal — hand off to CSV rather than bypass walls
- Do not instruct bypassing login walls or captchas
Minimum start pack (same day)
- Confirm one accurate HS from filing docs
- Compare three target countries on UN Comtrade (macro only)
- US: score ~20 recent buyers from ImportYeti/ImportInfo or user CSV; other markets: secondary leads + clear “no public BOL” caveat
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

