cue-cn-expected-credit-loss-cn@0.1.0
CAUTION· static onlyPublisher claims: "把年报或半年报附注里预期信用损失(金融工具减值准备计提方法)那一段读成逐行可回到原句的登记表:预期信用损失概况、三阶段划分、组合计提、单项计提、前瞻性信息与账龄依据。每个数照抄附注原句并挂〔锚:…〕[S#],计提比例与滚动轧差由机检现算。不重算损失率、不判断计提是否充分、不给评级目标价、不按逾期天数自行推断阶段。Do NOT use for: 判断计提是否充分或不足、投资评级与目标价、按逾期天数重排三阶段。Triggers: 预期信用损失 / 信用减值损失 / 损失准备 / 三阶段划分 / 组合计提 / 单项计提 / 前瞻性信息" 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.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-16 and scored it 70/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
No findings across 1,529 lines in 5 files.
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
10 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim huhoo: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.