← Back to Skills Marketplace
spzwin

cms-openclaw-honor

by spzwin · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
45
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install cms-openclaw-honor
Description
AI龙虾认证查询。用户询问「龙虾认证/AI龙虾/认证档位/本周 Token/Skill 命中/晋级条件/我是几级」等时,进入本 Skill 脚本调用流程;兼容说法「领虾档位/领虾等级」。通过依赖 cms-auth-skills 获取 AppKey 鉴权后查询当前员工本周认证状态;无需 access-token。
README (SKILL.md)

\r \r

cms-openclaw-honor — AI龙虾认证查询\r

\r OpenClaw 技能 namecms-openclaw-honor,与 skillcode 一致。本技能用于查询当前鉴权员工在 AI 龙虾认证体系中的本周档位与晋级进度。\r \r 当前版本: 1.0.1\r \r 接口版本: 业务接口统一使用 /open-api/ai-certification-honor-wall/* 前缀,鉴权类型为 appKey(无需 access-token)。\r \r

能力概览\r

\r | 模块 | 说明 |\r |------|------|\r | employee-status | 查询当前员工本周认证档位(L1/L2/L3)、Token 用量、四 Skill 命中、晋级下一档条件 |\r \r

全公司认证榜单(honor-wall)、往期榜单(honor-wall/history)尚未在本 Skill 开放;若用户需要全榜,说明能力范围并引导 Web 认证/荣誉墙页面。\r \r

适用范围与歧义排除\r

\r

  • 本 skill 唯一指向:通过 appKey 访问 open-api 暴露的 AI 龙虾认证接口(/open-api/ai-certification-honor-wall/openclaw/*)。\r
  • 身份边界corpIdemployeeId 由 open-api 根据 个人 appKey 自动解析,调用方不得在 Query/Header 中传入他人员工 ID 或企业 ID。\r
  • 典型触发词:AI龙虾、龙虾认证、认证档位、认证等级、L1/L2/L3、本周 Token、Skill 命中、晋级、我是几级;兼容别名:领虾、领虾档位、领虾等级、一级虾/二级虾/三级虾。\r
  • 不走本 skill:全公司榜单、他人档位查询、修改榜单数据。\r \r

统一规范\r

\r

  • 鉴权依赖:cms-auth-skills/SKILL.md\r
  • 生产基址:https://sg-al-cwork-web.mediportal.com.cn/open-api\r
  • 详细接口:references/employee-status/README.md\r
  • 鉴权注入规则:references/auth.md\r \r

强制前置(鉴权)\r

\r 调用任何脚本前,必须先通过依赖 Skill cms-auth-skills 获取有效 AppKey。\r \r

  • AppKey 必须以 --app-key 注入脚本命令。\r
  • 未鉴权时,禁止执行 scripts/**/*.py。\r
  • 所有 HTTP 请求 Header 携带 appKey无需 access-token。\r \r

标准执行流程\r

\r

  1. 识别用户是否要查询本人认证档位(执行)还是了解规则(可文字说明后确认是否执行)。\r
  2. 读取 references/auth.md 确认 AppKey 注入规则。\r
  3. 读取 references/employee-status/README.md。\r
  4. 执行 python3 scripts/openclaw/get-employee-status.py --app-key "\x3CAppKey>"。\r
  5. 将脚本输出的摘要呈现给用户;默认不回显完整 JSON。\r \r

脚本使用规则(强制)\r

\r

  1. 所有 Open API 调用必须通过 scripts/ 下 Python 脚本执行。\r
  2. 先读 references 再执行脚本。\r
  3. 鉴权统一依赖 cms-auth-skills,脚本不实现登录与换 token。\r
  4. 仅允许生产域名,不使用测试地址。\r
  5. 出错时间隔 1 秒、最多重试 3 次。\r \r

输出规范(对用户)\r

