Cinematic Script Writer
v1.4.6Create professional cinematic scripts for AI video generation with character consistency and cinematography knowledge. Use when the user wants to write a cinematic script, create story contexts with characters, generate image prompts for AI video tools (Midjourney, Sora, Veo), or needs cinematography guidance (camera angles, lighting, color grading). Also use for character consistency sheets, voice profiles, anachronism detection, and saving scripts to Google Drive.
⭐ 8· 2.7k·4 current·4 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The name/description (cinematic script writing, cinematography, prompt building, character consistency, storage) match the repository contents: cinematography DB files, consistency system, prompt builder, storage adapter/manager, and a CLI. Required binary is only 'node' and the install uses an npm package, which is proportional for a TypeScript/Node CLI.
Instruction Scope
SKILL.md instructs the agent/CLI to create contexts, generate scripts, build prompts, and connect to storage (Google Drive or local Downloads). Those actions require HTTP calls (OAuth) and file I/O for local saving — all within the documented scope. Be aware the storage commands will access the filesystem (Downloads fallback) and initiate an OAuth flow for Google Drive; those operations are expected but worth noting.
Install Mechanism
Installation uses npm (package name: cinematic-script-writer). npm is a standard mechanism for Node CLIs, but the skill's 'Source' and homepage are unknown; installing an npm package from an unverified publisher has the usual supply-chain risk. There are no opaque remote download URLs or extract-from-URL steps in the bundle.
Credentials
The skill declares no required environment variables or credentials. Google Drive integration is implemented via OAuth (interactive flow) per the docs, which is appropriate — it does not demand unrelated secrets or cloud credentials in env vars. Verify how OAuth client id/secret are provided at runtime (the code and config should show whether these are required or generated).
Persistence & Privilege
always is false and the skill does not request elevated/global privileges in the metadata. It reads/writes its own storage (Google Drive or local downloads) and uses an in-skill memory store; there is no evidence it modifies other skills or global agent settings.
Assessment
This skill appears coherent for cinematic script generation and includes expected functionality (cinematography DB, prompt builder, character consistency, Google Drive/local save). Before installing:
- Verify the npm package publisher and source (look up the package on the npm registry or inspect the repo) — the bundle's 'Source' is unknown.
- Review the skill's skill.json and storage-adapter/storage-manager code to confirm how Google OAuth is implemented and where tokens are stored (interactive OAuth is expected; persistent client secrets or hidden endpoints would be a red flag).
- Expect the CLI to access your filesystem (Downloads fallback) and to open an OAuth consent flow that grants Google Drive access — only proceed if you trust the publisher and the requested Drive scopes.
- If you need higher assurance, run the package in an isolated environment (container or VM), audit the package.json and runtime files, and confirm there are no unexpected network endpoints or hidden data-exfiltration logic.
If any of these checks show undisclosed credentials, unusual outbound endpoints, or persistent secrets being stored without your consent, do not install and report the package for further review.Like a lobster shell, security has layers — review code before you run it.
latestvk973vcn9n08wqt8pf1j5bt4vqx80xn64
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🎬 Clawdis
Binsnode