smyx-flowering-date-prediction-analysis@1.0.15
CAUTION· static onlyPublisher claims: "AI-powered flowering-date prediction for ornamental/cut-flower plants. From fixed greenhouse cameras or drones, captures images of flower-bud developmental stages, combines environmental sensor data — cumulative temperature (Growing Degree Days, GDD) and accumulated light (PAR or daylight hours) — and uses a pre-trained phenology model to predict the full-bloom date within the next 3-7 days. Helps growers precisely schedule pollination, harvesting and tourism activities. Scenarios: smart-agriculture greenhouses, cut-flower production bases, botanical gardens, flower tourism parks. | 通过智慧农业温室中的固定摄像头或无人机拍摄植物花蕾发育阶段的图像,并结合环境传感器提供的温度累积(生长度日,GDD)、光照累积(光合有效辐射或日照时长)等数据,利用预训练的物候模型预测未来3-7天内的开花日期(花朵完全开放)。该技能有助于温室种植者精准安排授粉、采收或观光活动。应用场景:智慧农业温室、切花生产基地、植物园、花卉观光园区。" 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.14
vet-skills diff smyx-flowering-date-prediction-analysis 1.0.14 1.0.15In the sandbox, this version reached for nothing 1.0.14 did not. Compared from the two recorded runs, not from source.
1.0.15 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-21 and scored it 66/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Hidden zero-width characters detected. 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-h5: "http://192.168.1.234:4100"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.# result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.| 🧑⚖️ 结果性质 | 分析结果仅供生产计划参考,预测日期存在 ±1-2 天误差,正式排产请结合人工巡查与历史经验 |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.
What would make this Verified
14 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim 18072937735: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Hidden zero-width characters detected≈ +4 on the totalKeep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.
- 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.