Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Explainer Video Guide

v0.1.5

Explainer video production guide: scripting, voiceover, visuals, and assembly. Covers script formulas, pacing rules, scene planning, and multi-tool pipelines...

0· 763·2 current·2 all-time
byÖmer Karışman@okaris

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for okaris/explainer-video-guide.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Explainer Video Guide" (okaris/explainer-video-guide) from ClawHub.
Skill page: https://clawhub.ai/okaris/explainer-video-guide
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install explainer-video-guide

ClawHub CLI

Package manager switcher

npx clawhub@latest install explainer-video-guide
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
The name and description (explainer video production: scripting, voiceover, visuals, assembly) align with the SKILL.md content: pacing rules, scene templates, TTS and model examples. The runtime examples all call infsh model runs, which is coherent with the stated multi-tool pipeline focus.
Instruction Scope
Instructions stay within video production scope (script formulas, scene prompts, TTS pacing, image->video workflows). They do instruct the agent/user to install and use the infsh CLI and to run infsh login, which implies contacting an external service and providing credentials; those credentials are neither declared in requires.env nor explained. The SKILL.md references local paths for images (e.g., path/to/workspace-still.png) which is expected for content pipelines.
!
Install Mechanism
The guide recommends running curl -fsSL https://cli.inference.sh | sh (pipe-to-shell) and downloading a binary from dist.inference.sh. Pipe-to-shell installs are high-risk because they execute remote code immediately. The SKILL.md claims checksum verification and links to a checksums file, but the instructions still direct an unattended pipe-to-sh flow rather than a manual, verifiable install. The install source is a third‑party domain rather than a widely-known release host; this increases risk and warrants manual verification before running.
Credentials
The skill declares no required env vars or credentials, which is consistent with being instruction-only. However, it instructs the user to run infsh login (implying account/API credentials) but does not document what credentials or scopes are needed. That omission is not necessarily malicious, but users should expect to provide/authorize external service credentials when using the CLI and should confirm what data is uploaded to the service.
Persistence & Privilege
No install spec, no code files, always:false, and no requests to modify other skills or system-wide configs. The skill does not request persistent system presence or elevated privileges.
Assessment
This skill is coherent with its purpose (video-production recipes that call a third‑party CLI). Before installing or running the suggested curl | sh, verify the authenticity of cli.inference.sh and its checksums (prefer manual download + verify SHA-256). Be cautious of running pipe-to-shell installs and of granting the external service account access (infsh login) — review what data (video frames, audio, scripts) will be uploaded and what permissions the API key/session grants. If you prefer lower risk, follow the manual install & verification links in the SKILL.md or use local tooling you already trust.

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

latestvk9798f7c5jqwgwaqeqrmnc89gn81cs08
763downloads
0stars
2versions
Updated 16h ago
v0.1.5
MIT-0

Explainer Video Guide

Create explainer videos from script to final cut via inference.sh CLI.

Quick Start

curl -fsSL https://cli.inference.sh | sh && infsh login

# Generate a scene for an explainer
infsh app run google/veo-3-1-fast --input '{
  "prompt": "Clean motion graphics style animation, abstract data flowing between connected nodes, blue and white color scheme, professional corporate aesthetic, smooth transitions"
}'

Install note: The install script only detects your OS/architecture, downloads the matching binary from dist.inference.sh, and verifies its SHA-256 checksum. No elevated permissions or background processes. Manual install & verification available.

Script Formulas

Problem-Agitate-Solve (PAS) — 60 seconds

SectionDurationContentWord Count
Problem10sState the pain point the viewer has~25 words
Agitate10sShow why it's worse than they think~25 words
Solution15sIntroduce your product/idea~35 words
How It Works20sShow 3 key steps or features~50 words
CTA5sOne clear next action~12 words

Before-After-Bridge (BAB) — 90 seconds

SectionDurationContent
Before15sShow the current frustrating state
After15sShow the ideal outcome
Bridge40sExplain how your product gets them there
Social Proof10sQuick stat or testimonial
CTA10sClear next step

Feature Spotlight — 30 seconds (social)

SectionDurationContent
Hook3sSurprising fact or question
Feature15sShow one feature solving one problem
Result7sThe outcome/benefit
CTA5sTry it / Learn more

Pacing Rules

Content TypeWords Per MinuteNotes
Standard narration150 wpmConversational pace
Complex/technical120 wpmAllow processing time
Energetic/social170 wpmFaster for short-form
Children's content100 wpmClear and slow

Key rule: 1 scene per key message. Don't pack multiple ideas into one visual.

Scene Duration Guidelines

  • Establishing shot: 3-5 seconds
  • Feature demonstration: 5-8 seconds
  • Text/stat on screen: 3-4 seconds (must be readable)
  • Transition: 0.5-1 second
  • CTA screen: 3-5 seconds

Visual Production

Scene Types

# Product in context
infsh app run google/veo-3-1-fast --input '{
  "prompt": "Clean product demonstration video, hands typing on a laptop showing a dashboard interface, bright modern office, soft natural lighting, professional"
}'

