Skills/ClawHub/okdata-wechat-search

okdata-wechat-search@0.1.0

CAUTION· static only

Publisher claims: "微信搜一搜与微信指数：用 okdata 接口读微信搜一搜的公开数据，包括微信搜一搜综合搜索、微信公众号实时查找、微信指数、微信搜一搜推荐词、微信小程序搜索、微信搜一搜综合搜索（备用版）等，不用登录、不用 Cookie，按次付费、失败不收费。适用于在微信搜一搜里搜文章、视频号和小程序、查关键词的微信指数走势、找某个领域的公众号、看搜一搜的推荐词，挖用户在搜什么。 WeChat Search (Sou Yi Sou) and WeChat Index public data for AI agents through the okdata API (remote MCP or HTTP), paid per call." Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher conn-ho · publishing for 2 daysInstalls 44Last detonated 3 h ago
What would fix thisWatchDispute verdict

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-14 and scored it 67/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 only
t+CategoryObserved action

This 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 134 lines in 2 files.

Cost to the agent

Instructions loaded
≈889 tok
1 file · 2 in bundle

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

13 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim conn-ho: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
Publish a new version to ClawHub, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim conn-hoPropose a patch to the maintainer