smyx-pet-hospital-waiting-anxiety-analysis@1.0.20
VERIFIED· install onlyPublisher claims: "Triggers when a user provides a pet hospital waiting area video URL or file for analysis; supports local video uploads or network URLs to call server-side APIs for anxiety-related behavior recognition, detecting open-mouth panting intensity, limb/torso trembling amplitude, ear-flattening degree and other stress signals, outputting a standardized anxiety level (1-5) to help medical staff identify high-stress pets and prioritize care or comfort (without diagnosing diseases or prescribing treatment). Application scenarios: pet hospital waiting areas, veterinary clinics, pet care institutions. Development reason: optimize visit workflow and reduce stress-related harm. | 当用户提供候诊区宠物视频的URL或文件时,触发本技能进行焦虑行为信号分析;支持通过上传本地视频或网络视频URL,调用服务端API检测张口喘气强度、四肢/躯干颤抖幅度、耳朵后贴程度等应激信号,综合输出标准化焦虑等级(1-5级),帮助医护人员识别高应激宠物并优先安排就诊或安抚(不诊断疾病、不提供治疗方案)。应用场景:宠物医院候诊区、动物诊所、宠物护理机构。" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Bundled scripts ran with no arguments; no agent task scenario for this bundle.- Tested
- 8 of 13 bundled scripts run with no arguments (the rest were not run: per-bundle cap), with decoy credentials in the environment · every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What changed since 1.0.19
vet-skills diff smyx-pet-hospital-waiting-anxiety-analysis 1.0.19 1.0.20In the sandbox, this version reached for nothing 1.0.19 did not. Compared from the two recorded runs, not from source.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-22 and scored it 89/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 1 s · 2 scenarios · 0 deviationsStatic findings
base-url-open-api: "http://192.168.1.234:9601/smyx-open-api"Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.base-url-health: "http://192.168.1.234:7070/jeecg-boot-xzgz"Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.# result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.base-url-open-h5: "http://192.168.1.234:4100"Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.| 🧑⚖️ 结果性质 | 分析结果仅供候诊流程参考,不提供疾病诊断或治疗方案 |Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.