Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Byted Data Label

v1.0.0

Seederive 非结构化数据打标平台,使用 LLM 对文本、语音、图片数据进行批量分析处理。 当用户提到以下任何场景时必须使用此 Skill:数据打标、标注、情感分析、标签分类、 观点提取、翻译、评论分析、水军识别、内容评分、标签库管理、提示词优化。 即使用户没有直接提到「Seederive」,只要涉及对一批...

0· 72·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The name, description, README (SKILL.md) and the included script all implement a Seederive data-labeling CLI that calls a Volcengine/Seederive OpenAPI — this is coherent with the stated purpose. However, the skill registry metadata declares no required environment variables or primary credential while the SKILL.md and the script clearly require VOLCENGINE_ACCESS_KEY and VOLCENGINE_SECRET_KEY. That metadata mismatch is unexpected and reduces trust.
Instruction Scope
SKILL.md instructs the agent to run the included CLI script and to read the packaged reference files in ${SKILL_DIR} for scenario-specific guidance. It asks the agent to read user-supplied data files (CSV/JSON) and to use two AK/SK environment variables — all these actions are within the described scope (creating/previewing/optimizing labeling tasks). The instructions do not ask the agent to read unrelated system config or to exfiltrate data to arbitrary endpoints beyond the service API.
!
Install Mechanism
There is no declared install spec, but the included Python script attempts to auto-install the 'requests' package at runtime via subprocess.check_call pip install if it is missing. Runtime package installation is a high-risk behavior (it writes to disk and executes external code) and should be made explicit in the skill metadata or avoided. No other external downloads are present in the files provided.
!
Credentials
The script and SKILL.md legitimately require VOLCENGINE_ACCESS_KEY and VOLCENGINE_SECRET_KEY to authenticate to the Seederive API, which is proportional to the skill's function. However, the skill registry metadata lists no required env vars or primary credential — an inconsistency that could cause users to unknowingly provide secrets without noticing or verifying. Also the script defaults to a specific API gateway base URL (sd6qlcofkmfq59riqgli0.apigateway-cn-beijing.volceapi.com); users may want to verify that endpoint is expected and trustworthy before supplying real credentials.
Persistence & Privilege
The skill does not request always:true, does not modify other skills or system-wide agent configuration, and only reads/writes files that are part of its documented workflow (user data files, output CSV). It will write downloaded CSV preview results to disk when requested, which is expected for this CLI.
What to consider before installing
This skill is a CLI wrapper for a Seederive/Volcengine labeling API and generally behaves as described, but take these precautions before installing or running it: - The SKILL.md and script require VOLCENGINE_ACCESS_KEY and VOLCENGINE_SECRET_KEY, but the registry metadata does not declare them — don't assume the skill will surface this requirement elsewhere. - The Python script will auto-install the 'requests' package at runtime if missing (it calls pip). Runtime installation of packages can modify your environment; prefer running in a sandbox/virtualenv or install dependencies yourself and inspect the package install commands first. - Verify the default API base URL (sd6qlcofkmfq59riqgli0.apigateway-cn-beijing.volceapi.com) is an expected Seederive/Volcengine endpoint before providing real credentials. If unsure, supply test/limited-permission keys first. - Review the included scripts (scripts/seederive.py) yourself: it performs HTTP requests (including file uploads) to the configured base URL using the AK/SK provided — that is necessary for the skill but also means your data and keys will be sent to that endpoint. - If you cannot verify the publisher or endpoint, consider running the skill only with throwaway credentials or in an isolated environment. If possible, request the skill author to update registry metadata to declare required env vars and list dependencies instead of doing runtime pip installs.

Like a lobster shell, security has layers — review code before you run it.

latestvk977hqk7e6t5mk4ra0sbadxq5h83nrza

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments