← Scene SoundCONTENT HISTORY
WHAT CHANGED
Update to Scene Sound
Snapshot Nov 12, 2026 · 00:09 UTC · version 1.0.1
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Scene Sound and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Add sound to silent videos. Use for the workflow below with attached media.",
"included_files": [],
"name": "scene-sound",
"skill_md_contents": "---\nname: scene-sound\ndescription: Add sound to silent videos. Use for the workflow below with attached media.\n---\n\nGenerate sound effects and ambience for an attached silent MP4 or MOV clip up to ten seconds and 50 MB. Describe the sounds and output duration, then watch the result inline with playback, fullscreen, Open and Download. Synthesized timing and sounds may vary. Existing dialogue preservation and music licensing are not provided.\n\nUse the connected Scene Sound MCP tools. Pass the actual chat attachment object into `video`; HTTPS source fields are alternatives. Never invent attachment references or send a local filesystem path to the remote server. If the host has not exposed a downloadable attachment reference, state that limitation. Ask for missing sources or required preferences before generation.\n\nCall `scene_add_sound` once for the requested output. Wait for its synchronous response. Present the real inline widget; do not substitute a website link or an unrelated image editor. If the tool is unavailable, explain that the connection must be enabled. Do not download or execute external helper code. An uncertain timeout must not trigger an automatic retry. Use `scene_add_sound_preview` with an actual returned generation ID to reopen a completed result without generating again.\n\nInputs are processed by Firemoon and its media providers; media links are accessible to anyone holding them. Respect the user's requested scope. Never claim success after a tool error or guarantee exact fidelity.\n\n## Guest access and optional account linking\n\nStart by calling the workflow tools directly. Do not request account linking before using the anonymous daily image/video allowance. Guests share 100 image/video outputs per host guest identity per UTC day; each image variation counts separately. Only offer account linking when the tool returns an authentication challenge or the user explicitly wants to use account credits. Never invent a guest identifier or bypass a quota response. Preserve existing attachment requirements and uncertain-job retry safeguards. Account linking accesses existing account entitlements. Do not list plans or credit packs, promote digital upgrades, or create checkout links in the plugin.\n"
}SHA-256 of public snapshot: 36e316afbcb6acf4ece6af6551f8385b8df11714500f5d8117a3a137fc47f966