agentleFS
fal-ai-communityfal-ai-community/skills/skills/fal-shot-craft/SKILL.md

fal-shot-craft

Skill265 starsChanged 10 days agoMITView on GitHub

Write or improve one fal video shot prompt. Use for physical action, motivated cameras and continuity anchors; do not use for full film assembly.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the production guide for this workflow.

    line 8
  2. Very specific:

    Before execution, map host-specific tools to available capabilities.

    line 11
  3. Distinctive:

    Do not infer authorization from a guide's defaults or mandatory review language.

    line 15
  4. Distinctive:

    Check that the required local Python, Node, browser, renderer and media tools exist before using them.

    line 17
  5. Distinctive:

    Read supporting references from this skill folder as the guide directs.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Fal Shot Craft

Read the production guide for this workflow. It preserves fal's published production guidance, not a promise that every host tool exists here.

Before execution, map host-specific tools to available capabilities. Use genmedia for model calls in terminal agents, or the installed fal MCP tools in plugin hosts. Resolve current endpoints and inspect their contracts; the guide's model names and prices are dated candidates. Preserve the user's model, provider, scope and budget. Do not infer authorization from a guide's defaults or mandatory review language.

Check that the required local Python, Node, browser, renderer and media tools exist before using them. Install publicly documented dependencies only within the user's authorized setup. Otherwise report the missing dependency and stop the dependent stage. This package does not supply hosted execution or an asset library.

Read supporting references from this skill folder as the guide directs. Record actual request IDs and output paths. Deliver only artifacts you inspected; identify incomplete stages and unverified checks.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.