Doubao Seedream & Seedance API Skill

v1.0.3

提供火山引擎API接口,实现文本及图片生成图像和视频、视觉理解、任务管理和配置设置功能。

7· 523·5 current·5 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
high confidence
!
Purpose & Capability
Name/description claim a Volcengine (Doubao) image/video/vision integration and the included Python code (ConfigManager, API client usage, model IDs) implements that. However the registry metadata declares no required credentials or config paths while SKILL.md and the code clearly expect an ARK_API_KEY (and optional VOLCENGINE_* env vars) and write/read ~/.volcengine; this mismatch is incoherent and should be resolved before trusting the skill.
!
Instruction Scope
SKILL.md instructs cloning and running external scripts (git clone https://github.com/Lychee-AI-Team/seedream-skill.git and ./install.sh, ./scripts/configure.sh, ./scripts/verify_install.sh) and storing API keys in ~/.volcengine or .env. These steps would execute external code not present in the skill bundle and grant the installer ability to create config files and write to the user's home config directory. The runtime instructions also reference files and scripts that are not present in the included manifest, giving the agent broad discretion to fetch/run code.
!
Install Mechanism
The skill has no declared install spec in the registry despite shipping many code files. SKILL.md recommends cloning a GitHub repo and running install scripts — pulling and executing an external repository is high risk because it can install arbitrary code. The included requirements.txt shows legitimate Python deps, but the recommended 'one-click' approach would bypass any vetting of remote install scripts.
!
Credentials
Registry metadata lists no required environment variables, but SKILL.md and ConfigManager clearly expect ARK_API_KEY (and support VOLCENGINE_* variables). The code reads/writes ~/.volcengine and may persist API keys/configs; requesting API keys is appropriate for this service but the registry metadata omission is inconsistent and could mislead users. No other unrelated secrets are requested in code.
Persistence & Privilege
The skill persists state and configs under ~/.volcengine (state.json, tasks.json, history.json) which is appropriate for task management. always:false (not force-included) and autonomous invocation are default. Writing to a per-user config directory is expected but users should be aware the skill will create and modify files in their home directory.
What to consider before installing
Key things to consider before installing: - Metadata vs reality: The registry metadata claims no credentials required, but SKILL.md and the code require an ARK_API_KEY (and support VOLCENGINE_* env vars). Confirm with the publisher which is authoritative. - External install scripts: SKILL.md recommends git-cloning and running install.sh and other scripts from a third-party GitHub repo. Do NOT run install scripts from unknown sources without reviewing them — they can execute arbitrary code on your machine. Prefer to use the code included with the skill (if the platform supports it) or inspect the remote repo and install scripts first. - Config and persistence: The skill will create ~/.volcengine and write state/config files (state.json, tasks.json, history.json). If you install, review those files and consider using a dedicated/non-privileged account or an isolated environment (container) and a dedicated API key with limited scope/quota. - Verify origin and integrity: The skill's homepage/source are unknown and owner id is opaque. If you need this capability, prefer an officially published integration or verify the GitHub repository and author identity, and inspect the install.sh/scripts referenced in SKILL.md. - Least privilege: Provide a scoped API key (not your primary account key), avoid storing long-lived keys in repo files, and set file permissions (the code suggests chmod 600) where keys are stored. If you want, I can: - extract the missing files referenced by SKILL.md and search the included bundle for any install scripts or unexpected network endpoints, - point out where the code reads/writes credentials and exactly which files are modified, - or produce a checklist of safe steps to install this skill in a sandbox (Docker) and review the remote install scripts before running them.

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

latestvk97bwddcp68v9ctfgs5n6f6jc98291sw

License

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

Comments