Token导航 LogoToken导航

Agent Skill · 研究检索

upkuajing-customs-trade-company-search(上夸晶海关贸易公司搜索)

upkuajing-customs-trade-company-search 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

upkuajing-customs-trade-company-search 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为接触敏感数据;许可证为 MIT-0,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 23,749。

总安装 4,190周安装 180GitHub Stars 公开资料未说明下载 1,469核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.6

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:upkuajing-customs-trade-company-search(上夸晶海关贸易公司搜索)
来源仓库:https://github.com/upkuajing/upkuajing-customs-trade-company-search
安装命令:
openclaw skills install upkuajing-customs-trade-company-search
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install upkuajing-customs-trade-company-search

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

基于海关贸易数据搜索进出口企业与全球买家信息。提供订单详情、联系人及物流关联数据,助力外贸业务。适用于寻找潜在客户或分析行业竞争格局的场景。使用前需开通边境魔方贸易数据接口权限。upkuajing-customs-trade-company-search 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

注意部分历史数据可能存在延迟,实时性依赖海关申报进度。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install upkuajing-customs-trade-company-search;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

upkuajing-customs-trade-company-search 怎么安装?

在终端执行 openclaw skills install upkuajing-customs-trade-company-search。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

upkuajing-customs-trade-company-search 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

upkuajing-customs-trade-company-search 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

upkuajing-customs-trade-company-search 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

upkuajing-customs-trade-company-search 用的人多吗?

公开数据是累计安装 4,190 次,近一周安装 180 次,下载 1,469 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

upkuajing-customs-trade-company-search 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
upkuajing-customs-trade-company-search

上夸晶海关贸易公司搜索 · 本页

4,190—接触敏感数据MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
upkuajing-customs-trade-company-search
description
Official skill for upkuajing (跨境魔方). Find companies (找公司) and global buyers using customs trade data. Get trade order details, business contact info, and lead generation tools for import/export market research and supply chain analysis.
metadata
{"version":"1.0.6","homepage":"https://www.upkuajing.com","clawdbot":{"emoji":"🏢","requires":{"bins":["python"],"env":["UPKUAJING_API_KEY"]},"primaryEnv":"UPKUAJING_API_KEY"}}

UpKuaJing Customs Trade Company Search

Search for companies through customs trade data using the UpKuaJing Open Platform API. This skill uses a data-driven approach: finding companies by analyzing trade records and transaction patterns.

Overview

This skill provides access to UpKuaJing's customs trade data API through four scripts: two search methods (trade list, company list) and two enhancement interfaces (company details, contact information). API key generation and top-up are provided through the auth.py script.

Running Scripts

Environment Setup

  1. Check Python: python --version
  2. Install dependencies: pip install -r requirements.txt

