← SoniloCONTENT HISTORY

Update to Sonilo

Snapshot Nov 20, 2026 · 06:24 UTC · version 1.2.0

Collection source: downloaded plugin package. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.

WHAT CHANGED

Payment or plan references changed

Full description — Now says: Create licensed music, sound effects, mixed videos, translated subtitles, and dubbed videos with a Sonilo Platform account. Preserve speech, request variants...

Observed in published text. Live prices and checkout terms have not been verified by this change.

Save Sonilo and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Full description

Before

Sep 30, 2026 · 23:10 UTC

Use Sonilo safely with a Sonilo Platform account for licensed music, sound effects, video-aware audio, newly mixed videos, audio ducking, account usage, and asynchronous generation-task retrieval. Validate public HTTPS media inputs befor...

After

Nov 20, 2026 · 06:24 UTC

Create licensed music, sound effects, mixed videos, translated subtitles, and dubbed videos with a Sonilo Platform account. Preserve speech, request variants or stems, keep names and terms intact with a glossary, and retrieve existing ta...

Skill instructions

Before

Sep 30, 2026 · 23:10 UTC

Use Sonilo safely with a Sonilo Platform account for licensed music, sound effects, video-aware audio, newly mixed videos, audio ducking, account usage, and asynchronous generation-task retrieval. Validate public HTTPS media inputs befor...

After

Nov 20, 2026 · 06:24 UTC

Create licensed music, sound effects, mixed videos, translated subtitles, and dubbed videos with a Sonilo Platform account. Preserve speech, request variants or stems, keep names and terms intact with a glossary, and retrieve existing ta...

Supporting files

Before

Sep 30, 2026 · 23:10 UTC

[{"relative_path":"agents/openai.yaml","size_in_bytes":485}]

After

Nov 20, 2026 · 06:24 UTC

