Agent skill

Facebook Diy Video Workflow

by Longxiaohao in Longxiaohao/AIvideo

Create Facebook ecommerce scripts, human-model first frames, product images, and AI-video prompts from bundled field-tested source prompts.

MITAuto-check passedMedia & Creative

Install Facebook Diy Video Workflow

skills CLI
$ npx skills add Longxiaohao/AIvideo --skill facebook-diy-video-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Longxiaohao/AIvideo facebook-diy-video-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Longxiaohao/AIvideo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/facebook-diy-video-workflow .claude/skills/facebook-diy-video-workflow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
facebook-diy-video-workflow
GitHub stars
109
Token cost
~4.9k tokens
SKILL.md length
2,573 words
Files
15 (incl. references)
Skills in repo
2
Repo updated
First seen
Licence
MIT

At a glance

Create Facebook ecommerce scripts, human-model first frames, product images, and AI-video prompts from bundled field-tested source prompts.

  • Works in 6 steps: When any high-risk signal is present,… → Recommend avoiding topology-critical… → Do not treat a successful storyboard… → …
  • Talking-head first frames
  • SKILL.md covers Preserve Prompt Integrity, Select a Prompt, Screen Complex Products and Route Human-Model First Frames, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Facebook Diy Video Workflow is an agent skill from Longxiaohao/AIvideo. Create Facebook ecommerce scripts, human-model first frames, product images, and AI-video prompts from bundled field-tested source prompts. Use for talking-head first frames, GPT Image 2 character images, Facebook spoken scripts, DIY reference-video recreation, parent-child DIY image-to-video, multi-scene product images, first-person unboxing, Veo/Grok prompts, Seedance Fast prompts, precise diamond-painting, pearl-painting, dot-drill, or fuse-bead placement shots, PromptHub face-mask preprocessing, and…

Its SKILL.md is about 4.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 17 other files, including reference files (for example `agents/openai.yaml`, `references/complex-product-generation-risks.md` and `references/face-mask-preprocessing.md`).

It sits in Media & Creative, covering AI video generation. It works with Seedance. The licence is MIT.

When your agent uses it

  • Talking-head first frames
  • GPT Image 2 character images
  • Facebook spoken scripts
  • DIY reference-video recreation

Example prompts

  • “/facebook-diy-video-workflow”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. When any high-risk signal is present, read and apply references/complex-product-generation-risks.md.
  2. Recommend avoiding topology-critical generation, full disassembly, full assembly, or exact routing shots by default. For company work…
  3. Do not treat a successful storyboard image or grid as proof that image-to-video is feasible. State that temporal consistency can still…
  4. Produce the required feasibility note before generation. Preserve the communication purpose of the shot while proposing a finished-result…
  5. Continue only when the user still requires generation. Validate the first generated image against the exact structure at full size, then…
  6. Stop the image-to-video branch if a critical part, path, endpoint, count, connection, or perspective relationship is wrong or drifts…

What it can do on your machine

Read from SKILL.md and the folder at commit d64e145. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Facebook Diy Video Workflow loads about 4.9k tokens when it runs, and up to ~17k if it reads all its reference files. Until then it costs about 230 tokens; SKILL.md has 2,573 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~230
When it runs · the whole SKILL.md, loaded when a task matches
~4.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~17k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Longxiaohao/AIvideo at commit d64e145, republished under its MIT licence (© Longxiaohao). 2,573 words, ~4,917 tokens.

Download SKILL.mdSave it as .claude/skills/facebook-diy-video-workflow/SKILL.md (or your agent's skills folder). This skill also uses 14 other files; get the full folder from GitHub.
name
facebook-diy-video-workflow
description
Create Facebook ecommerce scripts, human-model first frames, product images, and AI-video prompts from bundled field-tested source prompts. Use for talking-head first frames, GPT Image 2 character images, Facebook spoken scripts, DIY reference-video recreation, parent-child DIY image-to-video, multi-scene product images, first-person unboxing, Veo/Grok prompts, Seedance Fast prompts, precise diamond-painting, pearl-painting, dot-drill, or fuse-bead placement shots, PromptHub face-mask preprocessing, and feasibility checks for products with complex wires, clips, repeated parts, disassembly, or installation. Route detailed bead-craft Seedance requests through a full-size first-frame quality gate and other Seedance requests to Fast; route parent-child DIY through GPT Image 2 before Veo/Grok; recommend converting complex shots. Treat all bundled prompt files as immutable source text.

Facebook DIY Video Workflow

Use the bundled original prompts without rewriting them.

Preserve Prompt Integrity

  • Do not edit, rewrite, optimize, translate, condense, extend, or merge any bundled prompt.
  • Read the selected reference file completely before using it.
  • Keep the stored prompt text unchanged. Supply product details and attachments as separate user inputs.
  • Do not fill an unfinished field or infer a missing production step unless the user explicitly provides that information.
  • Pass new constraints alongside the original prompt instead of modifying the prompt file.

Select a Prompt

Screen Complex Products

Before any image or video generation, inspect the product for complex wires, cords, branches, endpoints, connectors, repeated clips, dense edges, grids, transparent overlaps, or an exact functional topology.

  1. When any high-risk signal is present, read and apply references/complex-product-generation-risks.md.
  2. Recommend avoiding topology-critical generation, full disassembly, full assembly, or exact routing shots by default. For company work, include a concise recommendation to discuss a shot conversion with the manager or project lead before spending generation credits.
  3. Do not treat a successful storyboard image or grid as proof that image-to-video is feasible. State that temporal consistency can still require many rerolls even when every still looks correct.
  4. Produce the required feasibility note before generation. Preserve the communication purpose of the shot while proposing a finished-result view, presenter shot, voice-over, real close-up, or another simpler visual.
  5. Continue only when the user still requires generation. Validate the first generated image against the exact structure at full size, then restrict each generated shot to one local area, one connector, or one simple action.
  6. Stop the image-to-video branch if a critical part, path, endpoint, count, connection, or perspective relationship is wrong or drifts during motion. Use the reference's real-footage, static-image, or editing fallback instead of attempting to hide the error with more camera movement.

For detailed bead-craft work, do not reject the shot only because it contains repeated beads or a grid. Route it through the dedicated first-frame gate, restrict the shot to one verified macro area and one-piece-at-a-time placement, and stop when the grid, numbered position, completed state, piece count, or contact relationship is wrong.

This preflight supplements the selected original prompt without modifying it.

Route Human-Model First Frames

Apply this route when the user mentions a human-model prompt, real-person first frame, talking-head character image, presenter master image, or equivalent wording in any language.

  1. Treat this as an image stage that runs before image-to-video. Do not start the Veo, Grok, or Seedance stage until the first frame passes validation.
  2. Select exactly one source prompt. Use the natural lifestyle prompt for a warm, non-influencer character whose short description, outfit, and product action come from the user. Use the beauty-presenter prompt for the specified 9:16 Chinese skincare-presenter portrait.
  3. Never merge the two source prompts. If the user explicitly requests both, run them as two separate image tasks and preserve each source file independently.
  4. For the natural lifestyle prompt, require the user's explicit values for 简要描述人物+穿搭 and 人物与产品的动作. Supply those values as separate runtime inputs; do not edit the stored source prompt or infer missing product use.
  5. For the beauty-presenter prompt, require 参考的妆容.jpg, 发箍.png, and 服装.png when the user expects the named reference matching. If any required reference is missing, ask only for the missing file instead of pretending it was supplied.
  6. When product scale matters, require a clean real-product reference plus exact dimensions, a size-comparison image, or one user-approved scale frame. Apply the size and refinement supplement; do not infer product dimensions or accept an unapproved generated image as size evidence.
  7. Submit the selected prompt to GPT Web with GPT Image 2 together with the user's references and separately supplied facts. Keep product scale, grip, contact points, clothing, hairstyle, face direction, mouth visibility, and lighting consistent with the selected prompt and references.
  8. When multiple versions are requested, generate each as a separate 9:16 image. Never return a collage, grid, split screen, or combined image in place of the independent files.
  9. Inspect every generated frame at full size. Verify natural facial identity, consistent skin texture, correct fingers and hands, unobstructed eyes and mouth, believable product geometry, correct person-product action, usable framing, and no unintended text or interface elements.
  10. Reject and regenerate the still image when any identity, anatomy, product, scale, contact, or lighting error would become visible in motion. A video prompt cannot repair a structurally wrong first frame.
  11. After product scale and contact pass validation, keep the approved frame unchanged. When refinement is requested, create a separate same-canvas reference with mosaic only over the product center, then upload the real product reference, approved scale frame, and mosaicked reference as separately labeled inputs. Freeze the product border, apparent dimensions, hands, contact points, person, camera, and scene while refining only the product center.
  12. After approval, keep this frame as the character and opening-frame anchor. If face-mask preprocessing is requested, create the separate face-mask reference next; then route to Veo, Grok, or Seedance as requested.

Because this workflow is primarily image-to-video, the first-frame image determines most of the final video's realism. Treat first-frame approval as a hard quality gate, not as an optional preview.

Prepare Face-Mask References

When the user requests face masking or a Seedance workflow needs a processed portrait reference, read and apply references/face-mask-preprocessing.md.

  1. Run this module after the character image exists and before video generation.
  2. Keep the unmasked image as the identity source and save the mask treatment as a separate reference.
  3. Do not upload user media to PromptHub or another external site without explicit authorization.
  4. Treat PromptHub as an optional external tool. Do not claim sponsorship, guaranteed availability, or permanent free access.
  5. Continue with the immutable Seedance prompt after reference preprocessing is complete.

Route Parent-Child DIY

Apply this route when the user mentions parent-child DIY or equivalent wording in any language. An explicit Seedance request still takes precedence and uses only the Seedance branch.

  1. Require a product reference image and a product size or dimension reference. Also require material-kit and picture-instruction references when their appearance cannot be established from the supplied product evidence. Do not infer product dimensions, parts, tools, or instruction content.
  2. Use GPT Image 2 for the image stage. Submit the original parent-child DIY prompt together with the user's references and separately supplied product facts.
  3. Generate the three A-version scenes as three separate 9:16 image files, one scene per generation. Never request or accept a collage, grid, split screen, triptych, contact sheet, or single combined image as the three-image deliverable.
  4. Keep the same mother, daughter, clothing, home craft room, DIY tools, and product identity across all three images. Keep product size and design locked to the references.
  5. Never place a product box on the table. The table may show only the referenced material packets, picture instruction manual, tray, and necessary DIY tools. Scene 2 must not contain the completed product.
  6. If the user explicitly requests a B version, generate a second set of three independent images. Change only camera position, natural gestures, and tabletop prop placement; keep every locked identity and product fact unchanged.
  7. After the images are complete, read and use references/veo-grok-multi-scene-prompt.md verbatim to compile the video prompt. Treat image 1 as the opening frame, image 2 as the middle-scene visual reference, and image 3 as the ending frame.
  8. Use mode E because the completed-product state, instruction-reading state without the completed product, and final presentation state require explicit scene changes. Write exact timed hard jump cuts while keeping each scene's internal camera motion continuous.
  9. For a single start-and-end-frame generation, supply image 1 as the first frame and image 3 as the last frame, while locking image 2 into the timed middle scene. For separate video units, state the first and last frame of every unit explicitly and use only generated or user-supplied frames.
  10. Produce the final prompt for Veo 3.1 or Grok as requested. Do not rewrite either bundled source prompt while connecting the image and video stages.

This route overrides the generic Veo/Grok direct route, the post-script product-display route, and the unboxing route unless the user explicitly requests separate additional deliverables.

Show full SKILL.md (969 more words)Show less

Route Detailed Bead-Craft Seedance Shots

Apply this route before the generic Seedance Fast branch when Seedance appears with 精细点钻, 点钻, 拼豆, 珍珠画, 钻石画, 编号圆圈, 连续点贴, fuse beads, Perler beads, or equivalent wording. Treat 精细化电钻 as a likely typo for 精细化点钻 only when bead-craft context is also present; do not route an actual electric-drill product here.

  1. Require a detailed macro product image before writing or running the video prompt. Require a separate product overview when the crop alone cannot establish product identity, plus the exact tool, piece shape, piece color, target positions, completed state, and real placement method.
  2. Inspect the macro image at full size. Verify that the local product pattern is sharp, the finished and unfinished areas are unambiguous, every visible bead or pixel piece has the correct shape and scale, numbered circles or peg positions are legible only where they should remain empty, and the hand-tool contact can be executed physically.
  3. Reject or regenerate the still image before video when the reference is soft, distant, overly unfinished, structurally inconsistent, missing target positions, or already contains duplicated, floating, merged, or deformed pieces. Do not expect Seedance to repair a weak first frame.
  4. Limit each video unit to one verified macro area and one simple repeated action. Place one new bead or piece at a time, preserve every previously completed position, move to a new empty target after each placement, and keep the tool tip, hand, grid, canvas, and product pattern consistent.
  5. For the exact Virgin Mary pearl-painting Shot 07 shown in the bundled example, use references/seedance-detailed-bead-placement-prompt.md verbatim.
  6. For another artwork, diamond-painting design, or fuse-bead product, keep the bundled example file unchanged and use it only as the field-tested execution reference. Build the runtime output separately from the user's verified facts. Never carry over the Virgin Mary design, 1 and 2 labels, white pearls, pink pen, 95% completion, or any other example fact unless the supplied references confirm it.
  7. Stop and request the missing or corrected image when a product fact needed by the macro action is unavailable. Do not invent a grid, label, bead color, pattern, completion percentage, tool, hand direction, or placement result.

Route Video Prompt Requests

Apply this routing after completing any explicitly requested human-model or parent-child image stage and before the script and post-script image routes:

  1. Match tool names case-insensitively and recognize equivalent wording in any language.
  2. If the request mentions Seedance together with a detailed bead-craft trigger, execute the detailed bead-craft route and its first-frame quality gate before selecting the stored high-precision example or producing a separate runtime prompt from verified product facts.
  3. Otherwise, if the request mentions Seedance, select only the original Seedance Fast prompt. Require the real product usage method, product reference, size evidence when scale matters, requested duration, aspect ratio, and any dialogue before execution. Do not reuse the example product facts as facts about the user's product.
  4. Otherwise, if parent-child DIY is present, execute the complete parent-child DIY route before producing the Veo/Grok prompt.
  5. Otherwise, if the request mentions Veo, Veo 3, Veo 3.1, Grok, a Grok prompt, multi-scene video switching, or continuous multi-angle camera movement, select only the original Veo/Grok prompt.
  6. When the Veo/Grok route is selected, preserve the prompt's A-E mode routing. Use mode E only for true scene changes with explicit timed jump cuts; keep multiple angles within one scene as continuous physical camera movement.
  7. A selected video-prompt branch overrides the default post-script three-image branch unless the user explicitly requests the images or a human-model first frame as an additional deliverable.
  8. If both Seedance and Veo/Grok are explicitly requested, produce separate outputs for each tool in the user's requested order. Never merge their source prompts.

Route Post-Script Images

Apply this routing after the spoken script is complete:

  1. Scan the user's request and generated workflow for unboxing, opening the box, opening the package, or equivalent intent in any language.
  2. If unboxing is present, require image 1 as the product and size source plus images 2, 3, and 4 as box-action references. Then run the original unboxing prompt. Produce three independent 9:16 images and a separate grid overview as requested by that prompt.
  3. Otherwise require both the product image and a size-comparison image. Then run the original multi-scene prompt. Produce three separate 9:16 image files, never a grid, collage, split screen, or combined image.
  4. If a required image is missing, pause this image branch and ask only for the missing image. Do not infer product dimensions.
  5. If the image tool can generate only one image per call, continue until the branch's required independent images are complete.

The unboxing branch overrides the multi-scene prohibition on grids only for its separate grid deliverable. Never replace its three independent images with the grid.

Run the Workflow

  1. Screen the product for complex-generation risks and apply the preflight module when needed.
  2. Complete the human-model first-frame route when explicitly requested, then check for detailed bead-craft Seedance, generic Seedance, parent-child DIY, and the remaining video-prompt, script, or image routes.
  3. Confirm the required product image, dimensions, character references, and reference video are available when the selected prompt depends on them.
  4. Generate and validate every required image reference before video generation. Stop when a first-frame defect would damage identity, anatomy, product truth, or realism in motion.
  5. Prepare a separate face-mask reference when requested, then continue through the selected video branch.
  6. Submit the original prompt together with the user's attachments and separately supplied facts.
  7. Follow the output format required by the selected prompt exactly.
  8. Preserve product truth: describe a DIY kit as a DIY kit, not as a finished handmade product.

Repository Boundaries

Keep archives, product images, reference videos, generated media, and temporary files outside this Skill. Users provide them at runtime.

© Longxiaohao, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 14 other files (references) in skills/facebook-diy-video-workflow of Longxiaohao/AIvideo.

  • SKILL.md
  • agents/openai.yaml
  • references/complex-product-generation-risks.md
  • references/face-mask-preprocessing.md
  • references/factory-old-man-unboxing-prompt.md
  • references/gpt-full-workflow.md
  • references/human-model-product-hold-size-refinement.md
  • references/human-model-prompts/beauty-presenter-first-frame-prompt.md
  • references/human-model-prompts/natural-lifestyle-first-frame-prompt.md
  • references/multi-scene-product-display-prompt.md
  • references/parent-child-diy-image-prompt.md
  • references/seedance-detailed-bead-placement-prompt.md
  • references/seedance-fast-10s-prompt.md
  • references/veo-grok-multi-scene-prompt.md
  • references/video-breakdown-recreation-prompt.md

Open the folder on GitHubat commit d64e145

Compare with similar skills

Facebook Diy Video Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Facebook Diy Video Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Facebook Diy Video Workflow this skillLongxiaohao/AIvideo109—~4.9kAutomated safety check: PassMIT
Seedancesongguoxs/seedance-prompt-skill2.9k1 repos~2.5kAutomated safety check: PassNone
SN Motion HTMLOpenSenseNova/SenseNova-Skills5.7k—~2.2kAutomated safety check: NotesMIT
Seedance Prompt Endexhunter/seedance2-skill4.2k—~3.8kAutomated safety check: PassMIT
Seedance Japanese Prompt ExamplesEmily2040/seedance-2.07.6k1 repos~898Automated safety check: PassMIT
Seedance 2 5 Video Directorliyue-aigc/seedance-2-5-video-director599—~3.5kAutomated safety check: PassMIT

Similar skills

  • Seedance

    songguoxs/seedance-prompt-skill

    This skill should be used when the user asks to "generate video prompts", "create Seedance prompts", "write video descriptions", mentions "Seedance", "seedance", "即梦", "即梦平台", "视频提示词", "视频生成"…

    2.9k GitHub starsUsed in 1 repo~2.5k tokens
    Media & CreativeAuto-check passed
  • SN Motion HTML

    OpenSenseNova/SenseNova-Skills

    Builds HTML stories where one continuous camera journey advances with page progress, using researched structure, AI stills, Seedance video clips and browser QA.

    5.7k GitHub stars~2.2k tokensUpdated 2 days ago
    Media & CreativeAuto-check: notes
  • Seedance Prompt En

    dexhunter/seedance2-skill

    Write effective prompts for Jimeng Seedance 2.0 multimodal AI video generation.

    4.2k GitHub stars~3.8k tokensUpdated 21 days ago
    Media & CreativeAuto-check passed
  • Seedance Japanese Prompt Examples

    Emily2040/seedance-2.0

    Provides Japanese prompt patterns and safe example rewrites for Seedance 2.0 video generation, with reference tags kept intact and each example labeled by risk.

    7.6k GitHub starsUsed in 1 repo~898 tokens
    Media & CreativeAuto-check passed
  • Seedance 2 5 Video Director

    liyue-aigc/seedance-2-5-video-director

    Design, derive, optimize, diagnose, and rewrite scripts or copy-ready prompts specifically for Dreamina/即梦 Seedance 2.5.

    599 GitHub stars~3.5k tokensUpdated 1 mo ago
    Media & CreativeAuto-check passed
  • Seedance Prompt Zh

    dexhunter/seedance2-skill

    为即梦 Seedance 2.0 多模态AI视频生成模型撰写高质量提示词。当用户需要使用文本、图片、视频、音频等多模态输入创作视频提示词时触发。涵盖@引用语法、运镜复刻、特效模仿、视频延长、视频编辑、音乐卡点、电商广告、短剧创作、科普教育等场景。

    4.2k GitHub stars~1.9k tokensUpdated 21 days ago
    Media & CreativeAuto-check passed

More from Longxiaohao/AIvideo

  • Create physically credible cinematic image and video prompts for giant creatures, Chinese dragons, deities, mysterious beings, disaster-scale scenes, and mythic realism.

    109 GitHub stars~335 tokensUpdated 1 mo ago
    Auto-check passed

Works with

Questions about Facebook Diy Video Workflow

What does Facebook Diy Video Workflow do?

Create Facebook ecommerce scripts, human-model first frames, product images, and AI-video prompts from bundled field-tested source prompts. Facebook Diy Video Workflow is an agent skill from Longxiaohao/AIvideo. Create Facebook ecommerce scripts, human-model first frames, product images, and AI-video prompts from bundled field-tested source prompts.

When should I use Facebook Diy Video Workflow?

Facebook Diy Video Workflow fits situations like: talking-head first frames; GPT Image 2 character images; facebook spoken scripts; DIY reference-video recreation.

How do I install Facebook Diy Video Workflow in Claude Code?

Run `npx skills add Longxiaohao/AIvideo --skill facebook-diy-video-workflow -a claude-code`. Or copy the skill folder (skills/facebook-diy-video-workflow in Longxiaohao/AIvideo) into .claude/skills/facebook-diy-video-workflow in your project. Claude Code loads it when a task matches its description.

How do I install Facebook Diy Video Workflow in Codex?

Run `npx skills add Longxiaohao/AIvideo --skill facebook-diy-video-workflow -a codex`. Or copy the skill folder (skills/facebook-diy-video-workflow in Longxiaohao/AIvideo) into .agents/skills/facebook-diy-video-workflow in your project. Codex loads it when a task matches its description.

Can I use Facebook Diy Video Workflow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Longxiaohao/AIvideo --skill facebook-diy-video-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/facebook-diy-video-workflow, .gemini/skills/facebook-diy-video-workflow, .github/skills/facebook-diy-video-workflow and .opencode/skills/facebook-diy-video-workflow in your project.

What does Facebook Diy Video Workflow need to run?

SKILL.md names no scripts, command-line tools or credentials: Facebook Diy Video Workflow is instructions for the agent only.

Does Facebook Diy Video Workflow access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Facebook Diy Video Workflow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Facebook Diy Video Workflow use?

Facebook Diy Video Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Facebook Diy Video Workflow use?

About 4.9k tokens (SKILL.md is roughly 20k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 12k tokens, read only when the agent opens those files.

What are the alternatives to Facebook Diy Video Workflow?

Skills that share tags, products or a category with Facebook Diy Video Workflow: Seedance (songguoxs/seedance-prompt-skill, 2.9k stars), SN Motion HTML (OpenSenseNova/SenseNova-Skills, 5.7k stars), Seedance Prompt En (dexhunter/seedance2-skill, 4.2k stars) and Seedance Japanese Prompt Examples (Emily2040/seedance-2.0, 7.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Facebook Diy Video Workflow?

Longxiaohao (a GitHub user) maintains it in Longxiaohao/AIvideo, which has 109 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on August 23, 2026.

Source: Longxiaohao/AIvideo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.