Query Customer Service Record
v1.0.0查询霍小钉客户服务记录。使用场景：用户需要查询某个客户的服务小计记录时，自动解析客户名称、调用搜索接口确认客户、处理多客户选择、查询服务记录并展示总结。
⭐ 0· 61·1 current·1 all-time
byxiaodouzi@adtomato
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the behavior: the SKILL.md and included script only call customer search and service-record endpoints on a configurable base_url. No unrelated credentials, binaries, or services are requested.
Instruction Scope
Runtime instructions stay within the stated scope: parse customer name/time, call the provided script to search and fetch records, ask the user to disambiguate when multiple matches occur, and format results. The instructions do not request unrelated files, environment variables, or system data.
Install Mechanism
No install spec (instruction-only) and a small Python script is bundled. This is low risk, but users must ensure Python and the 'requests' package are available; nothing is downloaded from external URLs.
Credentials
The skill requires no environment variables or credentials. The script accepts a base_url parameter (default provided) and currently assumes no authentication — this aligns with the SKILL.md note that auth can be added later.
Persistence & Privilege
Skill is not always-enabled, does not request system or other-skill configuration, and does not persist or modify global agent settings.
Assessment
This skill appears to do only what it claims: it calls two API endpoints on a configurable base_url and formats the results. Before installing or using it, verify: 1) the default base_url (https://hxd.ahdingtalk.com:8843) is the intended/authorized endpoint for your organization; 2) whether the API requires authentication in your environment (the script assumes none); 3) the environment has Python and the 'requests' library; and 4) you are comfortable allowing the agent to make network requests to the provided base_url because customer records are likely sensitive. If you plan to use it productionally, consider adding TLS/hostname validation checks, authentication headers, and explicit handling/logging policies for sensitive data.Like a lobster shell, security has layers — review code before you run it.
latestvk97cax11cakxgjqwg9e0ykqm1n84cerk
License
MIT-0
Free to use, modify, and redistribute. No attribution required.