agentleFS
aedev-toolsaedev-tools/kling-4-prompting-skill/skills/kling-4-prompting/SKILL.md

kling-4-prompting

Skill1 starsChanged 28 days agoMITView on GitHub

Write, revise, or troubleshoot Kling 4.0 video prompts from scene ideas, images, video references, storyboards, or keyframes. Use for prompt writing and shot planning; does not generate videos.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. vargHQ/skills★ 23same name
    2. glitterpixely/skills★ 6same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use information already supplied.

    line 15
  2. Distinctive:

    Do not load every reference for an ordinary single-shot request.

    line 25
  3. Distinctive:

    Check the brief against the draft:

    line 37
  4. Distinctive:

    Do reference roles conflict with the requested change?

    line 41
  5. Distinctive:

    Write prompts only unless the user separately requests generation.

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Kling 4 prompting

Translate the user's creative intent into a ready-to-use video prompt. Keep simple requests simple. Preserve their subject, supplied assets, sequence, spoken words, language, and deliberate visual choices.

Start with the brief

Use information already supplied. Ask a focused question only when the answer changes the result materially, such as which person to replace or which image is the endpoint. Infer ordinary creative choices and mention material assumptions outside the prompt. Do not run a compulsory questionnaire.

Separate prompt wording from interface settings. Confirm the selected model, mode, and available controls when a request depends on them. Full 4.0 capabilities do not establish Flash or third-party availability. For changing specifications, use sources.

Select only the detail you need

  • For references or a footage edit, read references and editing.
  • For multiple shots or keyframes, read shots and keyframes.
  • For illustrative prompts or a failed result, read the relevant section of examples.

Do not load every reference for an ordinary single-shot request.

Direct the shot

Describe visible behavior that can unfold in the requested time. Use a clear subject, an action, and an intelligible camera position. Add setting, lighting, texture, and audio where they help the requested result. Avoid padding every scene with film-stock names, arbitrary lens specifications, or unrelated mood adjectives.

For an existing image, spend the prompt on what changes. For a scene from scratch, establish the appearance and location first. Tie camera direction to the action. A fixed camera can watch a turning subject; an orbit moves the viewpoint. These are different instructions.

For speech, identify the speaker, preserve the exact requested words and language, and give space for pauses and reactions. If the lines cannot reasonably fit, offer a shorter script or longer clip without silently rewriting the dialogue. Distinguish ambient sound from music; silence can be intentional.

Check before returning

Check the brief against the draft:

  • Can the described actions fit the available time?
  • Does the camera receive incompatible directions at the same moment?
  • Do reference roles conflict with the requested change?
  • Is the prompt asking to preserve something it also replaces?
  • Are all asset labels backed by supplied media and confirmed ordering?
  • Are suggested settings actually available, or clearly conditional?

For a failed result, change the instruction most closely related to the failure first. Explain the revision briefly. Prompt wording cannot guarantee exact identity, text, timing, or motion.

Return the result

Lead with one copyable prompt in a fenced text block. Follow with only necessary reference assignments, settings, or assumptions. Label an illustrative asset mapping as such; unresolved labels are not a finished runnable prompt.

Match the user's requested prompt language. Keep dialogue in its requested language even if the surrounding direction uses another language. Offer alternatives when requested or when a real creative fork needs a choice.

Write prompts only unless the user separately requests generation. Do not invent tests, generated clips, benchmark scores, or credit savings. Suggestions here are direction to try, not measured output improvements.

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.