Script directory: scripts/*.py Run example: python scripts/*.py

Important: Always use direct script invocation like python scripts/trade_list_search.py. Do NOT use shell compound commands like cd scripts && python trade_list_search.py.

Important: Always use direct script invocation like python scripts/company_list_search.py. Do NOT use shell compound commands like cd scripts && python company_list_search.py.

Two Search Methods

Trade List Search (trade_list_search.py)

  • Return granularity: Each trade order as one record
  • Use cases: Focus on "what transactions occurred"
  • Examples:

- "Show all orders where Company A purchased LED" - "Find soybean trade records imported/exported to US" - "View specific transaction details within a time period"

Company List Search (company_list_search.py)

  • Return granularity: Trade orders aggregated by company, each company as one row
  • Use cases: Focus on "which companies exist"
  • Examples:

- "Find companies that purchased LED" - "Find US companies with electronics import/export business with China" - "Find companies with China-US trade" (logistics industry customer development)

Two Enhancement Features

After obtaining trade list or company list, use these interfaces to enrich company IDs in the results when necessary: Company Details (company_get_details.py --companyIds *)

  • Get company information (excluding contact information)
  • Parameters: --companyIds List of company IDs (space-separated), max 20 at a time
  • API business parameters: Company Details

Contact Information (company_get_contact.py --companyIds *)

  • Get contact details: email, phone, social media, website
  • Parameters: --companyIds List of company IDs (space-separated), max 20 at a time
  • API business parameters: Get Contact Information

API Key and Top-up

This skill requires an API key. The API key is stored in the ~/.upkuajing/.env file:

cat ~/.upkuajing/.env

Example file content:

UPKUAJING_API_KEY=your_api_key_here

API Key Not Set

First check if the ~/.upkuajing/.env file has UPKUAJING_API_KEY; If UPKUAJING_API_KEY is not set, prompt the user to choose:

  1. User has one: User provides it (manually add to ~/.upkuajing/.env file)
  2. User doesn't have one: You can apply using the interface (auth.py --new_key), the new key will be automatically saved to ~/.upkuajing/.env

Wait for user selection;

Account Top-up

When API response indicates insufficient balance, explain and guide user to top up:

  1. Create top-up order (auth.py --new_rec_order)
  2. Based on order response, send payment page URL to user, guide user to open URL and pay, user confirms after successful payment;

Get Account Information

Use this script to get account information for UPKUAJING_API_KEY: auth.py --account_info

API Key and UpKuaJing Account

Fees

All API calls incur fees, different interfaces have different billing methods. Latest pricing: Users can visit Detailed Price Description Or use: python scripts/auth.py --price_info (returns complete pricing for all interfaces)

List Search Billing Rules

Billed by number of calls, each call returns up to 20 records:

  • Number of calls: ceil(query_count / 20) times
  • Whenever query_count > 20, must before execution:

1. Inform user of expected number of calls 2. Stop, wait for explicit user confirmation in a separate message, then execute script

Enhancement Interface Billing Rules

Billed by number of IDs passed, max 20 IDs per call:

  • Pass 1 ID = billed 1 time
  • Pass 20 IDs = billed 20 times (single call limit)
  • Before batch retrieval must:

1. Inform user of number of IDs passed and corresponding fee count 2. Stop, wait for explicit user confirmation in a separate message, then execute script

Fee Confirmation Principle

Any operation that incurs fees must first inform and wait for explicit user confirmation. Do not execute in the same message as the notification.

Workflow

Choose the appropriate API based on user intent

Decision Guide

User IntentUse API
"Analyze trade patterns/order data"Trade list
"Find companies purchasing XXX"Company list
"Find suppliers for XXX with email"Company list existEmail=1
"Get company detailed information"Company details
"Get contact information"Contact information

Usage Examples

Scenario 1: Small Query — Trade Data Analysis

User request: "Show 2024 LED lighting fixture trade data exported to US"

python scripts/trade_list_search.py \
  --params '{"products": ["LED lights"], "buyerCountryCodes": ["US"], "dateStart": 1704067200000, "dateEnd": 1735689599999}' \
  --query_count 20

To further get supplier details (supports batch queries):

python scripts/company_get_details.py --companyIds 123456 789012 ...

Scenario 2: Large Query — Big Data Analysis

User request: "Analyze 100 soybean trade records from 2024" Before execution inform user: ceil(100/20) = 5 API calls, confirm before executing;

python scripts/trade_list_search.py --params '{"products": ["soybean"], "dateStart": 1704067200000, "dateEnd": 1735689599999}' --query_count 100

Scenario 3: Ultra Large Query - Multiple Script Calls Required

User request: "Find 2000 companies importing electronics from China, with email addresses" Before execution inform user: ceil(2000/20) = 100 API calls, confirm before executing;

python scripts/company_list_search.py --params '{"companyType": 2, "sellerCountryCodes": ["CN"], "existEmail": 1}' --query_count 1000

After execution: Script responds {"task_id":"a1b2-c3d4", "file_url": "xxxxx", ……} Continue execution, append data: Specify task_id, script continues query from last cursor and appends to file

python scripts/company_list_search.py --task_id 'a1b2-c3d4' --query_count 1000

Error Handling

  • API key invalid/non-existent: Check UPKUAJING_API_KEY in ~/.upkuajing/.env file
  • Insufficient balance: Guide user to top up according to Account Top-up steps
  • Invalid parameters: Must first check the corresponding API documentation in references/ directory, check parameter names and formats, do not guess

Best Practices

Choosing the Right Method

  1. Understand user intent:

- Analyze trade data? → Use trade list search - Find customers/partners? → Use company list search

  1. Check API documentation:

- Before executing list queries, must first check the corresponding API reference documentation - Trade list: Check references/trade-list-api.md - Company list: Check references/company-list-api.md

  1. Identify parameter conditions:

- Set date range - HS codes are usually more precise than product names for filtering - Reduce noise by filtering specific countries - Use ISO country codes: CN, US, JP, etc. - Use filters to find companies with contact information

Handling Results

  1. Handle jsonl files carefully: For large data queries, pay attention to file size
  1. Gradually enrich information: Only call details/contact interfaces when needed

- Company IDs returned by both list interfaces can be used for both detail interfaces - If user only needs a few companies, don't get details for all companies

Notes

  • All timestamps are in milliseconds
  • Country codes use ISO 3166-1 alpha-2 format (e.g., CN, US, JP)
  • File paths use forward slashes on all platforms
  • Product names and industry names must be in English
  • Search quantity affects API response time, recommend setting timeout:120
  • Prohibit outputting technical parameter format: Do not display code-style parameters in responses, convert to natural language
  • Do not estimate or guess per-call fees — use python scripts/auth.py --price_info to get accurate pricing information
  • Do not guess parameter names, get accurate parameter names and formats from documentation

Related Skills

Other UpKuaJing skills you might find useful:

  • upkuajing-global-company-people-search — Global company and people search
  • upkuajing-email-tool — Send emails and manage email tasks
  • upkuajing-map-merchants-search — Map-based merchant search
  • upkuajing-sms-tool — Send SMS and manage SMS tasks
  • upkuajing-contact-info-validity-check — Check contact info validity

平台分布

OpenClaw

79.32%
按下载量换算1,165

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills