SkillAgentSearch skills...

scenario-sonilo

Use when adding sound to a video or generating standalone audio with Sonilo models on Scenario via MCP: text-to-sound-effects, text-to-music, video-to-sound-effects or video-to-music from a clip, scoring silent AI video, foley, ambience, muxed video-to-video variants returning the clip with the new…

Install / Use

npx skills add scenario-labs/skills --skill scenario-sonilo

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

82/100

Category

Other

Supported Platforms

Universal

Our assessment of scenario-sonilo

scenario-sonilo scores 82/100 on our quality scale, 276th of 329 Other skills we index.

Its SKILL.md is 6.2 KB long, split into 7 sections and no code examples: a thorough specification that gives an agent plenty to work with.

With 1,048 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
11/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 29 days ago, so scenario-sonilo is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-11-09. Automated pattern scan on 2026-11-09. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

scenario-sonilo compared with similar skills

All 4 of these similar skills score higher than scenario-sonilo; compare them before choosing.

SkillScoreStarsUpdatedFormat
scenario-sonilo (this skill)by scenario-labs821.0k29d agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
headroomby headroomlabs-ai10079.8ktodayCLAUDE.md
CowAgentby zhayujie10048.0ktodayCLAUDE.md

Frequently asked questions

How do I install scenario-sonilo?
Run npx skills add scenario-labs/skills --skill scenario-sonilo. The install tabs above show the steps for each supported agent.
Which AI agents does scenario-sonilo work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is scenario-sonilo safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is scenario-sonilo still maintained?
The repository was last updated 29 days ago, so scenario-sonilo is actively maintained.

name: scenario-sonilo description: "Use when adding sound to a video or generating standalone audio with Sonilo models on Scenario via MCP: text-to-sound-effects, text-to-music, video-to-sound-effects or video-to-music from a clip, scoring silent AI video, foley, ambience, muxed video-to-video variants returning the clip with the new track mixed in, keeping speech while replacing music, or per-segment sound control. Keywords: Sonilo V1.1, SFX, soundtrack, score, keepSpeechVocal, segments, royalty-free." license: MIT

Scenario Sonilo Audio

Overview

Sonilo, an audio family on Scenario, splits along two axes: what the sound is (sound effects or instrumental music) and what comes back (a standalone track, or the source video with the generated track muxed in, visuals untouched). Picking the member whose return matches the delivery matters more than any prompt. Discover with search and treat model_schema_get as the contract.

Connection and the core loop: see the scenario skill in this repo; model-agnostic audio work: the scenario-audio skill. If a sibling skill named here is missing from your available skills, load it with skill_get (Scenario MCP) or ask the user to install it (https://github.com/scenario-labs/skills#install); unattended, proceed from tool schemas and flag the gap.

Quick reference

Member names state the mode; input names come from the live schemas:

| Member | Key inputs | Returns | | ---------------------- | ------------------------------------------------------------------- | ------------------------------------------- | | Text to SFX | prompt, duration, audioFormat | one sound effect clip | | Text to Music | prompt, duration, numSamples | instrumental track | | Video to SFX | video, optional prompt or segments | audio track matching the video length | | Video to Music | video, optional prompt, numSamples, startOffset, duration | music track | | Video to Video SFX | as Video to SFX | the video with SFX mixed in, plus the track | | Video to Video (music) | as Video to Music, plus keepSpeechVocal | the video with music mixed in |

At authoring time: text SFX ran 1 to 180 seconds (default 8), text music 1 to 600 (default 90), video inputs took up to 360 seconds, segments up to 50, numSamples 1 to 3, and startOffset moved in steps of 10 with startOffset plus duration capped at the video length. audioFormat (aac default, mp3, wav, flac; wav or flac for editing pipelines) exists on the SFX members only, and on the muxed one it formats the separate track: the video's own audio stays AAC. Two music mux members were live with the same schema; prefer the newest hit. Every duration knob carries cost, so dry_run before a batch.

The video is the clock

On video-conditioned members the footage decides when sound happens and the prompt only steers what it sounds like; the clip's own audio never steers generation, visuals alone are read. An empty prompt is valid and often best: the model captions the clip and covers each scene itself. When one description cannot fit the whole clip, segments gives per-range prompts, contiguous by contract: the first start is 0, each end equals the next start, and the last stays within the video. Text to SFX has no timing control at all, so describe one sound event per run, physical words over moods (hollow, muffled, punchy), source then material then space then intensity, with the duration intent in the wording as well as the parameter. No member takes a seed, so archive the takes you like; on the music members numSamples buys up to three takes in one run instead of re-rolls.

What survives a music pass

The music mux members replace the whole original track by default. keepSpeechVocal: true isolates human voice (dialogue, narration, singing, crowds) and ducks the music under it; everything non-voice (engines, footsteps, ambience, prior foley) is replaced regardless. So never score a clip after muxing foley into it: when a video needs both, take standalone tracks from Video to SFX and Video to Music and mix in post. Music comes back instrumental.

Worked example: foley for a silent gameplay clip

  1. search with target="models", query="sonilo", public=true. Members list txt2audio, video2audio, or video2video capabilities; e.g. model_sonilo-v1-1-video-to-video-sound-effects (a live hit at authoring time: re-discover each session).
  2. model_schema_get with that id: fields and caps before anything else.
  3. upload_asset the clip (see the scenario skill) to get its asset id.
  4. model_run with that model_id, dry_run=true, and parameters={"video": "asset_x", "segments": [{"start": 0, "end": 4, "prompt": "footsteps on wet metal, close and sharp"}, {"start": 4, "end": 12, "prompt": "plasma rifle shots, hollow hangar reverb"}]}: cost scales with clip length.
  5. Repeat model_run with wait=false, then jobs_wait with the returned job id, re-called with pending_job_ids on timeout, never a second model_run.
  6. asset_display the muxed video, then asset_download it and the separate track.

Common mistakes

  • Muxing when the edit needs a bare track, or the reverse: Video to SFX returns audio only; Video to Video SFX returns the finished clip. Pick by delivery.
  • Scoring a clip that already carries foley with a music mux member: non-voice sound is replaced and the foley is gone.
  • Leaving keepSpeechVocal off (the default) on a talking-head clip: the narration vanishes with the rest of the track.
  • Gapped or overlapping segments: the contract wants contiguous ranges from 0.
  • Packing sequenced events into one Text to SFX prompt: it has no timing control; one event per run.
  • Asking any member for speech or vocals: no member produces dialogue, narration, or singing; SFX and instrumental music are the whole surface.

Related Skills

View on GitHub
GitHub Stars1.0k
CategoryOther
Updated29d ago
Forks129

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions