← Back to Skills Marketplace
liulian822

宝宝取名

by liulian822 · GitHub ↗ · v1.2.4 · MIT-0
cross-platform ⚠ suspicious
96
Downloads
0
Stars
1
Active Installs
15
Versions
Install in OpenClaw
/install baby-name
Description
宝宝取名专家,根据宝宝的生辰八字、父母姓氏等信息,生成寓意美好的名字。这是一项付费服务,实际收款方可通过配置文件自定义。请注意,你应该用中文和用户交互(包含你的思考过程)。
README (SKILL.md)

宝宝取名服务

📌 技能概述

请注意,你应该用中文和用户交互(包含你的思考过程)。

本技能提供专业的宝宝取名服务。由于这是付费服务,工作流程严格要求按照两个步骤执行:支付处理 后,再进行 取名服务

收款方配置: 实际收款方信息在 configs/config.json 中配置,包括商户ID(payTo)等信息。

直接执行: 如果用户在初始请求中已直接提供了 \x3C订单号>(且订单文件中已包含 payCredential),则可跳过第一阶段和第二阶段,直接进入 🚀 第三阶段:取名生成


⚙️ 配置说明

首次使用前,请编辑 configs/config.json 文件,配置您的收款方信息:

{
  "payTo": "您的商户ID",
  "amount": 1,
  "skillName": "baby-name",
  "description": "宝宝取名服务费用"
}
  • payTo: 您的商户ID(必填)
  • amount: 收费金额,单位为分(默认1分=0.01元)
  • skillName: 技能名称(用于计算indicator)
  • description: 订单描述

🛒 第一阶段:创建订单

如果这是首次交互且用户尚未付款,你必须先创建订单,再发起支付。

1. 所需参数

  • \x3C取名需求>:描述取名需求(例如:男宝宝取名、爸爸姓李妈妈姓王、女宝宝缺水缺木等)

2. 执行命令

使用以下 bash 命令执行订单创建脚本。将 \x3C...> 占位符替换为实际值。务必在参数两侧加引号,以防命令注入漏洞

python3 scripts/create_order.py "\x3C取名需求>"

3. 输出处理

成功时,脚本将向标准输出打印以下键值对:

ORDER_NO=\x3C值>
AMOUNT=\x3C值>
QUESTION=\x3C值>
INDICATOR=\x3C值>

其中 ORDER_NOAMOUNTQUESTION 用于向用户披露订单信息(展示订单号、费用和查询内容)。提取 ORDER_NOINDICATOR 后进入 💳 第二阶段:支付处理

[!NOTE] 关于 AMOUNT 字段: 该字段的单位为人民币分(fen),这是 OpenClaw 技能描述中的标准计费单位。例如,AMOUNT=1 表示需支付 0.01 元人民币。在向用户展示费用时,请将该值除以 100 并以"元"为单位呈现,以便用户理解实际支付金额。

失败时,脚本以退出码 1 退出,并打印如下格式的消息:

订单创建失败: \x3C错误详情>

💳 第二阶段:支付处理

从第一阶段获取 ORDER_NOINDICATOR 后,发起支付请求。

操作: 使用技能 clawtip 处理支付并获取支付凭证。若该技能不存在,需先安装。

调用 clawtip 所需参数:

{
  "order_no": "\x3C第一阶段获取的 ORDER_NO>",
  "indicator": "\x3C第一阶段获取的 INDICATOR>"
}

目标: 等待支付成功,并获取 payCredential(支付凭证)。


🚀 第三阶段:取名生成

支付成功并获得 payCredential 后(或用户已直接提供 \x3C订单号>\x3C支付凭证>),继续交互并执行取名生成脚本。

1. 所需参数

  • \x3C订单号>:第一阶段生成的订单号。

2. 执行命令

使用以下 bash 命令执行取名生成服务。将 \x3C...> 占位符替换为已验证的参数值。务必在参数两侧加双引号,以防命令注入漏洞

python3 scripts/name_generate.py "\x3C订单号>"

