hifleet-mytonnages/SKILL.md
hifleet-skills 内置租船模块:路由A=本人邮箱船货盘(memory/SQLite);路由B=ttseapi 班轮船期(须 hifleet_api_key)。勿伪造数据。执行前须 read_file 分册(见 SKILL 内「必读分册」)。
npx skillsauth add charleiwang/hifleet-skills hifleet-mytonnagesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
执行任意工作流前:read_file SKILL_CONTEXT.md(定位、零基础、省 token、SQLite 事实库)、read_file ROUTING_AND_WHEN.md(能力路由 A/B、同轮混合、When to Run)。
首次启用记忆(memory-lancedb-pro):子步骤 A~D 全文 MEMORY_LANCEDB.md;路由 A 向量检索前须 read_file 并按该文件执行。
ROUTING_AND_WHEN.md。若当前请求(或其中一部分)属于 路由 B,则对该部分仅执行 Workflow 3,不得用 Workflow 2 的邮件同步与解析替代。若属于 路由 A,则邮件相关步骤仍按下列第 3~5 步及 Workflow 2 全文执行(2.1~2.7 内部逻辑不变)。若两类并存,分别执行两套路由。MEMORY_LANCEDB.md 完成知情同意与安装(或用户明确选择不启用并接受后果)。hifleet-mytonnages/config.json(即本分册所在目录;可用 HIFLEET_MYTONNAGES_DIR 覆盖)。不存在或不完整则进入 Workflow 1。ttseapi 补充船舶档案与 portid(须 hifleet_api_key,见 CHARTER_ENRICH_API.md),顺序不可省略。用户按查询港口查船盘/货盘且需按距离排序时,在 2.3 命中后按 2.3.1 与 CHARTER_ENRICH_API.md §3 批量算距并升序展示。子步骤 1.1~1.4 全文 WORKFLOW_1_MAIL.md(与 Workflow 1 完全对应,不得删减、不得改顺序)。执行前须 read_file WORKFLOW_1_MAIL.md。
子步骤 2.1~2.7 及 2.3.1、2.3.5、2.4、2.4.1、2.4.2 全文 WORKFLOW_2_MAIL.md(与 Workflow 2 完全对应,不得删减、不得重排)。执行路由 A 时须 read_file WORKFLOW_2_MAIL.md;富化与按距排序须 read_file CHARTER_ENRICH_API.md。
顺序摘要:2.1 时间窗 → 2.2 增量同步 → 2.3 SQLite→memory_search→合并(含 2.3.1 按港距排序)→ 2.3.5 脱敏 → 2.4 按 PARSE_SCHEMA.md 解析 → 2.4.1 三表写入 → 2.4.2 船舶档案 + portid 富化 → 2.5 筛选 → 2.6 输出与固定链接 → 2.7 last_used。
ttseapi 班轮接口,路由 B)不改变 Workflow 2(2.1~2.7)。接口 URL、Query、Body、params、解锁与错误处理等完整步骤见 SCHEDULE_API.md(不得删减)。执行路由 B 时须 read_file SCHEDULE_API.md。
全文 WORKFLOW_OUTPUT.md(不得删减含义)。
日期:邮件仅月日则补当前年 2026;船龄则建造年 = 2026 − 船龄。命名:TBN 保留;多港用 +。安全:密码 base64 等本地存储;配置权限 600;对话勿显式密码。
随包文件索引
<技能安装目录>/hifleet-skills/hifleet-mytonnages/
├── SKILL.md
├── SKILL_CONTEXT.md # 定位 + 零基础
├── ROUTING_AND_WHEN.md # 能力路由 + When to Run
├── MEMORY_LANCEDB.md
├── WORKFLOW_1_MAIL.md
├── WORKFLOW_2_MAIL.md
├── WORKFLOW_OUTPUT.md
├── SCHEDULE_API.md # 路由 B 班轮船期
├── CHARTER_ENRICH_API.md # 路由 A:档案 / portid / 按距排序
├── PARSE_SCHEMA.md
├── CONFIG.example.md
├── scripts/charter_facts_tool.py
├── scripts/desensitize_for_llm.py
├── config.json
└── charter_facts.sqlite3 / 向量库(运行时生成)
ClawHub 发布说明见 PUBLISH.md。
development
HiFleet 综合技能,包含船位、档案、航程(历史轨迹/历史挂靠/历史航次/上一港/当前停船)、PSC、区域/海峡通航、港口、租船船货盘邮件检索、港距排序、班轮船期、航线、航运、气象海况、船队、AIS。Use for vessel position, ship info, track history, port calls, voyage history, last departure, current stop, PSC inspection/anomalies/statistics, area or strait traffic, port, charter/open-vessel/cargo email search, port-distance sorting, liner schedule, route, shipping, weather, fleet, or AIS.
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.