Multi Variant Scripting
v1.0.0Produce 2-4 genuinely distinct video script variants from a single brief — technical/cinematic (A), general/walkthrough (B), developer/explainer (C). Uses in...
⭐ 0· 51·0 current·0 all-time
byNissan Dookeran@nissan
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and description (produce multiple distinct script variants) match the SKILL.md content: guidance, templates, and checklist for writing A/B/C variants. There are no unrelated requirements (no binaries, env vars, or installs) that would be inconsistent with a writing tool.
Instruction Scope
SKILL.md contains only writing methodology, templates, checks, and handoff format. It does not instruct the agent to read local files, access environment variables, call external endpoints, or collect unrelated system data. Mentions of external actors ('Finn', 'Nissan') are workflow labels in the doc and are not accompanied by network or upload instructions.
Install Mechanism
No install specification or code files are present. This is lowest-risk (instruction-only) — nothing is written to disk or fetched at install time.
Credentials
The skill declares no required environment variables, no primary credential, and no config paths. That aligns with a pure writing/templating skill. There are no secret names or unrelated credential requests.
Persistence & Privilege
The skill is not always:true and does not request persistent or elevated privileges. It does not modify other skills' configs or system settings in the instructions.
Assessment
This skill is an instruction-only template for writing multiple script variants and appears internally consistent and low-risk. Before installing/use: (1) verify that your production tooling (e.g., any system named 'Finn') does not automatically accept or publish handed-off scripts—this SKILL.md does not define any automatic uploads but your environment might; (2) avoid pasting secrets or private data into briefs you hand to the skill, since the skill's instructions assume local operation but your agent's environment may be configured to sync outputs externally; (3) if you expect integration with a build/production pipeline, confirm that separate connectors (not part of this skill) handle that and have appropriate access controls; (4) if you want stronger guarantees about no network egress, validate agent/runtime network policies—SKILL.md states outbound:false, but enforcement depends on the runtime. Overall, the skill appears coherent and safe to use as a writing-helper.Like a lobster shell, security has layers — review code before you run it.
latestvk979z8eayp9116vfy10gt486v983rkp7
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🎬 Clawdis