← PikaCONTENT HISTORY

Update to Pika

Snapshot Oct 10, 2026 · 06:12 UTC · version 0.5.3

Collection source: downloaded plugin package.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Use when the user asks Pika to make or edit an image, video, music, sound effect or voiceover and no more specific Pika skill fits.",
  "included_files": [],
  "name": "pika-create",
  "skill_md_contents": "---\nname: pika-create\ndescription: Use when the user asks Pika to make or edit an image, video, music, sound effect or voiceover and no more specific Pika skill fits.\n---\n\n# Make or edit media with Pika\n\n1. **Pick the app's tool.** Each Pika app is its own tool; choose by the task, not the output type. A purpose-built app (`headshot`, `product_ad`, `relight_media`, …) beats `create_video` or `create_image`, which fit when none does or the user names a model (pass it as `model`). If the user wants to look around, call `browse_apps` and read their pick with `get_panel`.\n2. **Gather inputs in one message.** Map what the user already said into the tool's fields. For anything missing:\n   - their photo, clip or audio → `ask_for_media` (pass `kind` when the field takes one kind, `app` with the app's id, and a short `purpose` such as \"the photo becomes the first frame\");\n   - an earlier Pika result → `show_creations`;\n   - a style, template, effect, voice or other choice → `list_presets` when the field's description names a collection or the user wants to see the choices; it lists published presets and built-in choices. An enum field's values are also its choices. A look the user describes works too.\n   Open one panel per turn, media first; show presets once the media is in.\n   When they say they uploaded or picked, call `get_panel` with that panel's `panel_id`.\n3. **Price and run it.** Call it with the input and a fresh `request_id` and no `max_credits`, then follow the quote's `next` (it applies the user's approval mode). On a yes, call it again with the same input and `request_id` and the agreed `max_credits`.\n4. **Follow `next`.** Each result names the next call, including when to wait on the job with `get_job`. Then offer the follow-ups the result suggests.\n\nJobs with no tool of their own:\n- color grade a photo or clip → `relight_media` with the look in `description` (or `edit_image` for a photo);\n- product shot from reference photos → `edit_image` with the photos in `reference_urls`;\n- sound effect or music → `create_audio`;\n- animate between a start and an end frame → `create_video` with model `pika`;\n- cut a clip down before `camera_director` (one shot of 4–30 s) or `extend_video` (at most 15 s) → `video_trim`, then pass its output url;\n- a talking head → `talking_head_studio` with a face image (`headshot` or `create_image` output, or the user's photo) and audio (the user's recording or `create_speech` output);\n- new aspect ratio for a video → `create_video` with model `seedance-25`, the clip in `video_urls`, the target `aspect_ratio`, and a prompt to recompose the scene and extend its surroundings while keeping the subjects, action, timing and on-screen text.\n\nTo stop a running job the user no longer wants, call `cancel_job`. To find a job from earlier, call `list_jobs`; to show one, `show_creations` with its `job_id`.\n"
}

SHA-256 of public snapshot: 901015024310fdeff3a47204d0a13209be2828d5284379e1c942288637af072f