[{"relative_path":"agents/openai.yaml","size_in_bytes":522},{"relative_path":"references/account-and-links.md","size_in_bytes":4158},{"relative_path":"references/dubbing.md","size_in_bytes":6223},{"relative_path":"references/examples.md"...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,34 +1,43 @@
 ---
 name: sonilo-workflows
-description: Use Sonilo safely with a Sonilo Platform account for licensed music, sound effects, video-aware audio, newly mixed videos, audio ducking, account usage, and asynchronous generation-task retrieval. Validate public HTTPS media inputs before any tool call, use read-only account tools directly, start paid generation only for explicit creation or processing requests, and never direct users to pricing, checkout, subscriptions, or credit recharge.
+description: Create licensed music, sound effects, mixed videos, translated subtitles, and dubbed videos with a Sonilo Platform account. Preserve speech, request variants or stems, keep names and terms intact with a glossary, and retrieve existing tasks. Validate public HTTPS media inputs before any tool call, and send a local file only through Sonilo's own upload tool; never direct users to pricing, checkout, subscriptions, or credit recharge.
 ---
 
 # Sonilo Workflows
 
-Use the Sonilo MCP tools as the source of truth for current parameters and results.
-
-## Account identity
-
-- This plugin authenticates against Sonilo Platform at `platform.sonilo.com`
-  through OAuth. A Sonilo Platform account is required.
-- Accounts created only on `sonilo.com` belong to a separate creator account
-  system and cannot be used to authenticate this plugin.
-- Never direct users to `sonilo.com` for plugin authentication or account
-  access. Never request a password, API key, one-time code, or MFA code.
-
-## Choose the operation
-
-- Call `get_account_services`, `get_usage`, or `get_generation_task` directly for read-only requests.
-- Call `text_to_music`, `text_to_sfx`, `video_to_music`, `video_to_sfx`, `video_to_video_music`, `video_to_video_sfx`, or `audio_ducking` only when the user clearly asks to create or process media. These operations may consume credits already present in the authenticated Sonilo Platform account.
-- Use `video_to_music` or `video_to_sfx` when the user wants a generated audio track based on a video. Use `video_to_video_music` or `video_to_video_sfx` only when the user asks for a new video with the generated audio mixed in. Do not substitute a video-producing tool for an audio-only request.
-- Set `preserve_speech` for `video_to_video_music` when the user asks to keep speech in the returned video. Set `isolate_vocals` for `video_to_music` when the user asks to separate the source video's vocals and mix them with the generated music. Otherwise follow the current tool defaults.
-- Clarify an exploratory or ambiguous request before starting a paid operation. Do not require redundant confirmation when the user has already requested generation and supplied enough information.
-- Follow the current tool input schema. Do not invent local paths, public URLs, task IDs, output URLs, prices, or unsupported parameters.
+Use the connected hosted MCP schemas and returned data as the source of truth.
+This plugin does not install the local `sonilo-mcp` Python server. Do not assume
+a tool or parameter exists because it appears in that repository.
+
+For the bundled connection, use the `sonilo_platform` MCP server. If a legacy
+local `sonilo` server is also available, do not use it for this workflow or
+fall back to it after a hosted authentication error. Reconnect the hosted
+Sonilo Platform connection instead. Registered directory connections may
+use a different namespace; identify them by their hosted schemas, including
+`get_generation_task`, rather than assuming every Sonilo tool is equivalent.
+
+## Account identity and availability
+
+- A Sonilo Platform account is required. OAuth connects the user to
+  `platform.sonilo.com`. Accounts created only on `sonilo.com` belong to a
+  separate creator account system.
+- Never direct users to `sonilo.com` for plugin authentication. Never ask for
+  passwords, API keys, one-time codes, or MFA codes.
+- After validating any media inputs, call `get_account_services` before a new
+  generation to check service availability and trial allowance. Check both
+  the connected tools and `available_services`; describe an unavailable feature
+  honestly instead of silently substituting a different paid operation.
+  `analyze_video` uses the service key `video_analysis`, and
+  `generate_video_subtitles` uses the service key `proofread`; other
+  generation tools in the routing table use their tool name as the service key.
+- For account questions or a credit rejection, read
+  [account and links](references/account-and-links.md). `get_usage` reports
+  historical spending, not the remaining balance.
 
 ## Validate remote media inputs
 
-Before calling any Sonilo MCP tool for a media-input request, validate the
-user-supplied video or audio URL.
+Before calling any Sonilo MCP tool for a media-input request, validate every
+user-supplied video, audio, and subtitle URL.
 
 - Require a publicly reachable `https://` URL. Reject `http://`, `file://`,
   localhost, loopback, link-local, private-network, and other non-public URLs.
@@ -36,40 +45,142 @@
   replacement. Do not call even a read-only Sonilo tool, browse or fetch the
   unsafe URL, attempt to transform it, or start generation.
 - Do not claim that a URL is public merely because it uses HTTPS. The hosted
-  Sonilo service remains responsible for DNS resolution, redirect validation,
-  and SSRF protections when a valid-looking public URL is submitted.
+  service remains responsible for DNS resolution, redirect validation, and
+  SSRF protections. A filename or local attachment is not a public URL; do not
+  upload a user's file to a third-party host to obtain one. The only supported
+  upload path is the one below.
+
+## Use a local file
+
+When the user asks to process a file on their own machine, use the hosted
+`create_upload_url` tool if it is among the connected tools and this
+environment can send the file's bytes in an HTTP PUT.
+
+1. Proceed only when the request clearly covers that file, and say that the
+   file will be uploaded to temporary storage on the user's Sonilo Platform
+   account. Do not upload files the user did not name.
+2. Call `create_upload_url` with the file's name and its exact size in bytes.
+   It is free and creates no task. It accepts video, audio, `.srt`, and `.vtt`
+   files up to `max_upload_size_mb` from `get_account_services`.
+3. Send the raw bytes to the returned `upload_url` with one HTTP PUT, for
+   example `curl -T <path> "<upload_url>"`, adding no authorization header.
+   A 403 means the size did not match or the URL expired: request a new URL
+   instead of retrying the old one.
+4. Once the PUT succeeds, pass the returned `file_url` wherever the chosen
+   tool takes a media or subtitle URL. A `file_url` from this tool is a valid
+   input; do not ask for a public URL in its place.
+
+Treat `upload_url` as a credential for that one upload: never show it to the
+user, log it, or reuse it. Do not present `file_url` as a result or download
+link; uploads are temporary working files. If the tool is not connected or
+the PUT cannot be made here, do not try another upload route: explain that a
+public `https://` URL is needed instead.
 
-## Run a paid asynchronous operation
+## Choose the operation
 
-1. Select the narrowest generation or processing tool that matches the request.
-2. Preserve the user's creative intent and requested duration or format. Prefer the tool's default output format unless the user asks for another supported format.
-3. Call the paid tool once and retain its returned `task_id`.
-4. Treat `status: processing` only as acknowledgement that generation started.
-5. Poll `get_generation_task` with the same `task_id`, waiting about 5–10 seconds between checks when waiting is available. Avoid tight polling loops.
-6. Stop when the task succeeds or fails. If continued waiting is unavailable, report that processing is still underway and include the `task_id` for a later check.
-
-## Keep purchases outside the plugin
-
-- Do not provide or direct users to pricing, checkout, subscription, credit
-  purchase, recharge, or top-up pages. Do not add a purchase call to action.
-- If a user asks where to buy credits or subscribe, respond only that purchasing
-  or recharging Sonilo credits is not available through this plugin. Do not
-  provide a purchase URL, name an external purchase destination, tell the user
-  to visit a website, account, billing, or pricing page, or suggest a workaround.
-- If a tool reports insufficient credits or includes a purchase URL, report the
-  insufficient-credit error neutrally and do not repeat or paraphrase the URL.
-- The Sonilo Platform homepage may be shared only when the user asks for
-  developer product information, Platform account sign-in, support, privacy,
-  or legal information, but never as a route to purchase.
-- Do not share `sonilo.com` as an authentication or account-access destination
-  because its creator accounts are not accepted by this plugin.
-- Explicit generation requests may consume credits already present in the
-  authenticated user's Sonilo Platform account; this existing-credit usage is
-  not a purchase flow.
-
-## Report the result
-
-- On success, return only media URLs and metadata actually present in the task result. For video-to-video operations, identify the returned URL as a newly mixed video; never claim that Sonilo modified the source video in place.
-- On failure, report the provided error and refund status without claiming that media was created.
-- Never describe a processing task as finished or fabricate a playable artifact.
-- Keep account, usage, task, and media details scoped to the authenticated Sonilo Platform user.
+Generation and processing tools run only when the user clearly asks to create
+or process media. They may consume existing account credits. Read-only account
+and task lookups do not, and neither does `create_upload_url`. Explain options without generating anything when the
+user asks what Sonilo can do. Do not require redundant confirmation for an
+explicit, sufficiently specified generation request.
+
+| Requested result | Hosted tool |
+| --- | --- |
+| Music from a description | `text_to_music` |
+| Sound effect from a description | `text_to_sfx` |
+| Music matched to a video, delivered as audio | `video_to_music` |
+| Sound effects matched to a video, delivered as audio | `video_to_sfx` |
+| A new video with generated music | `video_to_video_music` |
+| A new video with generated sound effects | `video_to_video_sfx` |
+| Music and sound effects together, delivered as audio | `video_to_sound` |
+| A new video with music and sound effects together | `video_to_video_sound` |
+| Lower existing music under a separate voice track | `audio_ducking` |
+| Editable translated subtitles before dubbing | `generate_video_subtitles` |
+| A dubbed video per requested language | `dubbing` |
+| A creative brief for a video | `analyze_video` (also potentially charged; `mode` picks the brief) |
+| Available services and account status | `get_account_services` |
+| Historical usage and spend | `get_usage` |
+| Progress or results of an existing task | `get_generation_task` |
+| Make a local video, audio, or subtitle file usable as an input | `create_upload_url` (free; see Use a local file) |
+
+Use video-producing tools for a new video with the generated audio mixed in;
+do not substitute them for an audio-only request. Prefer a single combined
+music-and-effects tool over two separate generations for the same request.
+Do not add a paid analysis step just to choose a generation tool.
+
+## Creative controls
+
+- **Speech:** use `preserve_speech=true` on supported video-music or combined
+  tools to keep the source speech. Add `ducking=true` when music must lower
+  during speech. Use `keep_original_sound=true` instead when the user wants
+  all original audio retained. Do not pass options to tools lacking them.
+- **Variants:** use the requested `variants_num` in one supported tool call;
+  default to one. Multiple variants consume more credits and are not covered
+  by a single-run trial. A free-only request does not authorize paid variants.
+  Return a separately labeled link for each actual result, not repeated links
+  to the first result.
+- **Stems:** set `stems=true` on `text_to_music` or `video_to_music` only when
+  requested. These separate the generated music into drums, bass, vocals, and
+  other; they do not split an arbitrary source recording. If `stems_error`
+  appears, deliver the successful music and available stems, explain the
+  missing extras, and do not regenerate or claim all stems succeeded.
+- **Timed effects:** follow the selected tool's `segments` schema. Hosted
+  video-SFX tools currently expect a JSON-encoded string, starting at zero
+  with contiguous `{start, end, prompt}` intervals. Preserve requested event
+  times; represent gaps as intervals requesting no added effects. Do not send
+  isolated disjoint intervals or use the music-segment schema. Combined tools
+  have their own segment schema; inspect it before use.
+- **Analysis:** `analyze_video` writes a music brief, a sound-design brief,
+  or both (`mode` = `music`, `sfx`, or `both`, the default). Every mode
+  costs the same; ask for only the brief the user wants.
+- Preserve requested duration, language, and format; otherwise use tool
+  defaults. Ask only for missing information that affects the requested
+  result or charge, and do not invent parameters or prices.
+
+For subtitle review, glossaries, input limits, dubbing, free previews, and
+returning to finish a full video, read
+[dubbing and continuation](references/dubbing.md).
+
+## Run or retrieve a task
+
+1. Submit the chosen generation once. Retain its `task_id`, source URLs, and
+   requested parameters in the conversation so the same work can be retrieved.
+2. `status: processing` means started, not finished. Poll `get_generation_task`
+   with the same ID, waiting about 5–10 seconds between checks when available.
+3. After a timeout or interruption with a task ID, retrieve that task. Do not
+   submit a new generation. Without a task ID, report that submission status
+   is unknown; do not claim no charge or blindly retry an ambiguous request.
+4. Stop on success or failure. If waiting cannot continue, return the task ID
+   and explain how the user can ask for its status later. Do not promise
+   background monitoring that has not been scheduled.
+5. A retry after confirmed pre-generation rejection requires the user's request
+   to continue. Refresh account state; do not keep retrying insufficient-credit
+   errors. Never restart an in-progress or already completed task to check it.
+
+## Report the result and useful next step
+
+- For media inputs and outputs, return readable Markdown links using only
+  URLs actually supplied by the user or returned by the task. Label outputs
+  by language, variant, or stem. Account-help links use the configured URLs
+  in [account and links](references/account-and-links.md).
+  Identify video-to-video results as new videos, not source files edited in place.
+- A subtitle file, a creative brief, and a 15-second preview are not a finished
+  full-length video. Label them accurately and report partial results.
+- On failure, report the actual error and refund status. Say “not started” or
+  “not charged” only when the response establishes that; otherwise say the
+  status is unknown. Never fabricate media, balances, refunds, or trial counts.
+- After a successful result, describe what was produced. Suggest a next step
+  only when it uses that result, such as reviewing subtitles. Do not pitch a
+  paid follow-up, quote its price, or automatically start more work.
+- Keep account, task, and media details scoped to the authenticated user.
+
+For concrete user-facing wording, see [examples](references/examples.md).
+Examples illustrate behavior, not real balances, URLs, or completed jobs.
+
+## Account links and commerce
+
+Follow [account and links](references/account-and-links.md) for neutral
+credit errors and the few permitted informational links. Never link a page
+that offers purchases, and never use a homepage or help page as a workaround
+to route the user to one. Suppress purchase URLs, prices, and purchase
+instructions returned by tools, including preview messages.
Full technical diff · 3 changed fields

changed /description

BEFORE
"Use Sonilo safely with a Sonilo Platform account for licensed music, sound effects, video-aware audio, newly mixed videos, audio ducking, account usage, and asynchronous generation-task retrieval. Validate public HTTPS media inputs before any tool call, use read-only account tools directly, start paid generation only for explicit creation or processing requests, and never direct users to pricing, checkout, subscriptions, or credit recharge."
AFTER
"Create licensed music, sound effects, mixed videos, translated subtitles, and dubbed videos with a Sonilo Platform account. Preserve speech, request variants or stems, keep names and terms intact with a glossary, and retrieve existing tasks. Validate public HTTPS media inputs before any tool call, and send a local file only through Sonilo's own upload tool; never direct users to pricing, checkout, subscriptions, or credit recharge."

changed /included_files

BEFORE
[
  {
    "relative_path": "agents/openai.yaml",
    "size_in_bytes": 485
  }
]
AFTER
[
  {
    "relative_path": "agents/openai.yaml",
    "size_in_bytes": 522
  },
  {
    "relative_path": "references/account-and-links.md",
    "size_in_bytes": 4158
  },
  {
    "relative_path": "references/dubbing.md",
    "size_in_bytes": 6223
  },
  {
    "relative_path": "references/examples.md",
    "size_in_bytes": 6472
  }
]

changed /skill_md_contents

BEFORE
"---\nname: sonilo-workflows\ndescription: Use Sonilo safely with a Sonilo Platform account for licensed music, sound effects, video-aware audio, newly mixed videos, audio ducking, account usage, and asynchronous generation-task retrieval. Validate public HTTPS media inputs before any tool call, use read-only account tools directly, start paid generation only for explicit creation or processing requests, and never direct users to pricing, checkout, subscriptions, or credit recharge.\n---\n\n# Sonilo Workflows\n\nUse the Sonilo MCP tools as the source of truth for current parameters and results.\n\n## Account identity\n\n- This plugin authenticates against Sonilo Platform at `platform.sonilo.com`\n  through OAuth. A Sonilo Platform account is required.\n- Accounts created only on `sonilo.com` belong to a separate creator account\n  system and cannot be used to authenticate this plugin.\n- Never direct users to `sonilo.com` for plugin authentication or account\n  access. Never request a password, API key, one-time code, or MFA code.\n\n## Choose the operation\n\n- Call `get_account_services`, `get_usage`, or `get_generation_task` directly for read-only requests.\n- Call `text_to_music`, `text_to_sfx`, `video_to_music`, `video_to_sfx`, `video_to_video_music`, `video_to_video_sfx`, or `audio_ducking` only when the user clearly asks to create or process media. These operations may consume credits already present in the authenticated Sonilo Platform account.\n- Use `video_to_music` or `video_to_sfx` when the user wants a generated audio track based on a video. Use `video_to_video_music` or `video_to_video_sfx` only when the user asks for a new video with the generated audio mixed in. Do not substitute a video-producing tool for an audio-only request.\n- Set `preserve_speech` for `video_to_video_music` when the user asks to keep speech in the returned video. Set `isolate_vocals` for `video_to_music` when the user asks to separate the source video's vocals and mix them with the generated music. Otherwise follow the current tool defaults.\n- Clarify an exploratory or ambiguous request before starting a paid operation. Do not require redundant confirmation when the user has already requested generation and supplied enough information.\n- Follow the current tool input schema. Do not invent local paths, public URLs, task IDs, output URLs, prices, or unsupported parameters.\n\n## Validate remote media inputs\n\nBefore calling any Sonilo MCP tool for a media-input request, validate the\nuser-supplied video or audio URL.\n\n- Require a publicly reachable `https://` URL. Reject `http://`, `file://`,\n  localhost, loopback, link-local, private-network, and other non-public URLs.\n- For an invalid URL, explain the public-HTTPS requirement and ask for a valid\n  replacement. Do not call even a read-only Sonilo tool, browse or fetch the\n  unsafe URL, attempt to transform it, or start generation.\n- Do not claim that a URL is public merely because it uses HTTPS. The hosted\n  Sonilo service remains responsible for DNS resolution, redirect validation,\n  and SSRF protections when a valid-looking public URL is submitted.\n\n## Run a paid asynchronous operation\n\n1. Select the narrowest generation or processing tool that matches the request.\n2. Preserve the user's creative intent and requested duration or format. Prefer the tool's default output format unless the user asks for another supported format.\n3. Call the paid tool once and retain its returned `task_id`.\n4. Treat `status: processing` only as acknowledgement that generation started.\n5. Poll `get_generation_task` with the same `task_id`, waiting about 5–10 seconds between checks when waiting is available. Avoid tight polling loops.\n6. Stop when the task succeeds or fails. If continued waiting is unavailable, report that processing is still underway and include the `task_id` for a later check.\n\n## Keep purchases outside the plugin\n\n- Do not provide or direct users to pricing, checkout, subscription, credit\n  purchase, recharge, or top-up pages. Do not add a purchase call to action.\n- If a user asks where to buy credits or subscribe, respond only that purchasing\n  or recharging Sonilo credits is not available through this plugin. Do not\n  provide a purchase URL, name an external purchase destination, tell the user\n  to visit a website, account, billing, or pricing page, or suggest a workaround.\n- If a tool reports insufficient credits or includes a purchase URL, report the\n  insufficient-credit error neutrally and do not repeat or paraphrase the URL.\n- The Sonilo Platform homepage may be shared only when the user asks for\n  developer product information, Platform account sign-in, support, privacy,\n  or legal information, but never as a route to purchase.\n- Do not share `sonilo.com` as an authentication or account-access destination\n  because its creator accounts are not accepted by this plugin.\n- Explicit generation requests may consume credits already present in the\n  authenticated user's Sonilo Platform account; this existing-credit usage is\n  not a purchase flow.\n\n## Report the result\n\n- On success, return only media URLs and metadata actually present in the task result. For video-to-video operations, identify the returned URL as a newly mixed video; never claim that Sonilo modified the source video in place.\n- On failure, report the provided error and refund status without claiming that media was created.\n- Never describe a processing task as finished or fabricate a playable artifact.\n- Keep account, usage, task, and media details scoped to the authenticated Sonilo Platform user.\n"
AFTER
"---\nname: sonilo-workflows\ndescription: Create licensed music, sound effects, mixed videos, translated subtitles, and dubbed videos with a Sonilo Platform account. Preserve speech, request variants or stems, keep names and terms intact with a glossary, and retrieve existing tasks. Validate public HTTPS media inputs before any tool call, and send a local file only through Sonilo's own upload tool; never direct users to pricing, checkout, subscriptions, or credit recharge.\n---\n\n# Sonilo Workflows\n\nUse the connected hosted MCP schemas and returned data as the source of truth.\nThis plugin does not install the local `sonilo-mcp` Python server. Do not assume\na tool or parameter exists because it appears in that repository.\n\nFor the bundled connection, use the `sonilo_platform` MCP server. If a legacy\nlocal `sonilo` server is also available, do not use it for this workflow or\nfall back to it after a hosted authentication error. Reconnect the hosted\nSonilo Platform connection instead. Registered directory connections may\nuse a different namespace; identify them by their hosted schemas, including\n`get_generation_task`, rather than assuming every Sonilo tool is equivalent.\n\n## Account identity and availability\n\n- A Sonilo Platform account is required. OAuth connects the user to\n  `platform.sonilo.com`. Accounts created only on `sonilo.com` belong to a\n  separate creator account system.\n- Never direct users to `sonilo.com` for plugin authentication. Never ask for\n  passwords, API keys, one-time codes, or MFA codes.\n- After validating any media inputs, call `get_account_services` before a new\n  generation to check service availability and trial allowance. Check both\n  the connected tools and `available_services`; describe an unavailable feature\n  honestly instead of silently substituting a different paid operation.\n  `analyze_video` uses the service key `video_analysis`, and\n  `generate_video_subtitles` uses the service key `proofread`; other\n  generation tools in the routing table use their tool name as the service key.\n- For account questions or a credit rejection, read\n  [account and links](references/account-and-links.md). `get_usage` reports\n  historical spending, not the remaining balance.\n\n## Validate remote media inputs\n\nBefore calling any Sonilo MCP tool for a media-input request, validate every\nuser-supplied video, audio, and subtitle URL.\n\n- Require a publicly reachable `https://` URL. Reject `http://`, `file://`,\n  localhost, loopback, link-local, private-network, and other non-public URLs.\n- For an invalid URL, explain the public-HTTPS requirement and ask for a valid\n  replacement. Do not call even a read-only Sonilo tool, browse or fetch the\n  unsafe URL, attempt to transform it, or start generation.\n- Do not claim that a URL is public merely because it uses HTTPS. The hosted\n  service remains responsible for DNS resolution, redirect validation, and\n  SSRF protections. A filename or local attachment is not a public URL; do not\n  upload a user's file to a third-party host to obtain one. The only supported\n  upload path is the one below.\n\n## Use a local file\n\nWhen the user asks to process a file on their own machine, use the hosted\n`create_upload_url` tool if it is among the connected tools and this\nenvironment can send the file's bytes in an HTTP PUT.\n\n1. Proceed only when the request clearly covers that file, and say that the\n   file will be uploaded to temporary storage on the user's Sonilo Platform\n   account. Do not upload files the user did not name.\n2. Call `create_upload_url` with the file's name and its exact size in bytes.\n   It is free and creates no task. It accepts video, audio, `.srt`, and `.vtt`\n   files up to `max_upload_size_mb` from `get_account_services`.\n3. Send the raw bytes to the returned `upload_url` with one HTTP PUT, for\n   example `curl -T <path> \"<upload_url>\"`, adding no authorization header.\n   A 403 means the size did not match or the URL expired: request a new URL\n   instead of retrying the old one.\n4. Once the PUT succeeds, pass the returned `file_url` wherever the chosen\n   tool takes a media or subtitle URL. A `file_url` from this tool is a valid\n   input; do not ask for a public URL in its place.\n\nTreat `upload_url` as a credential for that one upload: never show it to the\nuser, log it, or reuse it. Do not present `file_url` as a result or download\nlink; uploads are temporary working files. If the tool is not connected or\nthe PUT cannot be made here, do not try another upload route: explain that a\npublic `https://` URL is needed instead.\n\n## Choose the operation\n\nGeneration and processing tools run only when the user clearly asks to create\nor process media. They may consume existing account credits. Read-only account\nand task lookups do not, and neither does `create_upload_url`. Explain options without generating anything when the\nuser asks what Sonilo can do. Do not require redundant confirmation for an\nexplicit, sufficiently specified generation request.\n\n| Requested result | Hosted tool |\n| --- | --- |\n| Music from a description | `text_to_music` |\n| Sound effect from a description | `text_to_sfx` |\n| Music matched to a video, delivered as audio | `video_to_music` |\n| Sound effects matched to a video, delivered as audio | `video_to_sfx` |\n| A new video with generated music | `video_to_video_music` |\n| A new video with generated sound effects | `video_to_video_sfx` |\n| Music and sound effects together, delivered as audio | `video_to_sound` |\n| A new video with music and sound effects together | `video_to_video_sound` |\n| Lower existing music under a separate voice track | `audio_ducking` |\n| Editable translated subtitles before dubbing | `generate_video_subtitles` |\n| A dubbed video per requested language | `dubbing` |\n| A creative brief for a video | `analyze_video` (also potentially charged; `mode` picks the brief) |\n| Available services and account status | `get_account_services` |\n| Historical usage and spend | `get_usage` |\n| Progress or results of an existing task | `get_generation_task` |\n| Make a local video, audio, or subtitle file usable as an input | `create_upload_url` (free; see Use a local file) |\n\nUse video-producing tools for a new video with the generated audio mixed in;\ndo not substitute them for an audio-only request. Prefer a single combined\nmusic-and-effects tool over two separate generations for the same request.\nDo not add a paid analysis step just to choose a generation tool.\n\n## Creative controls\n\n- **Speech:** use `preserve_speech=true` on supported video-music or combined\n  tools to keep the source speech. Add `ducking=true` when music must lower\n  during speech. Use `keep_original_sound=true` instead when the user wants\n  all original audio retained. Do not pass options to tools lacking them.\n- **Variants:** use the requested `variants_num` in one supported tool call;\n  default to one. Multiple variants consume more credits and are not covered\n  by a single-run trial. A free-only request does not authorize paid variants.\n  Return a separately labeled link for each actual result, not repeated links\n  to the first result.\n- **Stems:** set `stems=true` on `text_to_music` or `video_to_music` only when\n  requested. These separate the generated music into drums, bass, vocals, and\n  other; they do not split an arbitrary source recording. If `stems_error`\n  appears, deliver the successful music and available stems, explain the\n  missing extras, and do not regenerate or claim all stems succeeded.\n- **Timed effects:** follow the selected tool's `segments` schema. Hosted\n  video-SFX tools currently expect a JSON-encoded string, starting at zero\n  with contiguous `{start, end, prompt}` intervals. Preserve requested event\n  times; represent gaps as intervals requesting no added effects. Do not send\n  isolated disjoint intervals or use the music-segment schema. Combined tools\n  have their own segment schema; inspect it before use.\n- **Analysis:** `analyze_video` writes a music brief, a sound-design brief,\n  or both (`mode` = `music`, `sfx`, or `both`, the default). Every mode\n  costs the same; ask for only the brief the user wants.\n- Preserve requested duration, language, and format; otherwise use tool\n  defaults. Ask only for missing information that affects the requested\n  result or charge, and do not invent parameters or prices.\n\nFor subtitle review, glossaries, input limits, dubbing, free previews, and\nreturning to finish a full video, read\n[dubbing and continuation](references/dubbing.md).\n\n## Run or retrieve a task\n\n1. Submit the chosen generation once. Retain its `task_id`, source URLs, and\n   requested parameters in the conversation so the same work can be retrieved.\n2. `status: processing` means started, not finished. Poll `get_generation_task`\n   with the same ID, waiting about 5–10 seconds between checks when available.\n3. After a timeout or interruption with a task ID, retrieve that task. Do not\n   submit a new generation. Without a task ID, report that submission status\n   is unknown; do not claim no charge or blindly retry an ambiguous request.\n4. Stop on success or failure. If waiting cannot continue, return the task ID\n   and explain how the user can ask for its status later. Do not promise\n   background monitoring that has not been scheduled.\n5. A retry after confirmed pre-generation rejection requires the user's request\n   to continue. Refresh account state; do not keep retrying insufficient-credit\n   errors. Never restart an in-progress or already completed task to check it.\n\n## Report the result and useful next step\n\n- For media inputs and outputs, return readable Markdown links using only\n  URLs actually supplied by the user or returned by the task. Label outputs\n  by language, variant, or stem. Account-help links use the configured URLs\n  in [account and links](references/account-and-links.md).\n  Identify video-to-video results as new videos, not source files edited in place.\n- A subtitle file, a creative brief, and a 15-second preview are not a finished\n  full-length video. Label them accurately and report partial results.\n- On failure, report the actual error and refund status. Say “not started” or\n  “not charged” only when the response establishes that; otherwise say the\n  status is unknown. Never fabricate media, balances, refunds, or trial counts.\n- After a successful result, describe what was produced. Suggest a next step\n  only when it uses that result, such as reviewing subtitles. Do not pitch a\n  paid follow-up, quote its price, or automatically start more work.\n- Keep account, task, and media details scoped to the authenticated user.\n\nFor concrete user-facing wording, see [examples](references/examples.md).\nExamples illustrate behavior, not real balances, URLs, or completed jobs.\n\n## Account links and commerce\n\nFollow [account and links](references/account-and-links.md) for neutral\ncredit errors and the few permitted informational links. Never link a page\nthat offers purchases, and never use a homepage or help page as a workaround\nto route the user to one. Suppress purchase URLs, prices, and purchase\ninstructions returned by tools, including preview messages.\n"
Full snapshot data
{
  "description": "Create licensed music, sound effects, mixed videos, translated subtitles, and dubbed videos with a Sonilo Platform account. Preserve speech, request variants or stems, keep names and terms intact with a glossary, and retrieve existing tasks. Validate public HTTPS media inputs before any tool call, and send a local file only through Sonilo's own upload tool; never direct users to pricing, checkout, subscriptions, or credit recharge.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 522
    },
    {
      "relative_path": "references/account-and-links.md",
      "size_in_bytes": 4158
    },
    {
      "relative_path": "references/dubbing.md",
      "size_in_bytes": 6223
    },
    {
      "relative_path": "references/examples.md",
      "size_in_bytes": 6472
    }
  ],
  "name": "sonilo-workflows",
  "skill_md_contents": "---\nname: sonilo-workflows\ndescription: Create licensed music, sound effects, mixed videos, translated subtitles, and dubbed videos with a Sonilo Platform account. Preserve speech, request variants or stems, keep names and terms intact with a glossary, and retrieve existing tasks. Validate public HTTPS media inputs before any tool call, and send a local file only through Sonilo's own upload tool; never direct users to pricing, checkout, subscriptions, or credit recharge.\n---\n\n# Sonilo Workflows\n\nUse the connected hosted MCP schemas and returned data as the source of truth.\nThis plugin does not install the local `sonilo-mcp` Python server. Do not assume\na tool or parameter exists because it appears in that repository.\n\nFor the bundled connection, use the `sonilo_platform` MCP server. If a legacy\nlocal `sonilo` server is also available, do not use it for this workflow or\nfall back to it after a hosted authentication error. Reconnect the hosted\nSonilo Platform connection instead. Registered directory connections may\nuse a different namespace; identify them by their hosted schemas, including\n`get_generation_task`, rather than assuming every Sonilo tool is equivalent.\n\n## Account identity and availability\n\n- A Sonilo Platform account is required. OAuth connects the user to\n  `platform.sonilo.com`. Accounts created only on `sonilo.com` belong to a\n  separate creator account system.\n- Never direct users to `sonilo.com` for plugin authentication. Never ask for\n  passwords, API keys, one-time codes, or MFA codes.\n- After validating any media inputs, call `get_account_services` before a new\n  generation to check service availability and trial allowance. Check both\n  the connected tools and `available_services`; describe an unavailable feature\n  honestly instead of silently substituting a different paid operation.\n  `analyze_video` uses the service key `video_analysis`, and\n  `generate_video_subtitles` uses the service key `proofread`; other\n  generation tools in the routing table use their tool name as the service key.\n- For account questions or a credit rejection, read\n  [account and links](references/account-and-links.md). `get_usage` reports\n  historical spending, not the remaining balance.\n\n## Validate remote media inputs\n\nBefore calling any Sonilo MCP tool for a media-input request, validate every\nuser-supplied video, audio, and subtitle URL.\n\n- Require a publicly reachable `https://` URL. Reject `http://`, `file://`,\n  localhost, loopback, link-local, private-network, and other non-public URLs.\n- For an invalid URL, explain the public-HTTPS requirement and ask for a valid\n  replacement. Do not call even a read-only Sonilo tool, browse or fetch the\n  unsafe URL, attempt to transform it, or start generation.\n- Do not claim that a URL is public merely because it uses HTTPS. The hosted\n  service remains responsible for DNS resolution, redirect validation, and\n  SSRF protections. A filename or local attachment is not a public URL; do not\n  upload a user's file to a third-party host to obtain one. The only supported\n  upload path is the one below.\n\n## Use a local file\n\nWhen the user asks to process a file on their own machine, use the hosted\n`create_upload_url` tool if it is among the connected tools and this\nenvironment can send the file's bytes in an HTTP PUT.\n\n1. Proceed only when the request clearly covers that file, and say that the\n   file will be uploaded to temporary storage on the user's Sonilo Platform\n   account. Do not upload files the user did not name.\n2. Call `create_upload_url` with the file's name and its exact size in bytes.\n   It is free and creates no task. It accepts video, audio, `.srt`, and `.vtt`\n   files up to `max_upload_size_mb` from `get_account_services`.\n3. Send the raw bytes to the returned `upload_url` with one HTTP PUT, for\n   example `curl -T <path> \"<upload_url>\"`, adding no authorization header.\n   A 403 means the size did not match or the URL expired: request a new URL\n   instead of retrying the old one.\n4. Once the PUT succeeds, pass the returned `file_url` wherever the chosen\n   tool takes a media or subtitle URL. A `file_url` from this tool is a valid\n   input; do not ask for a public URL in its place.\n\nTreat `upload_url` as a credential for that one upload: never show it to the\nuser, log it, or reuse it. Do not present `file_url` as a result or download\nlink; uploads are temporary working files. If the tool is not connected or\nthe PUT cannot be made here, do not try another upload route: explain that a\npublic `https://` URL is needed instead.\n\n## Choose the operation\n\nGeneration and processing tools run only when the user clearly asks to create\nor process media. They may consume existing account credits. Read-only account\nand task lookups do not, and neither does `create_upload_url`. Explain options without generating anything when the\nuser asks what Sonilo can do. Do not require redundant confirmation for an\nexplicit, sufficiently specified generation request.\n\n| Requested result | Hosted tool |\n| --- | --- |\n| Music from a description | `text_to_music` |\n| Sound effect from a description | `text_to_sfx` |\n| Music matched to a video, delivered as audio | `video_to_music` |\n| Sound effects matched to a video, delivered as audio | `video_to_sfx` |\n| A new video with generated music | `video_to_video_music` |\n| A new video with generated sound effects | `video_to_video_sfx` |\n| Music and sound effects together, delivered as audio | `video_to_sound` |\n| A new video with music and sound effects together | `video_to_video_sound` |\n| Lower existing music under a separate voice track | `audio_ducking` |\n| Editable translated subtitles before dubbing | `generate_video_subtitles` |\n| A dubbed video per requested language | `dubbing` |\n| A creative brief for a video | `analyze_video` (also potentially charged; `mode` picks the brief) |\n| Available services and account status | `get_account_services` |\n| Historical usage and spend | `get_usage` |\n| Progress or results of an existing task | `get_generation_task` |\n| Make a local video, audio, or subtitle file usable as an input | `create_upload_url` (free; see Use a local file) |\n\nUse video-producing tools for a new video with the generated audio mixed in;\ndo not substitute them for an audio-only request. Prefer a single combined\nmusic-and-effects tool over two separate generations for the same request.\nDo not add a paid analysis step just to choose a generation tool.\n\n## Creative controls\n\n- **Speech:** use `preserve_speech=true` on supported video-music or combined\n  tools to keep the source speech. Add `ducking=true` when music must lower\n  during speech. Use `keep_original_sound=true` instead when the user wants\n  all original audio retained. Do not pass options to tools lacking them.\n- **Variants:** use the requested `variants_num` in one supported tool call;\n  default to one. Multiple variants consume more credits and are not covered\n  by a single-run trial. A free-only request does not authorize paid variants.\n  Return a separately labeled link for each actual result, not repeated links\n  to the first result.\n- **Stems:** set `stems=true` on `text_to_music` or `video_to_music` only when\n  requested. These separate the generated music into drums, bass, vocals, and\n  other; they do not split an arbitrary source recording. If `stems_error`\n  appears, deliver the successful music and available stems, explain the\n  missing extras, and do not regenerate or claim all stems succeeded.\n- **Timed effects:** follow the selected tool's `segments` schema. Hosted\n  video-SFX tools currently expect a JSON-encoded string, starting at zero\n  with contiguous `{start, end, prompt}` intervals. Preserve requested event\n  times; represent gaps as intervals requesting no added effects. Do not send\n  isolated disjoint intervals or use the music-segment schema. Combined tools\n  have their own segment schema; inspect it before use.\n- **Analysis:** `analyze_video` writes a music brief, a sound-design brief,\n  or both (`mode` = `music`, `sfx`, or `both`, the default). Every mode\n  costs the same; ask for only the brief the user wants.\n- Preserve requested duration, language, and format; otherwise use tool\n  defaults. Ask only for missing information that affects the requested\n  result or charge, and do not invent parameters or prices.\n\nFor subtitle review, glossaries, input limits, dubbing, free previews, and\nreturning to finish a full video, read\n[dubbing and continuation](references/dubbing.md).\n\n## Run or retrieve a task\n\n1. Submit the chosen generation once. Retain its `task_id`, source URLs, and\n   requested parameters in the conversation so the same work can be retrieved.\n2. `status: processing` means started, not finished. Poll `get_generation_task`\n   with the same ID, waiting about 5–10 seconds between checks when available.\n3. After a timeout or interruption with a task ID, retrieve that task. Do not\n   submit a new generation. Without a task ID, report that submission status\n   is unknown; do not claim no charge or blindly retry an ambiguous request.\n4. Stop on success or failure. If waiting cannot continue, return the task ID\n   and explain how the user can ask for its status later. Do not promise\n   background monitoring that has not been scheduled.\n5. A retry after confirmed pre-generation rejection requires the user's request\n   to continue. Refresh account state; do not keep retrying insufficient-credit\n   errors. Never restart an in-progress or already completed task to check it.\n\n## Report the result and useful next step\n\n- For media inputs and outputs, return readable Markdown links using only\n  URLs actually supplied by the user or returned by the task. Label outputs\n  by language, variant, or stem. Account-help links use the configured URLs\n  in [account and links](references/account-and-links.md).\n  Identify video-to-video results as new videos, not source files edited in place.\n- A subtitle file, a creative brief, and a 15-second preview are not a finished\n  full-length video. Label them accurately and report partial results.\n- On failure, report the actual error and refund status. Say “not started” or\n  “not charged” only when the response establishes that; otherwise say the\n  status is unknown. Never fabricate media, balances, refunds, or trial counts.\n- After a successful result, describe what was produced. Suggest a next step\n  only when it uses that result, such as reviewing subtitles. Do not pitch a\n  paid follow-up, quote its price, or automatically start more work.\n- Keep account, task, and media details scoped to the authenticated user.\n\nFor concrete user-facing wording, see [examples](references/examples.md).\nExamples illustrate behavior, not real balances, URLs, or completed jobs.\n\n## Account links and commerce\n\nFollow [account and links](references/account-and-links.md) for neutral\ncredit errors and the few permitted informational links. Never link a page\nthat offers purchases, and never use a homepage or help page as a workaround\nto route the user to one. Suppress purchase URLs, prices, and purchase\ninstructions returned by tools, including preview messages.\n"
}

SHA-256 of public snapshot: 590e7d9043acc325d716900fc331774db684b36c30344fa72065aa636556093f