patent-gap-supply-chain@0.1.2
CAUTION· static onlyPublisher claims: "Competitive intelligence workflow that infers supply-chain relationships from patent gaps — with trade secret assessment, competitive triangulation, negative verification, patent quality scoring, evidence freshness tracking, reverse workflow (supplier→client), and financial cross-validation. 通过"专利缺口"反推产业链关系的竞争情报工作流,集商业秘密评估、竞对三角验证、 负向验证、专利质量评分、证据时效追踪、反向工作流(供应商→客户)、财务数据交叉验证于一体。 Use when researching tech/hardware/manufacturing/pharma stocks, analyzing industry supply chains, identifying suppliers or customers, investigating patent gaps, or inferring supply-chain relationships from patent ownership. Supports both forward (patent gap → supplier) and reverse (technology owner → downstream clients) analysis directions. 触发场景:科技股研究、行业分析、产业链推断、 供应商识别、客户挖掘、专利缺口分析、专利归属查询、技术依赖分析、上下游推断 / Triggers: patent gap analysis, supply chain inference, supplier identification, customer identification, technology dependency, competitive intelligence, tech stock research, industry analysis, trade secret assessment, negative verification, patent quality, financial cross-validation, reverse supply-chain analysis. The skill starts from a patent gap (or known technology owner), evaluates trade secret likelihood, activates five verification leads with competitive triangulation, runs negative verification to rule out false positives, scores patent quality, tracks evidence freshness, then cross-validates against financial disclosures, outputting a confidence-scored supply-chain inference report." 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-09 and scored it 71/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,544 lines in 9 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
9 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim tianzhiceng297-boop: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.