smyx-poop-clean-trigger-analysis@1.0.16
CAUTION· static onlyPublisher claims: "Triggers when a user provides a dog toilet / pet defecation-zone video URL or file for analysis; uses a fixed camera on the dog toilet or designated defecation area to monitor video in real time, detects whether the pet is defecating (presence of feces) and, once the pet leaves the area, automatically outputs a cleaning trigger signal that can drive a robot vacuum to that spot for cleanup. Enables fully automated pet-waste handling, reduces owner workload, and keeps the home hygienic. Application: indoor dog toilets, balcony defecation zones, pet kennels. Does NOT provide medical diagnosis — only outputs vision-based event detection results. | 当用户提供狗厕所或宠物固定排便区域视频URL或文件时,触发本技能进行排便事件检测分析;通过安装在狗厕所或宠物固定排便区域的摄像头实时分析视频,识别宠物是否在该区域排便(粪便出现),并在宠物离开该区域后自动输出清扫触发信号,联动扫地机器人前往清理;实现宠物排泄物的即时自动化处理,减轻主人清理负担,保持居家环境卫生。应用场景:宠物家庭室内狗厕所、阳台排便区、宠物笼舍。仅输出基于视觉的事件检测结果,不进行医疗诊断。" Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
What changed since 1.0.15
vet-skills diff smyx-poop-clean-trigger-analysis 1.0.15 1.0.16In the sandbox, this version reached for nothing 1.0.15 did not. Compared from the two recorded runs, not from source.
1.0.16 was not run in the sandbox (static only); the comparison covers what static analysis recorded only.
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 analysed it statically (a sandbox run is pending) on 2026-11-18 and scored it 68/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
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.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-open-h5: "http://192.168.1.234:4100"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.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.
What would make this Verified
12 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim smyx-sunjinhui: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- URL to a private-network address≈ +1 on the totalReplace encoded or assembled strings with plain literals and remove undeclared network calls.