Ai Media Cli
Analysis
This appears to be a coherent setup and usage guide for an external AI media CLI, with expected but important handling of an API key, paid credits, and package installation.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
install -> recharge credits -> create API key -> set key -> config show -> models list --json -> run first image/video task
The documented workflow includes account funding and running media-generation jobs, which are expected for this CLI but can spend credits or send prompts to the service.
node | package: ai-media-generator | creates binaries: ai-media
The skill installs an external package that provides a local CLI binary. That is central to the skill’s stated purpose, but the artifact review does not include the package contents.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
create API key -> copy plaintext key now -> ai-media config set-key ...
The skill instructs users to handle a plaintext API key and configure it for the CLI, which is purpose-aligned but grants access to the user’s ricebowl.ai account.
