Update to Kling AI
Snapshot Nov 21, 2026 · 18:11 UTC · version 1.2.0
Collection source: downloaded plugin package.
Payment or plan references changed
Full description — Now says: Write Kling video prompts and storyboards, or prepare and generate approved clips with text, frames, Omni Reference, HDR, audio, and motion transfer.
Observed in published text. Live prices and checkout terms have not been verified by this change.
Up to 3 plugins free · no card required.
All fields and original values.
Full description
Oct 24, 2026 · 12:58 UTC
Use Kling AI in Codex for text-to-video, image-to-video, omni references, keyframes, or motion control, including ads, short films, and single- or multi-shot creation. Use current account capabilities and the shared lifecycle for existin...
Nov 21, 2026 · 18:11 UTC
Write Kling video prompts and storyboards, or prepare and generate approved clips with text, frames, Omni Reference, HDR, audio, and motion transfer.
Skill instructions
Oct 24, 2026 · 12:58 UTC
Use Kling AI in Codex for text-to-video, image-to-video, omni references, keyframes, or motion control, including ads, short films, and single- or multi-shot creation. Use current account capabilities and the shared lifecycle for existin...
Nov 21, 2026 · 18:11 UTC
Write Kling video prompts and storyboards, or prepare and generate approved clips with text, frames, Omni Reference, HDR, audio, and motion transfer. # Kling video generation For prompt-only or storyboard work, use [motion and shot plann...
Supporting files
Oct 24, 2026 · 12:58 UTC
[{"relative_path":"agents/openai.yaml","size_in_bytes":267},{"relative_path":"references/motion-and-shots.md","size_in_bytes":8870},{"relative_path":"references/omni-video.md","size_in_bytes":2199},{"relative_path":"references/scene-patt...
Nov 21, 2026 · 18:11 UTC
[{"relative_path":"agents/openai.yaml","size_in_bytes":319},{"relative_path":"references/motion-and-shots.md","size_in_bytes":6708},{"relative_path":"references/scene-patterns.md","size_in_bytes":3731}]
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -1,66 +1,32 @@ --- name: kling-ai-generate-video -description: Use Kling AI in Codex for text-to-video, image-to-video, omni references, keyframes, or motion control, including ads, short films, and single- or multi-shot creation. Use current account capabilities and the shared lifecycle for existing tasks. +description: Write Kling video prompts and storyboards, or prepare and generate approved clips with text, frames, Omni Reference, HDR, audio, and motion transfer. --- -# Kling AI video generation +# Kling video generation -Turn the request into coherent motion direction and one authorized remote generation. Follow the [core Skill](../kling-ai/SKILL.md) and [CLI contract](../kling-ai/references/cli-contract.md). Invoke the CLI only, with live command/model definitions. +For prompt-only or storyboard work, use [motion and shot planning](references/motion-and-shots.md) and return the requested plan. Ask for missing assets only when the intended setup requires them. Follow the [core workflow](../kling-ai/SKILL.md) for preparation, billing and results. For local calls use the [CLI contract](../kling-ai/references/cli-contract.md). Submit each authorized task at most once. -## Operating rules +## Choose the current mode -- Use CLI browser OAuth. Never request or expose API keys, tokens, cookies, authorization headers, or upload tickets. Requested preview/download URLs may be delivered, but never logged or used as permanent identities. -- Before paid generation, show the final tool/model, prompt summary, resolution or duration, ratio, count, reference roles, and actual billing information when available. Obtain explicit confirmation of these settings immediately before submission; an already confirmed unchanged step needs no repeated confirmation. If a live tool requires billing disclosure, explain its actual returned billing scope before submission without inventing prices or billing methods. -- Submit each explicitly authorized step once. Run distinct tasks and cross-media dependencies serially through the shared workflow. Never automatically retry failed or ambiguous generation. -- Discover live tools and definitions at runtime. Never hardcode model names, input roles, durations, or multi-shot fields from examples. -- Prefer media attached directly in the conversation. Pass supported CLI resource flags for auto-upload; preserve input roles and order. +- Check live `text_to_video` for text, `image_to_video` for frame-driven requests, and `omni_ref_video` for both when available. A text-only Omni Reference pair must allow no media. A frame-driven pair must declare the requested frame roles. For mixed media, check live support for every role and their combinations. +- With open model choice, prefer compatible Kling 4.0 Omni Reference when the account offers it. For speed or credit savings, consider a compatible Kling 4.0 Flash pair. Honor an explicitly named 4.0 or 4.0 Flash variant. Match it to the current full ID or declared alias and validate the tool/model pair. +- Standard 4.0 can offer first, tail and intermediate keyframes. Flash image-to-video uses a single first frame where declared. On CLI, when using named frame slots, bind them with repeatable `--input` such as `--input first_image=./first.png`. Use either named frame inputs or `--image` / `--tailImage` shortcuts for that command. +- For motion transfer, use `motion_control` with a subject image and exactly one motion source, following [Element and motion rules](../kling-ai/references/elements-motion-feedback.md). For HDR, required silence, multiple reference types, or source audio retention, use [live settings](../kling-ai/references/generation-settings.md) to filter eligible pairs before selecting one. -Read [asset workflows](../kling-ai/references/asset-workflows.md) for subjects, motions, or reference preparation. +## Quality workflow -Before generation, obtain candidates through [capability discovery](../kling-ai/references/capability-discovery.md) and honor [account visibility](../kling-ai/SKILL.md#account-visibility-and-rollout). After selection, read the [parameter module table](../kling-ai/references/model-parameters.md), loading only applicable files. Submit through [generation submission](../kling-ai/references/tool-workflows.md). For existing tasks, go directly to [task results](../kling-ai/references/task-results.md). +1. Use [motion and shot planning](references/motion-and-shots.md) and the relevant [scene pattern](references/scene-patterns.md) for the destination. Preserve the characters, product facts and continuity that anchor the scene. +2. Write in time order. Describe the opening, subject action, camera movement and ending separately. Use one primary camera movement for a short shot. For a multi-shot request, keep shot timings within total duration and submit one task. A shot preference expresses intent. Require explicit support when the user needs a fixed shot count or a single-shot guarantee. +3. Honor requested ratio, duration and resolution when supported. With unspecified ratio, preserve first-frame composition when the model permits it. Suggest about 5 seconds for one beat or 10 seconds for two connected beats when supported. Keep live defaults for unspecified settings unless the user approves a change. +4. Preserve exact dialogue and synchronize audio cues with the visible events when requested. Verify supported audio controls. Do not add narration, readable text or product claims without a request. +5. Follow the core workflow to disclose applicable billing, check balance, submit once and inspect the actual video and audio before claiming visual QA. Use the video task number for recovery and reference task numbers only to refresh their source media. -## Load recommendations by capability +## Local CLI examples -Existing-task queries skip recommendations and creative references. For new generation, read the current CLI `tool_list` response, then read exactly one file: +Replace `<model>` with the canonical ID and use the verified executable from the CLI contract. -| Tool discovery | Read | -| --- | --- | -| No `omni_ref_video` | [Standard video recommendations](references/standard-video.md) | -| `omni_ref_video` exists | [Omni and new-model recommendations](references/omni-video.md), which branches further using actual model availability | - -Then discover models through [CLI capability discovery](../kling-ai/references/capability-discovery.md). When `omni_ref_video` exists, ordinary text/image video requests must inspect its returned models together with the existing entry point in the full `who_am_i` response before deciding whether its models meet input requirements. Recommendation files govern selection; parameter modules govern payloads. Do not preload both files or branch on tool count. Discovery failure is not absence of a new tool: explain the inability to read capabilities and stop selection. Re-evaluate after reconnecting or switching account/environment; discard the invalidated branch. - -## Workflow - -1. Select the tool/model pair using recommendations and live responses, preferring a requested available model. Use the module table for specifications, required/optional inputs, and sound; do not preload irrelevant modules. -2. Read [motion and shot planning](references/motion-and-shots.md) for every new generation, edit, or variant. Select a profile governing motion budget, camera path, continuity anchors, and acceptance checks. Only read-only queries and authorized retries with unchanged parameters may skip it. Add [scene patterns](references/scene-patterns.md) when products, UGC, explainers, multi-shot stories, or social formats need further decisions. A complete existing plan does not replace motion planning. -3. Internally establish intended use, protected subjects, and target action. Ask only about blocking assets/dialogue or conflicting requirements; choose ordinary camera movement, lighting, and unspecified options reasonably instead of requiring a questionnaire. -4. Write a motion-centered prompt covering subject/camera/environment movement, rhythm, continuity, and protected elements. Translate abstract quality into lighting, materials, depth, and composition. -5. Validate parameters, check credits, and submit once through the shared workflow. After acceptance, follow task results. Do not generate comparison samples automatically or create an unrequested final version after a preview. - -## Creative constraints - -Load applicable modules for reference roles, frame order, combination caps, sound controls, and output specifications. Never silently discard unsupported inputs, convert them to text, guess fields/models/enums, or switch account/endpoint to probe availability. - -Focus the prompt on requested action and visuals. Do not add unrequested narration, on-screen text, characters, or claims. Match single/multi-shot structure to narrative intent and supported parameters; do not split into multiple paid tasks merely to add shots. - -## Quality gates - -Before submission, align duration, ratio, shot structure, and sound switches with the prompt. Actions need a beginning, progression, and end; frames need plausible transitions; multi-shot continuity must be explicit. Each ad/explainer shot needs a communication purpose. - -When the host can inspect video, check opening, key action, transitions, and ending for identity drift, deformation, flicker, discontinuity, and cropping. Listen to required dialogue/audio for wording, lip sync, and original-sound intent. Covers or still frames cannot establish motion or audio quality. Follow [shared inspection rules](../kling-ai/references/task-results.md). - -## Failure handling - -- Authorization: run the pinned CLI `login`, then verify with `who_am_i`. -- Invalid model/parameters: refresh capabilities and prepare a correction without automatically resubmitting a prior generation. -- Insufficient credits: explain and stop until recharged; do not retry automatically. -- Lost response: recover or report unknown through task results; never replay blindly. -- Provider failure: summarize safely, retain the task ID, and do not automatically resubmit. - - -Submit at most once per confirmed paid step. Runtime, polling, and link delivery follow the core CLI workflow. - -## CLI input mapping - -Always pass `--model` from the selected command's live set. `omni_ref_video` uses repeatable `--image`, `--video`, `--audio`, or declared named `--input`; it can be text-only when the model permits. For `image_to_video`, choose either `--image`/`--tailImage` or named `--input`, never both forms. `motion_control` needs a subject `--image` and exactly one `--video` or `--motionId`. CLI 0.2.1 removed `--omni` and `--flash`; do not use them. See the CLI contract before constructing a command. +```bash +kling-plugin text_to_video --model <model> "Sunset over the sea; gentle waves, slow forward camera movement" +kling-plugin image_to_video --model <model> --input first_image=./first-frame.png "Animate the waves; preserve the horizon and composition" +```
Full technical diff · 3 changed fields
changed /description
"Use Kling AI in Codex for text-to-video, image-to-video, omni references, keyframes, or motion control, including ads, short films, and single- or multi-shot creation. Use current account capabilities and the shared lifecycle for existing tasks."
"Write Kling video prompts and storyboards, or prepare and generate approved clips with text, frames, Omni Reference, HDR, audio, and motion transfer."
changed /included_files
[
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 267
},
{
"relative_path": "references/motion-and-shots.md",
"size_in_bytes": 8870
},
{
"relative_path": "references/omni-video.md",
"size_in_bytes": 2199
},
{
"relative_path": "references/scene-patterns.md",
"size_in_bytes": 4419
},
{
"relative_path": "references/standard-video.md",
"size_in_bytes": 1435
}
][
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 319
},
{
"relative_path": "references/motion-and-shots.md",
"size_in_bytes": 6708
},
{
"relative_path": "references/scene-patterns.md",
"size_in_bytes": 3731
}
]changed /skill_md_contents
"---\nname: kling-ai-generate-video\ndescription: Use Kling AI in Codex for text-to-video, image-to-video, omni references, keyframes, or motion control, including ads, short films, and single- or multi-shot creation. Use current account capabilities and the shared lifecycle for existing tasks.\n---\n\n# Kling AI video generation\n\nTurn the request into coherent motion direction and one authorized remote generation. Follow the [core Skill](../kling-ai/SKILL.md) and [CLI contract](../kling-ai/references/cli-contract.md). Invoke the CLI only, with live command/model definitions.\n\n## Operating rules\n\n- Use CLI browser OAuth. Never request or expose API keys, tokens, cookies, authorization headers, or upload tickets. Requested preview/download URLs may be delivered, but never logged or used as permanent identities.\n- Before paid generation, show the final tool/model, prompt summary, resolution or duration, ratio, count, reference roles, and actual billing information when available. Obtain explicit confirmation of these settings immediately before submission; an already confirmed unchanged step needs no repeated confirmation. If a live tool requires billing disclosure, explain its actual returned billing scope before submission without inventing prices or billing methods.\n- Submit each explicitly authorized step once. Run distinct tasks and cross-media dependencies serially through the shared workflow. Never automatically retry failed or ambiguous generation.\n- Discover live tools and definitions at runtime. Never hardcode model names, input roles, durations, or multi-shot fields from examples.\n- Prefer media attached directly in the conversation. Pass supported CLI resource flags for auto-upload; preserve input roles and order.\n\nRead [asset workflows](../kling-ai/references/asset-workflows.md) for subjects, motions, or reference preparation.\n\nBefore generation, obtain candidates through [capability discovery](../kling-ai/references/capability-discovery.md) and honor [account visibility](../kling-ai/SKILL.md#account-visibility-and-rollout). After selection, read the [parameter module table](../kling-ai/references/model-parameters.md), loading only applicable files. Submit through [generation submission](../kling-ai/references/tool-workflows.md). For existing tasks, go directly to [task results](../kling-ai/references/task-results.md).\n\n## Load recommendations by capability\n\nExisting-task queries skip recommendations and creative references. For new generation, read the current CLI `tool_list` response, then read exactly one file:\n\n| Tool discovery | Read |\n| --- | --- |\n| No `omni_ref_video` | [Standard video recommendations](references/standard-video.md) |\n| `omni_ref_video` exists | [Omni and new-model recommendations](references/omni-video.md), which branches further using actual model availability |\n\nThen discover models through [CLI capability discovery](../kling-ai/references/capability-discovery.md). When `omni_ref_video` exists, ordinary text/image video requests must inspect its returned models together with the existing entry point in the full `who_am_i` response before deciding whether its models meet input requirements. Recommendation files govern selection; parameter modules govern payloads. Do not preload both files or branch on tool count. Discovery failure is not absence of a new tool: explain the inability to read capabilities and stop selection. Re-evaluate after reconnecting or switching account/environment; discard the invalidated branch.\n\n## Workflow\n\n1. Select the tool/model pair using recommendations and live responses, preferring a requested available model. Use the module table for specifications, required/optional inputs, and sound; do not preload irrelevant modules.\n2. Read [motion and shot planning](references/motion-and-shots.md) for every new generation, edit, or variant. Select a profile governing motion budget, camera path, continuity anchors, and acceptance checks. Only read-only queries and authorized retries with unchanged parameters may skip it. Add [scene patterns](references/scene-patterns.md) when products, UGC, explainers, multi-shot stories, or social formats need further decisions. A complete existing plan does not replace motion planning.\n3. Internally establish intended use, protected subjects, and target action. Ask only about blocking assets/dialogue or conflicting requirements; choose ordinary camera movement, lighting, and unspecified options reasonably instead of requiring a questionnaire.\n4. Write a motion-centered prompt covering subject/camera/environment movement, rhythm, continuity, and protected elements. Translate abstract quality into lighting, materials, depth, and composition.\n5. Validate parameters, check credits, and submit once through the shared workflow. After acceptance, follow task results. Do not generate comparison samples automatically or create an unrequested final version after a preview.\n\n## Creative constraints\n\nLoad applicable modules for reference roles, frame order, combination caps, sound controls, and output specifications. Never silently discard unsupported inputs, convert them to text, guess fields/models/enums, or switch account/endpoint to probe availability.\n\nFocus the prompt on requested action and visuals. Do not add unrequested narration, on-screen text, characters, or claims. Match single/multi-shot structure to narrative intent and supported parameters; do not split into multiple paid tasks merely to add shots.\n\n## Quality gates\n\nBefore submission, align duration, ratio, shot structure, and sound switches with the prompt. Actions need a beginning, progression, and end; frames need plausible transitions; multi-shot continuity must be explicit. Each ad/explainer shot needs a communication purpose.\n\nWhen the host can inspect video, check opening, key action, transitions, and ending for identity drift, deformation, flicker, discontinuity, and cropping. Listen to required dialogue/audio for wording, lip sync, and original-sound intent. Covers or still frames cannot establish motion or audio quality. Follow [shared inspection rules](../kling-ai/references/task-results.md).\n\n## Failure handling\n\n- Authorization: run the pinned CLI `login`, then verify with `who_am_i`.\n- Invalid model/parameters: refresh capabilities and prepare a correction without automatically resubmitting a prior generation.\n- Insufficient credits: explain and stop until recharged; do not retry automatically.\n- Lost response: recover or report unknown through task results; never replay blindly.\n- Provider failure: summarize safely, retain the task ID, and do not automatically resubmit.\n\n\nSubmit at most once per confirmed paid step. Runtime, polling, and link delivery follow the core CLI workflow.\n\n## CLI input mapping\n\nAlways pass `--model` from the selected command's live set. `omni_ref_video` uses repeatable `--image`, `--video`, `--audio`, or declared named `--input`; it can be text-only when the model permits. For `image_to_video`, choose either `--image`/`--tailImage` or named `--input`, never both forms. `motion_control` needs a subject `--image` and exactly one `--video` or `--motionId`. CLI 0.2.1 removed `--omni` and `--flash`; do not use them. See the CLI contract before constructing a command.\n"
"---\nname: kling-ai-generate-video\ndescription: Write Kling video prompts and storyboards, or prepare and generate approved clips with text, frames, Omni Reference, HDR, audio, and motion transfer.\n---\n\n# Kling video generation\n\nFor prompt-only or storyboard work, use [motion and shot planning](references/motion-and-shots.md) and return the requested plan. Ask for missing assets only when the intended setup requires them. Follow the [core workflow](../kling-ai/SKILL.md) for preparation, billing and results. For local calls use the [CLI contract](../kling-ai/references/cli-contract.md). Submit each authorized task at most once.\n\n## Choose the current mode\n\n- Check live `text_to_video` for text, `image_to_video` for frame-driven requests, and `omni_ref_video` for both when available. A text-only Omni Reference pair must allow no media. A frame-driven pair must declare the requested frame roles. For mixed media, check live support for every role and their combinations.\n- With open model choice, prefer compatible Kling 4.0 Omni Reference when the account offers it. For speed or credit savings, consider a compatible Kling 4.0 Flash pair. Honor an explicitly named 4.0 or 4.0 Flash variant. Match it to the current full ID or declared alias and validate the tool/model pair.\n- Standard 4.0 can offer first, tail and intermediate keyframes. Flash image-to-video uses a single first frame where declared. On CLI, when using named frame slots, bind them with repeatable `--input` such as `--input first_image=./first.png`. Use either named frame inputs or `--image` / `--tailImage` shortcuts for that command.\n- For motion transfer, use `motion_control` with a subject image and exactly one motion source, following [Element and motion rules](../kling-ai/references/elements-motion-feedback.md). For HDR, required silence, multiple reference types, or source audio retention, use [live settings](../kling-ai/references/generation-settings.md) to filter eligible pairs before selecting one.\n\n## Quality workflow\n\n1. Use [motion and shot planning](references/motion-and-shots.md) and the relevant [scene pattern](references/scene-patterns.md) for the destination. Preserve the characters, product facts and continuity that anchor the scene.\n2. Write in time order. Describe the opening, subject action, camera movement and ending separately. Use one primary camera movement for a short shot. For a multi-shot request, keep shot timings within total duration and submit one task. A shot preference expresses intent. Require explicit support when the user needs a fixed shot count or a single-shot guarantee.\n3. Honor requested ratio, duration and resolution when supported. With unspecified ratio, preserve first-frame composition when the model permits it. Suggest about 5 seconds for one beat or 10 seconds for two connected beats when supported. Keep live defaults for unspecified settings unless the user approves a change.\n4. Preserve exact dialogue and synchronize audio cues with the visible events when requested. Verify supported audio controls. Do not add narration, readable text or product claims without a request.\n5. Follow the core workflow to disclose applicable billing, check balance, submit once and inspect the actual video and audio before claiming visual QA. Use the video task number for recovery and reference task numbers only to refresh their source media.\n\n## Local CLI examples\n\nReplace `<model>` with the canonical ID and use the verified executable from the CLI contract.\n\n```bash\nkling-plugin text_to_video --model <model> \"Sunset over the sea; gentle waves, slow forward camera movement\"\nkling-plugin image_to_video --model <model> --input first_image=./first-frame.png \"Animate the waves; preserve the horizon and composition\"\n```\n"
Full snapshot data
{
"description": "Write Kling video prompts and storyboards, or prepare and generate approved clips with text, frames, Omni Reference, HDR, audio, and motion transfer.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 319
},
{
"relative_path": "references/motion-and-shots.md",
"size_in_bytes": 6708
},
{
"relative_path": "references/scene-patterns.md",
"size_in_bytes": 3731
}
],
"name": "kling-ai-generate-video",
"skill_md_contents": "---\nname: kling-ai-generate-video\ndescription: Write Kling video prompts and storyboards, or prepare and generate approved clips with text, frames, Omni Reference, HDR, audio, and motion transfer.\n---\n\n# Kling video generation\n\nFor prompt-only or storyboard work, use [motion and shot planning](references/motion-and-shots.md) and return the requested plan. Ask for missing assets only when the intended setup requires them. Follow the [core workflow](../kling-ai/SKILL.md) for preparation, billing and results. For local calls use the [CLI contract](../kling-ai/references/cli-contract.md). Submit each authorized task at most once.\n\n## Choose the current mode\n\n- Check live `text_to_video` for text, `image_to_video` for frame-driven requests, and `omni_ref_video` for both when available. A text-only Omni Reference pair must allow no media. A frame-driven pair must declare the requested frame roles. For mixed media, check live support for every role and their combinations.\n- With open model choice, prefer compatible Kling 4.0 Omni Reference when the account offers it. For speed or credit savings, consider a compatible Kling 4.0 Flash pair. Honor an explicitly named 4.0 or 4.0 Flash variant. Match it to the current full ID or declared alias and validate the tool/model pair.\n- Standard 4.0 can offer first, tail and intermediate keyframes. Flash image-to-video uses a single first frame where declared. On CLI, when using named frame slots, bind them with repeatable `--input` such as `--input first_image=./first.png`. Use either named frame inputs or `--image` / `--tailImage` shortcuts for that command.\n- For motion transfer, use `motion_control` with a subject image and exactly one motion source, following [Element and motion rules](../kling-ai/references/elements-motion-feedback.md). For HDR, required silence, multiple reference types, or source audio retention, use [live settings](../kling-ai/references/generation-settings.md) to filter eligible pairs before selecting one.\n\n## Quality workflow\n\n1. Use [motion and shot planning](references/motion-and-shots.md) and the relevant [scene pattern](references/scene-patterns.md) for the destination. Preserve the characters, product facts and continuity that anchor the scene.\n2. Write in time order. Describe the opening, subject action, camera movement and ending separately. Use one primary camera movement for a short shot. For a multi-shot request, keep shot timings within total duration and submit one task. A shot preference expresses intent. Require explicit support when the user needs a fixed shot count or a single-shot guarantee.\n3. Honor requested ratio, duration and resolution when supported. With unspecified ratio, preserve first-frame composition when the model permits it. Suggest about 5 seconds for one beat or 10 seconds for two connected beats when supported. Keep live defaults for unspecified settings unless the user approves a change.\n4. Preserve exact dialogue and synchronize audio cues with the visible events when requested. Verify supported audio controls. Do not add narration, readable text or product claims without a request.\n5. Follow the core workflow to disclose applicable billing, check balance, submit once and inspect the actual video and audio before claiming visual QA. Use the video task number for recovery and reference task numbers only to refresh their source media.\n\n## Local CLI examples\n\nReplace `<model>` with the canonical ID and use the verified executable from the CLI contract.\n\n```bash\nkling-plugin text_to_video --model <model> \"Sunset over the sea; gentle waves, slow forward camera movement\"\nkling-plugin image_to_video --model <model> --input first_image=./first-frame.png \"Animate the waves; preserve the horizon and composition\"\n```\n"
}SHA-256 of public snapshot: 8602977d99b0043d4b65774f3cfe010abac4e13f9917281f92b56d0fac3710f1