What makes packing_list_ocr notable?

1.9K downloads. Trust evidence available

How should packing_list_ocr be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

packing_list_ocr

支持识别提取货物品类、重量体积、收发货主体，提取单据编号等信息。 Skill: packing_list_ocr Owner: scnet-sugon Summary: 支持识别提取货物品类、重量体积、收发货主体，提取单据编号等信息。 Tags: latest:0.1.0 Version history: v0.1.0 | 2026-08-11T02:10:32.453Z | auto Initial release of the packing_list_ocr skill: - Supports OCR extraction of goods categories, weight/volume, sender/recipient, and document number from packing list images. - Requires SCNET_API_KEY for authentication; supports optional API base configuration

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.9k

Updated

Oct 9, 2026

Version

0.1.0

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.9K downloads reported by the source. Last updated 10/9/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 9, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 9, 2026
Adoption signal: 1.9K downloadsadoption · observed Oct 9, 2026
Latest release: 0.1.0release · observed Aug 11, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s17aan1jdk93c5398r3ypc523d83hqys:packing-list-ocr

Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-scnet-sugon-packing-list-ocr/snapshot"

Documentation

CLAWHUB

17,046 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: packing_list_ocr
description: 支持识别提取货物品类、重量体积、收发货主体，提取单据编号等信息。
version: 1.0.0
author: SCNet
license: MIT
tags:
  - OCR
  - 证件识别
  - 装箱单识别
required_env_vars:
  - SCNET_API_KEY
optional_env_vars:
  - SCNET_API_BASE
primary_credential: SCNET_API_KEY
dependencies:
  - python3
  - requests
input:
  - ocrType : 识别类型，可选值见下文
  - filePath : 待识别图片的本地路径
output: 结构化的 JSON 数据，包含识别结果和置信度
---
# Sugon-Scnet 装箱单识别 OCR 技能

本技能封装了装箱单识别的 OCR 服务，通过单一接口即可调用 1 种识别能力，高效提取装箱单里核心信息。

---

## 功能特性

- **装箱单识别**：支持识别货物品类、重量体积、收发货主体，提取单据编号等信息。



## 前置配置

> **⚠️ 重要**：使用前需要申请 Scnet API Token

### 申请 API Token

