Narrator Ai Cli
v1.0.1Create AI-narrated film/drama commentary videos via CLI. Two workflow paths (Original & Adapted narration), 93 movies, 146 BGM tracks, 63 dubbing voices in 1...
⭐ 3· 80·0 current·0 all-time
bydob6y@4myhime
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name and description match the actual requirements: the skill is a CLI client for a remote narration/video service and legitimately needs the narrator-ai-cli binary and an API key (NARRATOR_APP_KEY). The manifest and SKILL.md reference the service endpoint (openapi.jieshuo.cn) and CLI commands for uploading files and creating tasks, which align with the stated purpose.
Instruction Scope
Runtime instructions tell the agent to run CLI commands, upload files (presigned URL → OSS PUT → callback), store config at ~/.narrator-ai/config.yaml, and use the NARRATOR_APP_KEY (or env override). These actions are expected for a video-uploading narration client, but the SKILL.md references a config file path and optional env vars (NARRATOR_SERVER, NARRATOR_TIMEOUT) even though the registry lists no required config paths and only NARRATOR_APP_KEY — a minor mismatch to be aware of. The skill will transmit uploaded media and metadata to the remote API (expected for its function).
Install Mechanism
Registry metadata reported 'no install spec', but SKILL.md includes a pip install spec pointing to a GitHub release ZIP (https://github.com/jieshuo-ai/narrator-ai-cli/archive/refs/tags/v1.0.0.zip) and the frontmatter contains an openclaw.install entry. Installing via pip from a pinned GitHub release is a common pattern and lower risk than arbitrary URLs, but it still installs third-party code from a repo you must trust. The platform currently will not auto-install (registry has no install spec), so the user or agent would need the binary present or install it manually.
Credentials
The skill declares a single primary credential NARRATOR_APP_KEY, which is proportionate for authenticating to the Narrator API. SKILL.md also documents optional env overrides (NARRATOR_SERVER, NARRATOR_TIMEOUT) and stores the key in ~/.narrator-ai/config.yaml (permissions 0600). These additional env/config details are reasonable but were not reflected in the registry's required config paths — minor inconsistency. No unrelated credentials are requested.
Persistence & Privilege
always:false and user-invocable:true (normal). The CLI will create and use its own config file in the user's home directory (~/.narrator-ai/config.yaml) and does not request system-wide privileges or modify other skills. Behavior is standard for a CLI client.
Assessment
This skill appears to be what it claims: a CLI client for a remote Narrator AI service that needs the narrator-ai-cli binary and an API key. Before installing or using it, consider: (1) verify you trust the GitHub repo (jieshuo-ai) and the API host (https://openapi.jieshuo.cn) because media and API keys are sent there; (2) the SKILL.md suggests installing via pip from a GitHub ZIP — prefer the pinned release URL over tracking main; (3) the CLI will store your API key in ~/.narrator-ai/config.yaml (permissions 0600) — use a key scoped for this service and not a high-privilege or reused secret; (4) the registry metadata omitted the install spec and the config path that appear in SKILL.md — ask the publisher to clarify or provide an official homepage/source before trusting the package; (5) if you want to limit exposure, run the CLI inside a virtualenv/container and review the repo code before installing.Like a lobster shell, security has layers — review code before you run it.
latestvk977knstr67zw1svb9d6pdwez5844wfv
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🎬 Clawdis
Binsnarrator-ai-cli
EnvNARRATOR_APP_KEY
Primary envNARRATOR_APP_KEY