ARTICLE_TO_VIDEO_SCRIPT

v0.1.0

Convert pasted articles, research reports, blog posts, and long-form content into a structured commentary video script with sections for HOOK, BODY, and LIGH...

0· 391·3 current·3 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for danielfoch/article-to-video-script.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "ARTICLE_TO_VIDEO_SCRIPT" (danielfoch/article-to-video-script) from ClawHub.
Skill page: https://clawhub.ai/danielfoch/article-to-video-script
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

Canonical install target

openclaw skills install danielfoch/article-to-video-script

ClawHub CLI

Package manager switcher

npx clawhub@latest install article-to-video-script
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the runtime instructions: the SKILL.md defines a clear article→script transform and requests only the pasted ARTICLE and a MODE. There are no unrelated binaries, credentials, or config paths requested.
Instruction Scope
Runtime instructions stay inside the stated purpose: they describe how to structure hooks, body, CTAs, and analysis. The skill does not instruct the agent to read files, access environment variables, or send data to external endpoints. It explicitly requires confirmation of mode before producing output.
Install Mechanism
No install spec and no code files are present. This is the lowest-risk delivery model (instruction-only) — nothing is written to disk or downloaded by the skill.
Credentials
The skill declares no environment variables, credentials, or config paths. All required inputs are user-provided text fields (MODE and ARTICLE), which is appropriate for a text-transformation skill.
Persistence & Privilege
always is false and the skill does not request persistent system presence or modifications to other skills. Autonomous invocation is allowed by platform default but is not combined with any elevated privileges or secret access.
Assessment
This skill is internally consistent and doesn't request credentials or install code. Before using it, avoid pasting private or sensitive documents (personal data, unreleased research, or confidential client materials) because the skill processes whatever text you provide. Also review outputs for factual accuracy and potential defamatory or biased claims, since the instructions explicitly ask for opinionated commentary. If you need guarantees about privacy or audit logging, prefer a vetted plugin that documents data handling or run transformations locally under your own control.

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

latestvk97fqcfhqx38awnnwctm57fxn1824h4r
391downloads
0stars
1versions
Updated 1mo ago
v0.1.0
MIT-0

Article to Video Script

Convert source content into a commentary-first video script.

Required Input

Expect this input format:

MODE: short or long ARTICLE: [pasted content]

If mode is missing or unclear, ask exactly: Short form (≤90s) or long form (~10 min)?

Do not produce a script until the mode is confirmed.

Global Style Rules

Apply in both modes:

  • Write with a confident, analytical, direct tone.
  • Keep language intelligent but accessible.
  • Sound like real-time creator commentary, not robotic narration.
  • Include clear opinions when warranted.
  • Avoid fluff and corporate language.
  • Do not open with praise or sugarcoating.
  • Do not use em dashes.
  • Avoid "this isn't X, it's Y" framing.
  • Avoid hype and fear-mongering.

Always structure output with these sections in order:

  1. HOOK
  2. BODY
  3. LIGHT CTA

Analysis Rules

Always:

  • Extract key stats from the source.
  • Highlight contradictions.
  • Identify incentives.
  • Clarify second-order effects.
  • Simplify complex data without losing accuracy.

Avoid:

  • Rewriting the article.
  • Reading source text verbatim.
  • Generic summary voice.

Treat this as commentary, not narration.

Short Mode (<=90 seconds)

Target 150-250 words total.

HOOK (0-7 seconds)

  • Start with a pattern interrupt.
  • Use a bold stat, claim, or sharp framing.
  • No greeting.
  • No intro fluff.

BODY

  • Deliver 2-4 tight talking points grounded in the source.
  • Cover what happened, why it matters, and what people are missing.
  • Keep sentences punchy and vertical-video friendly.
  • Avoid long explanatory detours.

LIGHT CTA (last 5-10 seconds)

  • Use soft prompts such as follow, comment, or request for deeper data.
  • Never use aggressive sales CTAs.

Long Mode (~10 minutes)

Target 1,200-1,600 words total.

HOOK (0-10 seconds)

  • Open with a bold stat, claim, or tension point.
  • Create urgency or curiosity.
  • No greeting.

BODY (Structured Sections)

  • Start BODY with a SETUP (30-60 seconds) subsection that explains what the source says and why it matters now.
  • Build 3-5 clearly labeled sections.
  • For each section include:
    • Headline
    • Explanation
    • Commentary/analysis
    • Implication
  • Include screen-direction prompts where useful, such as:
    • [Pull up chart]
    • [Show headline]
    • [Zoom into data]
  • Focus on:
    • What the data says
    • Structural implications
    • Who benefits
    • Who loses
    • What likely happens next

LIGHT CTA (final 20-30 seconds)

  • Use soft subscribe/comment/follow phrasing.
  • Keep CTA low pressure.

Output Rules

Return only the final script.

  • No process explanation.
  • No meta commentary.
  • No extra formatting outside script sections.

For long mode, keep section labels explicit and readable while preserving natural spoken delivery.

Comments

Loading comments...