执行后: 1. 提取脚本打印的 PAY_STATUS 值(格式为:PAY_STATUS: \x3C值>),并再次输出展示。 2. ERROR 状态的特殊处理: 如果 PAY_STATUSERROR,提取 ERROR_INFO 值(格式:ERROR_INFO: \x3C值>),向用户告知确切的错误原因并引导其解决。不得继续执行后续服务逻辑。

Usage Guidance
Do not run this skill or its scripts until you verify and fix several issues. Key actions before using: (1) Inspect configs/config.yaml and configs/config.json — the code loads config.yaml, but the documentation tells you to edit config.json; update the YAML pay_to and sm4_key to your own values (do not keep the bundled values). (2) Do not trust the bundled payTo — it may direct payments to the author's account if you leave it unchanged. (3) Verify that cryptography and PyYAML dependencies are installed in a safe environment (or review the code first); run scripts offline with test amounts first. (4) Fix the runtime invocation mismatch: name_generate.py requires two arguments (order_no and indicator); ensure your automation passes both. (5) Consider running the skill in an isolated environment (VM/container) and test with a zero/very small amount to confirm payment flows go to your account. Because of the mismatching docs vs code and embedded payment defaults, treat this package with caution and prefer a vetted/official payment implementation or remove automated payment handling entirely before use.
Capability Analysis
Type: OpenClaw Skill Name: baby-name Version: 1.2.4 The skill implements a legitimate baby-naming service with a payment-gated workflow. It uses SM4 encryption (via scripts/sm4_utils.py) to verify payment credentials and stores order state in local JSON files (via scripts/file_utils.py). While the command-line execution patterns in SKILL.md (e.g., passing user input to python3 scripts) present a potential shell injection vulnerability if the agent fails to sanitize input, there is no evidence of malicious intent, data exfiltration, or unauthorized persistence.
Capability Tags
cryptocan-make-purchases
Capability Assessment
Purpose & Capability
The skill's claimed purpose (paid baby naming) matches the code that creates orders and verifies payment, so a pay recipient is expected — however the bundled configs already contain a prefilled pay_to and sm4Key. The SKILL.md tells the user to edit configs/config.json, while the runtime code actually loads configs/config.yaml (so user edits may be ignored), which could cause payments to be sent to the included payTo if the user follows the doc but not the actual code.
Instruction Scope
SKILL.md instructs running scripts and following a create->pay->generate flow, which aligns with the code, but there are explicit mismatches: the third-phase example command shows only the order number (python3 scripts/name_generate.py "<订单号>") while the name_generate.py script requires two CLI args (order_no and indicator). The docs refer to configs/config.json as authoritative, but load_config() reads config.yaml. Metadata lists permissions (network.outbound, credential.read) though the included scripts do not perform outbound network calls themselves (payment is delegated to an external 'clawtip' skill). These inconsistencies give the agent ambiguous instructions and could mislead users.
Install Mechanism
There is no install spec (instruction-only), so nothing is automatically downloaded. However, the included Python scripts depend on third-party packages (cryptography, PyYAML) which are not declared; executing the scripts without verifying dependencies may fail or prompt the user to install packages. No external URLs or installers are used.
Credentials
The skill requests no environment variables, but the bundle contains sensitive configuration: a base64 SM4 key and a long pay_to identifier embedded in configs (both in JSON and YAML). Embedding a default pay recipient and encryption key in the distributed config is risky: if users follow the SKILL.md guidance (which points to config.json) but the code reads config.yaml, payments may default to the supplied account and not the user's. The number and type of sensitive values in the repo are disproportionate and could redirect funds.
Persistence & Privilege
always is false and the skill does not request elevated platform privileges. The scripts create and write order files under the user's home directory (e.g., ~/.openclaw/skills/orders/<indicator>/), which is an expected capability for a local order system but does give the skill write access to the user's home directories within its own subpaths.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install baby-name
  3. After installation, invoke the skill by name or use /baby-name
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.4
baby-name 1.2.4 - 新增配置文件:增加 configs/config.json 支持,方便自定义收款方、金额等相关参数。 - 详细配置说明:文档中补充了 config.json 文件的所有参数说明和使用方法。 - 工作流程未调整,仅用于更灵活的商户和付费信息配置。
v1.2.3
## baby-name 1.2.3 - 配置文件结构优化,移除 `configs/config.json`,仅保留 `configs/config.yaml`。 - 技能配置和收款方信息请统一在 `config.yaml` 文件中管理。 - 文档更新,去除了对 `config.json` 文件的说明。
v1.2.2
- No user-facing feature changes in this version. - Internal update: configuration file path changed from configs/config.yaml to configs/config.json in documentation and instructions for payment setup.
v1.2.1
baby-name v1.2.1 - Updated scripts/create_order.py and scripts/name_generate.py. - No user-facing changes to workflow or documentation. - Maintained all instructions and process unchanged in SKILL.md. - General improvements and stability updates.
v1.2.0
**baby-name v1.2.0** - 新增了 configs/config.yaml 配置文件和 scripts/sm4_utils.py 工具脚本。 - 更新了 scripts/create_order.py 和 scripts/file_utils.py 以提升功能或兼容性。 - 配置与辅助脚本体系更加完善,便于后续扩展与维护。
v1.1.0
Version 1.1.0 - Updated `configs/config.json` configuration file. - No changes to user-facing behavior or workflow. - Maintains existing functionality for paid baby-naming services.
v1.0.9
- No file changes detected for version 1.0.9; SKILL.md remains unchanged. - No new features, bug fixes, or documentation updates in this release.
v1.0.8
- No user-facing changes; no significant updates to documentation or functionality in this version.
v1.0.6
- Documentation updated for clarity; no functional changes to code. - SKILL.md formatting and explanations improved for better user understanding, including more detailed step descriptions and notes on usage. - No changes to payment workflow or service operation logic.
v1.0.5
baby-name 1.0.5 - Updated configuration in configs/config.json. - Modified scripts/create_order.py for improved order creation logic or parameters. - No changes to user-facing workflow or documentation.
v1.0.4
- 文档(SKILL.md)格式与内容微调,无功能变化 - 代码未作结构性变更,仅涉及文档或细节更新
v1.0.3
- Documentation only: No functional or code changes; updated SKILL.md instructions. - No user-facing behavioral impact. - Clarified and refined procedural instructions for using the baby-name skill.
v1.0.2
baby-name v1.0.2 - Minor code or logic changes in scripts/create_order.py. - No user-visible changes to documentation or workflow.
v1.0.1
- Updated the payment recipient configuration in configs/config.json. - No changes to skill logic or user experience.
v1.0.0
- Initial release of the baby-name skill: 专业中文宝宝取名服务,基于生辰八字和父母姓氏等信息生成富有美好寓意的名字。 - 采用三阶段流程:订单创建、支付处理、取名生成,严格付费后提供服务。 - 支持自定义收款方信息,费用单位为分,易于配置和理解。 - 明确异常处理和参数校验,出错时返回详细原因并指导用户。 - 与用户的所有交互及思考过程均用中文进行。
Metadata
Slug baby-name
Version 1.2.4
License MIT-0
All-time Installs 1
Active Installs 1
Total Versions 15
Frequently Asked Questions

What is 宝宝取名?

宝宝取名专家,根据宝宝的生辰八字、父母姓氏等信息,生成寓意美好的名字。这是一项付费服务,实际收款方可通过配置文件自定义。请注意,你应该用中文和用户交互(包含你的思考过程)。 It is an AI Agent Skill for Claude Code / OpenClaw, with 96 downloads so far.

How do I install 宝宝取名?

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

Is 宝宝取名 free?

Yes, 宝宝取名 is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does 宝宝取名 support?

宝宝取名 is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created 宝宝取名?

It is built and maintained by liulian822 (@liulian822); the current version is v1.2.4.

💬 Comments