# Abstract concept visualization
infsh app run bytedance/seedance-1-5-pro --input '{
  "prompt": "Abstract motion graphics, colorful data streams connecting floating geometric shapes, smooth fluid animation, dark background with glowing elements, tech aesthetic"
}'

# Lifestyle/outcome shot
infsh app run google/veo-3-1-fast --input '{
  "prompt": "Happy person relaxing on couch with laptop, smiling at screen, bright airy living room, warm afternoon light, satisfied customer feeling, lifestyle commercial style"
}'

# Before/after comparison
infsh app run falai/flux-dev-lora --input '{
  "prompt": "Split screen comparison, left side cluttered messy desk with papers and stress, right side clean organized minimalist workspace, dramatic difference, clean design"
}'

Image-to-Video for Scenes

# Generate a still frame first
infsh app run falai/flux-dev-lora --input '{
  "prompt": "Professional workspace with glowing holographic interface, futuristic but clean, blue accent lighting"
}'

# Animate it
infsh app run falai/wan-2-5-i2v --input '{
  "prompt": "Gentle camera push in, holographic elements subtly floating and rotating, soft ambient light shifts",
  "image": "path/to/workspace-still.png"
}'

Voiceover Production

Script Writing Tips

  • Short sentences. Max 15 words per sentence.
  • Active voice. "You can track your data" not "Your data can be tracked."
  • Conversational tone. Read it aloud — if it sounds stiff, rewrite.
  • One idea per sentence. One sentence per visual beat.

Generating Voiceover

# Professional narration with Dia TTS
infsh app run falai/dia-tts --input '{
  "prompt": "[S1] Tired of spending hours on reports that nobody reads? There is a better way. Meet DataFlow. It turns your raw data into visual stories... in seconds. Just connect your source, pick a template, and share. Try DataFlow free today."
}'

Pacing Control in TTS

TechniqueEffectExample
Period .Medium pause"This changes everything. Here's how."
Ellipsis ...Long pause (dramatic)"And the result... was incredible."
Comma ,Short pause"Fast, simple, powerful."
Exclamation !Emphasis/energy"Start building today!"
Question ?Rising intonation"What if there was a better way?"

Music & Audio

Background Music Guidelines

  • Volume: 20-30% under narration (duck 6-12dB when voice plays)
  • Style: match the brand tone (corporate = ambient electronic, startup = upbeat indie)
  • Structure: intro swell (first 3s) -> subtle loop under narration -> swell at CTA
  • No vocals: instrumental only under narration
# Generate background music
infsh app run <music-gen-app> --input '{
  "prompt": "upbeat corporate background music, modern electronic, 90 BPM, positive and professional, no vocals, suitable for product explainer video"
}'

Assembly Pipeline

Full Production Workflow

# 1. Generate voiceover
infsh app run falai/dia-tts --input '{
  "prompt": "[S1] Your script here..."
}'

# 2. Generate scene visuals (in parallel)
infsh app run google/veo-3-1-fast --input '{"prompt": "scene 1 description"}' --no-wait
infsh app run google/veo-3-1-fast --input '{"prompt": "scene 2 description"}' --no-wait
infsh app run google/veo-3-1-fast --input '{"prompt": "scene 3 description"}' --no-wait

# 3. Merge scenes into sequence
infsh app run infsh/media-merger --input '{
  "media": ["scene1.mp4", "scene2.mp4", "scene3.mp4"]
}'

# 4. Add voiceover to video
infsh app run infsh/video-audio-merger --input '{
  "video": "merged-scenes.mp4",
  "audio": "voiceover.mp3"
}'

# 5. Add captions
infsh app run infsh/caption-videos --input '{
  "video": "final-with-audio.mp4",
  "caption_file": "captions.srt"
}'

Video Length by Format

FormatLengthPlatform
Social teaser15-30sTikTok, Instagram Reels, YouTube Shorts
Product demo60-90sWebsite, landing page
Feature explainer90-120sYouTube, email
Tutorial/walkthrough2-5minYouTube, help center
Investor pitch video2-3minPitch deck supplement

Transition Types

TransitionWhen to UseEffect
CutDefault between related scenesClean, professional
Dissolve/CrossfadeTime passing, mood shiftSoft, contemplative
WipeNew topic or sectionClear separation
Zoom/PushDrilling into detailFocus attention
Match cutVisual similarity between scenesClever, memorable

Common Mistakes

MistakeProblemFix
Script too wordyVoiceover rushed, viewer overwhelmedCut to 150 wpm max
No hook in first 3sViewers leave immediatelyStart with the problem or surprising stat
Visuals lag narrationConfusing disconnectVisuals should match or slightly precede words
Background music too loudCan't hear narrationDuck music 6-12dB under voice
No captions85% of social video watched silentAlways add captions
Too many ideasViewer retains nothingOne core message per video

Related Skills

npx skills add inference-sh/skills@ai-video-generation
npx skills add inference-sh/skills@video-prompting-guide
npx skills add inference-sh/skills@text-to-speech
npx skills add inference-sh/skills@prompt-engineering

Browse all apps: infsh app list

Comments

Loading comments...