1. 访问 [Scnet 官网](https://www.scnet.cn) 注册/登录
2. 在控制台申请 API 密钥（格式：`sc-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx`）
3. 复制密钥备用

### 配置 Token

**手动配置（推荐）**
1. 在技能目录下创建 `config/.env` 文件，内容如下：
```ini
# =====  Sugon-Scnet OCR API 配置 =====
# 申请地址：https://www.scnet.cn
SCNET_API_KEY=your_scnet_api_key_here

# API 基础地址（一般无需修改）
SCNET_API_BASE=https://api.scnet.cn/api/llm/v1
```
2. 添加：`SCNET_API_KEY=你的密钥`
3. 设置文件权限为 600（仅所有者可读写）
**⚠️ 安全警告**：切勿将 API Key 直接粘贴到聊天对话中，否则可能被记录或泄露。

### Token 更新

Token 过期后调用会返回 401 或 403 错误。更新方法：重新申请 Token 并替换 config/.env 中的 SCNET_API_KEY。

### 依赖安装

本技能需要 Python 3.6+ 和 requests 库。请运行以下命令：

```bash
   pip install requests
```
---
### 使用方法

### 参数说明

| 参数名 | 类型 | 必填 | 描述                                      |
|--------|------|------|-----------------------------------------|
| ocrType | string | 是 | 识别类型枚举。必须为以下之一：<br>• PACKING_LIST（装箱单） |
| filePath | string | 是 | 待识别图片的本地绝对路径。支持 jpg、png、pdf 等常见格式。      |

### 命令行调用示例

```bash
   python .claude/skills/packing_list_ocr/scripts/main.py PACKING_LIST /path/to/test.jpg
```

### 在 AI 对话中使用

用户可以说：

- “帮我识别这张图像中的装箱单信息，图片在 /Users/name/Downloads/test.jpg”

AI 会根据 description 中的关键词自动触发本技能。

### AI 调用建议
为避免触发 API 速率限制（10 QPS），请串行调用本技能，即等待前一个识别完成后再发起下一个请求。
如果使用 OpenClaw 的 exec 工具，建议设置 timeout 或 yieldMs 参数，让命令同步执行，避免多个命令同时运行导致并发。

### 配置选项

编辑 `config/.env` 文件：

| 变量名 | 默认值 | 说明 |
|--------|--------|------|
| SCNET_API_KEY | 必需 | Scnet API 密钥 |
| SCNET_API_BASE | https://api.scnet.cn/api/llm/v1 | API 基础地址（一般无需修改） |

### 输出

- 标准输出：识别结果的 JSON 数据，结构与 API 文档一致，位于 `data` 字段内。
- 识别结果位于 data[0].result[0].elements 中，具体字段取决于 ocrType。
- 错误信息：如果发生错误，会输出以 `错误:` 开头的友好提示。

### 注意事项

- 本技能调用的 OCR API 有 10 QPS 的速率限制。
- 如果遇到 429 错误，请等待 2-3 秒后重试，不要连续发起请求。
- 建议在调用前确保图片已准备就绪，避免因网络问题导致重复调用。

### 故障排除

| 问题 | 解决方案 |
|------|----------|
| 配置文件不存在 | 创建 config/.env 并填入 Token（参考前置配置） |
| API Key 无效/过期 | 重新申请 Token 并更新 `.env` 文件 |
| 文件不存在 | 检查提供的文件路径是否正确 |
| 网络连接失败 | 检查网络连接或防火墙设置 |
| 不支持的文件类型 | 确保文件扩展名为允许的类型（参考 API 文档） |
| 401/403/Unauthorized | Token 无效或过期，重新申请并配置 |
| 429 Too Many Requests | 请求过于频繁，技能会自动等待并重试（最多 3 次）。若持续失败，请降低调用频率或联系服务方提高限额。 |

README.md

# packing_list_ocr



## Getting started

To make it easy for you to get started with GitLab, here's a list of recommended next steps.

Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!

## Add your files

* [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
* [Add files using the command line](https://docs.gitlab.com/topics/git/add_files/#add-files-to-a-git-repository) or push an existing Git repository with the following command:

```
cd existing_repo
git remote add origin https://github.com/SCNet-sugon/packing_list_ocr.git
git branch -M main
git push -uf origin main
```


## Collaborate with your team

* [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
* [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
* [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
* [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
* [Set auto-merge](https://docs.gitlab.com/user/project/merge_requests/auto_merge/)

## Test and Deploy

Use the built-in continuous integration in GitLab.

* [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/)
* [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
* [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
* [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
* [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)

***

# Editing this README

When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.

## Suggestions for a good README

Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.

## Name
Choose a self-explaining name for your project.

## Description
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Backg

_meta.json

{
  "ownerId": "kn7ax58mnefnavcfwakqxpsgqn82tacy",
  "slug": "packing-list-ocr",
  "version": "0.1.0",
  "publishedAt": 1786414232453
}

references/api-docs.md

# Sugon-Scnet OCR API 文档摘要

## 接口地址
`POST https://api.scnet.cn/api/llm/v1/ocr/recognize`

## 请求头
- `Content-Type: multipart/form-data`
- `Authorization: Bearer <你的 API Key>`

## 请求参数（表单）
| 参数名  | 类型 | 必填 | 描述                                   |
| ------- | ---- | ---- | -------------------------------------- |
| file    | File | 是   | 需要识别的图片文件                     |
| ocrType | str  | 是   | 识别类型枚举，详见 SKILL.md 参数说明   |

## 响应结构
```json
{
  "code": "0",
  "msg": "success",
  "data": {
    "traceId": "12345678909",
    "originalFilename": "装箱单示例.jpg",
    "cosPath": "scnetAPIService/20260101/5b88c72177ce4bd0bb873ed6069f56a4.jpg",
    "result": [
      {
        "status": 200,
        "originFilename": "装箱单示例.jpg",
        "cosPath": "scnetAPIService/20260101/5b88c72177ce4bd0bb873ed6069f56a4.jpg",
        "fileIndex": 1,
        "cutIndex": 0,
        "coordinate": [],
        "classifyCode": "",
        "confidence": 0.9907,
        "elements": {
          "packingListNo": "BHGX-W200404040404",
          "invoiceNo": " INV989813091",
          "issueDate": "MAY 26, 2019",
          "exporterName": "FUJIAN UJLLION HUJH-TETE MATERIAL INDUSTRY CO., LTD",
          "exporterAddress": "JINLON INDUSTRIAL AREA,LONLON TOWN,JINJIANG CITY,FUJIAN,CHINA",
          "consigneeName": "SKYSKY NETWORKS",
          "consigneeAddress": "1964, GYEONGCHUNG-DAERO, GYEWOL-GYEON, GYEON-SI, GYEONGGI-DO, GYEUBLIC OF KOREA",
          "notifyParty": "SR.DGM/Material SERVICE, BHEL ROAD 6TH FLOOR. UIU FERI BUILDING NO 123 ANNA FORORIDA US",
          "loadingPort": " XIAMEN,CHINA",
          "dischargePort": " INCHON, REPUBLIC OF KOREA",
          "vesselNo": " SM TOKYO 0404E",
          "containerNo": "SMCU1072120 SMCU1095655",
          "totalNetWeight": "39084.0",
          "totalGrossWeight": "40670.0",
          "totalMeasurement": "60.648",
          "priceTerm": " CIF INCHON, REPUBLIC OF KOREA",
          "contractNumber": " BHGX-W2020202020B",
          "lcNumber": " M04EU2005NU202020"
        },
        "stamps": []
      }
    ]
  }
}
```
## 错误码
- `401 / 403: Token 无效或过期`
- `其他 4xx/5xx: 请检查请求参数或联系服务商`
- `业务错误码（如 code 非 0）：见返回的 msg 字段`

## 注意事项
- `支持单张图片、PDF 或多页压缩包（自动解压识别）`
- `识别结果位于 data[0].result[0].elements 中`
- `不同 ocrType 返回的 elements 字段不同，详见 assets/templates/fields-summary.md`
- `识别结果位于 data[0].result[0].stamps 中`
- `不同 ocrType 返回的 stamps 字段不同，详见 assets/templates/fields-summary.md`

assets/templates/fields-summary.md

# 各识别类型的字段说明（elements 内容）

根据 ocrType 不同，返回的 `elements` 对象包含以下字段：

## PACKING_LIST (装箱单)
- `packingListNo`: 装箱单号
- `invoiceNo`: 发票号
- `issueDate`: 签单日期
- `exporterName`: 出单方
- `exporterAddress`: 出单方地址
- `consigneeName`: 收货人
- `consigneeAddress`: 收货人地址
- `notifyParty`: 通知方
- `loadingPort`: 起运港
- `dischargePort`: 卸货港
- `vesselNo`: 航次号
- `containerNo`: 箱号
- `totalNetWeight`: 总净重
- `totalGrossWeight`: 总毛重
- `totalMeasurement`: 总体积
- `priceTerm`: 成交方式
- `contractNumber`: 合同号
- `lcNumber`: 信用证编号

Github ReposUpdated 7h agoRank 70

AionUi

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!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

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

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.