\r 优先输出:\r \r

  • 姓名、部门、本周区间(weekRange)\r
  • 当前认证档位(tier / tierLabel)或「未上榜」\r
  • Token 用量(totalInTokenDisplay)、使用次数(totalCnt)、Skill 命中数\r
  • 若有下一档:摘要 nextTierRequirements.summary 及未满足项\r \r 不暴露:appKey、完整原始 JSON(除非用户明确要求技术细节)。\r \r

分档规则速查(与认证榜单一致)\r

\r | 等级 | Token(本周) | 附加条件 |\r |------|---------------|----------|\r | L3 | ≥ 1 亿 | 在 L3 准入名单 |\r | L2 | ≥ 2000 万 | 四 Skill 系统 ≥ 2 |\r | L1 | ≥ 50 万 | AI 使用次数 > 20(至少 21 次) |\r | 未上榜 | 不满足任一档 | — |\r \r 统计周期:本周(周五 00:00 — 下周四 23:59)。\r \r

错误处理\r

\r | 场景 | 处理 |\r |------|------|\r | resultCode != 1 或 HTTP 401 | 检查 AppKey 是否有效、是否已通过 cms-auth-skills 授权 |\r | 400 缺少企业/员工信息 | 确认使用的是绑定当前用户的个人 appKey |\r | 5xx | 间隔重试,最多 3 次后提示稍后重试 |\r \r

能力树\r

\r

cms-openclaw-honor/\r
├── SKILL.md\r
├── references/\r
│   ├── auth.md\r
│   ├── api-endpoints.md\r
│   └── employee-status/\r
│       └── README.md\r
└── scripts/\r
    └── openclaw/\r
        ├── honor_wall_client.py\r
        └── get-employee-status.py\r
```\r
Usage Guidance
Install only if you trust the Open API service and the companion cms-auth-skills dependency to handle your personal AppKey. The skill should be allowed to call the documented production domain, but it does not need broad filesystem access, background execution, or access to unrelated environment secrets.
Capability Tags
requires-sensitive-credentials
Capability Assessment
Purpose & Capability
The stated purpose, documentation, and scripts align: the skill fetches the authenticated user's weekly certification tier, token usage, skill hits, and next-tier requirements from a single documented employee-status endpoint.
Instruction Scope
Runtime instructions restrict use to self-status lookups, exclude company-wide rankings and other employees, require prior AppKey acquisition through the dependency skill, and tell the agent not to expose the AppKey.
Install Mechanism
The artifact contains markdown references and two Python scripts, with no package install hooks, background setup, or hidden execution mechanism.
Credentials
The scripts make authenticated HTTPS requests to a disclosed production domain and can read XG_BIZ_API_KEY or XG_APP_KEY as a fallback, which is sensitive but consistent with the documented AppKey-based lookup purpose.
Persistence & Privilege
No persistence, file writes, privilege escalation, credential storage, destructive actions, or broad local indexing were found.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install cms-openclaw-honor
  3. After installation, invoke the skill by name or use /cms-openclaw-honor
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
初始版本
Metadata
Slug cms-openclaw-honor
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is cms-openclaw-honor?

AI龙虾认证查询。用户询问「龙虾认证/AI龙虾/认证档位/本周 Token/Skill 命中/晋级条件/我是几级」等时,进入本 Skill 脚本调用流程;兼容说法「领虾档位/领虾等级」。通过依赖 cms-auth-skills 获取 AppKey 鉴权后查询当前员工本周认证状态;无需 access-token。 It is an AI Agent Skill for Claude Code / OpenClaw, with 45 downloads so far.

How do I install cms-openclaw-honor?

Run "/install cms-openclaw-honor" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is cms-openclaw-honor free?

Yes, cms-openclaw-honor is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does cms-openclaw-honor support?

cms-openclaw-honor is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created cms-openclaw-honor?

It is built and maintained by spzwin (@spzwin); the current version is v1.0.0.

💬 Comments