@fotor-ai/dsh-fotor-plugin 0.6.1 → 0.8.0

package/skills/fotor-connect/references/mcp-integration.md

@@ -21,7 +21,7 @@ Use the runtime routing, authentication, and website flow below. Keep credential
 | Connect to Fotor, connect to the Fotor website, or connect and open Fotor | Authenticate MCP, then follow the website flow below |
 | Connect to Fotor MCP or check MCP connectivity without a website request; explicitly keep the website closed | Perform the requested MCP check; omit the website handoff |
 | Introduce features or query models | Answer from current tool descriptions or model queries; omit website navigation unless also requested |
-| Credit-account questions or reported limits | Follow the [credits workflow](credits.md); ordinary connection does not query balance |
+| The user asks for their own Fotor credit balance | Follow the [credits workflow](credits.md); ordinary connection does not query balance |
 
 Equivalent wording in other languages follows the same routing. Uploads, image processing, and media generation alone do not request website access. Ordinary website connection requests authorize the final visible navigation; they do not authorize media submissions.
 
@@ -67,7 +67,7 @@ This budget covers automatic MCP connection recovery, not website navigation, cr
 
 ### Connect to the website
 
-1. Complete MCP authentication and authenticated tool discovery, using [bounded connection recovery](#bounded-connection-recovery) for eligible failures. When available, require a successful `list_models` read-only check without dumping its catalog before requesting a website link. Determine browser availability before creating the short-lived link, following the browser route in the packaged [authentication guidance](authentication.md). Otherwise prepare the manual fallback. Only a successful discovery that omits `get_website_url` establishes a missing website capability; an unavailable chat tool surface or failed discovery does not establish the service version. Report MCP and website outcomes separately, without substituting a top-up link or claiming ordinary page access as automatic login.
+1. Complete MCP authentication and authenticated tool discovery, using [bounded connection recovery](#bounded-connection-recovery) for eligible failures. When available, require a successful `list_models` read-only check without dumping its catalog before requesting a website link. Determine browser availability before creating the short-lived link, following the browser route in the packaged [authentication guidance](authentication.md). Otherwise prepare the manual fallback. Only a successful discovery that omits `get_website_url` establishes a missing website capability; an unavailable chat tool surface or failed discovery does not establish the service version. Report MCP and website outcomes separately, without claiming an ordinary page visit established automatic login.
 2. Call `get_website_url` without arguments. Its public response contains `handoff_url` and integer `expires_in` from 0 to 600; it does not expose `target_url`. Require a usable link and remaining lifetime greater than zero. A zero lifetime is already expired: use the bounded replacement rule below. Missing, malformed, or out-of-range fields are a handoff failure. The server configures and validates the destination; before navigation, the plugin can check only the handoff endpoint against the [connection table](#connection), not the hidden target. Never decode the ticket, rewrite its URL, or change environments to recover a mismatch.
 3. Follow [one-time browser links](#one-time-browser-links) for the returned `handoff_url`, using the actual remaining lifetime. This final visible navigation is the requested website visit and consumes the ticket.
 4. Inspect the resulting page in that same browser session. Compare its HTTPS origin with the selected website in the connection table and verify authenticated state before reporting the website connected. A valid handoff endpoint alone does not prove the hidden redirect target is correct. On a different environment or unexpected origin, stop further interaction and report the mismatch; do not follow it as a fallback. A link, a generic page, or a login/error screen is insufficient. If state is unclear, ask the user to confirm it. Website failure does not justify resetting working MCP credentials.
@@ -75,7 +75,7 @@ This budget covers automatic MCP connection recovery, not website navigation, cr
 
 ### One-time browser links
 
-Apply this section only to `get_website_url.handoff_url`. This plugin's selected website connection flow uses one final visible navigation in the browser specified by the packaged [authentication guidance](authentication.md). The service description instead prescribes a user-clicked link to prevent early consumption; the plugin's selected browser action is the intended final visit, never a pre-opening check. Honor an explicit user preference for manual delivery and any host restriction; use the manual fallback when direct navigation is unavailable. Handle other returned account links only under the packaged [credit-link policy](credits.md#validate-and-deliver-pricing-links).
+Apply this section only to `get_website_url.handoff_url`. This plugin's selected website connection flow uses one final visible navigation in the browser specified by the packaged [authentication guidance](authentication.md). The service description instead prescribes a user-clicked link to prevent early consumption; the plugin's selected browser action is the intended final visit, never a pre-opening check. Honor an explicit user preference for manual delivery and any host restriction; use the manual fallback when direct navigation is unavailable.
 
 - Parse the returned URL before use. It must have the exact HTTPS origin and path of the selected environment's [login handoff endpoint](#connection), no username/password or fragment, and one nonempty `code` query parameter only. Check URL components rather than hostname substrings. Reject an unknown environment or mismatch without fetching the address, rewriting the host, or switching services.
 - Immediately navigate once in the selected visible host browser. Do not first fetch, preview, probe, or open the ticket in a hidden tab. After navigation, treat it as consumed and never offer it as a reusable login link.
@@ -97,13 +97,20 @@ Inspect the connected service's actual tool descriptions and input schemas. The
 | `submit_first_frame_video_task` | Animate `image_url` as the first frame; a successful call may consume Fotor credits |
 | `submit_first_last_frame_video_task` | Use ordered `start_image_url` and `end_image_url`; a successful call may consume Fotor credits |
 | `submit_multimodal_video_task` | Use supported image, video, and/or audio references; a successful call may consume Fotor credits |
-| `get_task` | Query an existing image-processing, image-generation, or video task by `task_id` |
+| `submit_soundtrack_task` | Compose a separate MP3 from exactly one source image or video |
+| `submit_audio_track_task` | Generate a new track from reference audio |
+| `submit_song_edit_task` | Extend, remix or edit a section of a song |
+| `submit_speech_task` | Generate speech or a scripted podcast with built-in voices |
+| `submit_audio_separation_task` | Separate existing vocals and accompaniment into a ZIP |
+| `get_task` | Look up one known image, video or audio task using existing credentials |
 | `get_website_url` | Obtain an environment-bound, one-time website login link for the verified MCP user |
-| `get_credits` | Query available balance; apply the packaged [credits workflow](credits.md) to any other returned fields |
+| `get_credits` | Query only the authenticated user's own balance; follow the [balance lookup](credits.md#query-the-selected-account) |
 
 For model-based generation/editing, start with `list_models`, optionally filtering by `media_type` and `mode`. Uploads and fixed image-processing operations use their own tool contracts without model selection. Filters combine with AND; an empty filtered result is not evidence of a failed connection. Then query `list_models` with the chosen `model_id` before submitting. Model IDs, available modes, and catalog sizes can change; an unknown or retired ID requires a new selection, not an invented replacement.
 
-Use the returned resolutions, aspect ratios, qualities, duration values/ranges, reference types, and defaults. Honor an explicit model or output preference; explain an unsupported constraint before changing it. When no preference is given, choose a suitable supported model and use its reported defaults. `duration=0` selects `default_duration`; duration ranges are inclusive integer seconds, while a list permits only its listed values. `explicit_aspect_ratio_modes` requires a concrete supported ratio instead of `auto`; for multimodal references this condition applies when images are supplied without videos.
+For standalone audio, read the selected model’s `operations[]`. Use its tool, selector, required parameters, result format and synchronous behavior. Only soundtrack creation accepts a model ID.
+
+For images and videos, use the returned resolutions, aspect ratios, qualities, duration values/ranges, reference types, and defaults. Honor an explicit model or output preference; explain an unsupported constraint before changing it. When no preference is given, choose a suitable supported model and use its reported defaults. `duration=0` selects `default_duration`; duration ranges are inclusive integer seconds, while a list permits only its listed values. `explicit_aspect_ratio_modes` requires a concrete supported ratio instead of `auto`; for multimodal references this condition applies when images are supplied without videos.
 
 ### Inputs and native capabilities
 
@@ -113,7 +120,7 @@ Use native model resolutions and supported output options for generation. Explic
 
 ### Credit consumption before submission
 
-Every discovered tool whose name matches `submit_*_task` may consume Fotor credits when its call succeeds. This applies to all image and video submissions, including future tools matching that name pattern; discovery and the actual schema still determine whether a tool can be called.
+Every discovered tool whose name matches `submit_*_task` may consume Fotor credits when its call succeeds. This applies to all image, video and audio submissions, including future tools matching that name pattern; discovery and the actual schema still determine whether a tool can be called.
 
 Before submitting, briefly tell the user in their conversation language that the successful call may consume Fotor credits. Continue under an already explicit task request without adding a blanket confirmation step. Preserve the user's budget, requested scope, and host approval requirements. For an explicitly requested sequence, one notice before the first submission may cover every named step; disclose newly added steps or scope changes before submitting them.
 
@@ -121,14 +128,13 @@ Do not apply this notice to model discovery, balance queries, uploads or task po
 
 ### Submission, recovery, and results
 
-For an explicit `insufficient_credits` submission error, follow [insufficient credits during media submission](credits.md#insufficient-credits-during-media-submission). This applies to image generation, fixed image processing, and every video submission mode; it does not make balance queries a prerequisite.
+For an explicit `insufficient_credits` submission error, follow [insufficient credits during media submission](credits.md#insufficient-credits-during-media-submission). This applies to image generation, fixed image processing, and every video and audio submission mode; it does not make balance queries a prerequisite.
 
-1. Submit the requested operation once and retain its returned `task_id`, environment, and selected model or fixed `operation`. A submitted task is not a completed artifact.
-2. Query that task with `get_task`. Each call performs one lookup; the client may repeat queries at reasonable intervals within the active task's execution budget. The tool does not start background polling.
-3. Respect `is_terminal` and the actual status. `processing` does not distinguish queued, running, or upstream-unavailable tasks. Report `unknown` as uncertain. Stop polling when `is_terminal` is true and report the terminal outcome, including failure, timeout, cancellation, or completion. If state fields conflict, report the inconsistency rather than inventing progress.
-4. On completion, deliver the actual `result_url` when present. If it is missing, report completion without an available artifact link. Result URLs may expire. Prefer a host-supported media preview and describe quality only after inspecting the result.
-5. An explicit `submission_uncertain` error or a lost submission response can mean a task was created and charged. Use a known task ID for recovery. Without one, report the uncertain submission and stop; do not automatically resubmit or assume an unprovided idempotency mechanism. On a query error or polling limit, preserve the same ID and report the last observed state.
+1. Submit once. Retain the returned task ID, environment, selected operation and expected output format. Image and video calls normally return an accepted task. Audio may already have completed. Inspect both the MCP error flag and the structured content, including on `isError=true`. Retain any known task ID, safe `failure_reason` and reported credit value.
+2. On completion, deliver the actual `result_url` immediately without polling. Prefer a host-supported preview for playable media. Offer an audio separation ZIP as a download. If the URL is absent, report completion without an available link. Describe quality only after inspecting the artifact.
+3. For an accepted or processing task, query the same ID with `get_task`. Each call performs one lookup. Within the task budget, wait between checks. The query can omit the model and result format, so retain the originating operation. Stop on completion, `failed`, `timed_out` or `cancelled`. Report unknown or conflicting state as uncertain. A safe failure summary may be generic.
+4. A transport timeout, lost response or `submission_uncertain` may follow an accepted, chargeable submission. Recover only by looking up a known ID. Without an ID, report the uncertain outcome and stop. Never automatically resubmit. On a lookup error or polling limit, preserve the ID and last observed state.
 
 `credits_increment` reports the increment returned by that particular submission or query, not a balance or a price quote. Preserve `0` as zero and `null` as unknown. Do not add submission and polling values together as if each observation were a new charge. Report missing or inconsistent values without estimating usage.
 
-Task lookup is scoped to the selected API key's Business. Another Business cannot retrieve its results, and a task ID must not be moved between environments to recover a failure. Key lookup can register a developer or create a missing key, so `get_task` is not a side-effect-free connection probe. Use `list_models` for read-only checks; it reads the model catalog without developer lookup, key creation, or generation requests.
+Task lookup is scoped to the selected API key's Business. Another Business cannot retrieve its results, and a task ID must not be moved between environments to recover a failure. Task lookup uses existing credentials. If none are usable, report `credentials_unavailable`. It creates no developer, key or task and consumes no credits. Use `list_models` for connection checks.

package/skills/fotor-connect/references/media-upload.md

@@ -1,6 +1,6 @@
 # Fotor Media Upload
 
-Read this workflow for standalone uploads and when an image or video task needs local references. Use already accessible HTTPS references directly for creation; upload only the specific local files or client-accessible attachments needed by the user's request. An attachment label without readable bytes is not an uploadable file.
+Read this workflow for standalone uploads and when an image, video or audio task needs local references. Use already accessible HTTPS references directly for creation; upload only the specific local files or client-accessible attachments needed by the user's request. An attachment label without readable bytes is not an uploadable file.
 
 ## Prepare the input
 
@@ -29,6 +29,6 @@ If the file changes after signing, recalculate its metadata and request a new li
 
 Process multiple files one at a time, preserving input order and the association between each file and its successful URL. Report name, media type, exact byte size, and `file_url` for successes; report a concise reason for each failure without exposing signatures. A partial batch is not an all-success result. If a creation task needs a failed input, resolve it before submission rather than silently omitting it.
 
-For standalone uploads, deliver those results and finish. For requested creation, use the uploaded URLs in the appropriate reference fields or image-processing `image_url`, keeping the same environment. File acceptance by storage does not establish model compatibility or media-task success.
+For standalone uploads, deliver those results and finish. For requested creation, use the uploaded URLs in the appropriate reference fields or the selected audio operation’s source URL or image-processing `image_url`, keeping the same environment. File acceptance by storage does not establish model compatibility or media-task success.
 
 `expires_in` describes the maximum upload-address lifetime; temporary signing credentials may expire earlier. It does not describe file retention. Signature expiry does not delete an uploaded file, and `file_url` is not a presigned download URL. Do not promise permanent storage, a deletion time, or long-term URL availability unless the service provides that information.

package/skills/fotor-credits/SKILL.md

@@ -1,12 +1,8 @@
 ---
 name: fotor-credits
-description: Check available Fotor credits and provide its pricing-page link. Use for Fotor balance and recharge requests; signed-in website access belongs to fotor-connect and media tasks use their own skills.
+description: Query the authenticated user's own Fotor credit balance. Use when the user asks how many Fotor credits they have.
 ---
 
-# Fotor Credits
+# Check my Fotor credits
 
-Follow the shared [credits and top-up workflow](references/credits.md) for authentication, balance reporting, low-balance or explicit recharge requests, pricing-link validation, and errors.
-
-Report the actual balance and deliver a pricing link only when selected by that workflow. Let the user click it; a pricing link does not sign them in. A credits request alone does not open a browser or request a website-login link. Respect explicit balance-only, no-link, and no-browser restrictions.
-
-Keep payment under the user's control. Neither a returned link nor an opened page establishes that a purchase or recharge completed.
+Use this skill only for the signed-in user's own balance. For other requests, explain its scope without calling a tool. Follow the [balance lookup](references/credits.md#query-the-selected-account) and report the number returned, including zero, or explain why the balance is unavailable.

package/skills/fotor-credits/references/credits.md

@@ -1,36 +1,11 @@
-# Fotor Credits and Top-up
-
-Read this workflow for a balance question or an explicit recharge request. Media submission and ordinary website connection do not require a preliminary balance query.
+# Fotor credit balance
 
 ## Query the selected account
 
-1. Follow [MCP authentication](mcp-integration.md#authenticate-mcp) for the installed environment, reusing valid credentials or completing required external-browser OAuth. Discover `get_credits`; if absent, report the unavailable capability without changing environments.
-2. Call `get_credits` without arguments. It returns nonnegative numeric `credits` and a regular pricing-page `top_up_url`. This URL reuses an existing browser session but does not sign the user in. It is not a one-time ticket and has no `expires_in` field.
-3. Report the actual balance. `credits_increment` in a task response is that task's consumption, not this balance; do not infer available funds from it. A balance observation is not a generation price quote or a guarantee that a later submission can proceed.
-4. Treat `credits_unavailable`, authentication errors, invalid/missing balance values, and other failures as unavailable information, never as zero. Do not create accounts, keys, replacement tasks, or credentials to work around a balance error. If a successful response has a valid balance but an unusable pricing link, report the balance and, when a link is selected below, the separate link problem.
-
-## Select the response
-
-| Request and result | Action |
-| --- | --- |
-| Balance below 100, or an explicit request to top up | Report the balance and deliver the validated pricing link as described below. Let the user click it. |
-| Balance of 100 or more; no top-up request | Report only the balance. Keep the returned link out of the response. |
-| Explicit balance-only or no-link instruction | Report only the balance, including when it is below 100. |
-| Browser navigation is forbidden or unavailable | Deliver the selected link if the user permits links; link delivery needs no browser automation. |
-| Query failed | Report the failure; do not infer a low balance or invent a pricing link. |
-
-## Validate and deliver pricing links
-
-Use this rule for both `get_credits.top_up_url` and a submission error's `top_up_url`:
-
-1. Require a nonempty absolute HTTPS URL whose origin exactly matches the selected environment's website in the [connection table](mcp-integration.md#connection), with no embedded username/password. Check URL components rather than hostname substrings. Reject an unknown environment, malformed URL, or origin mismatch without visiting it, changing environments, or rewriting its host.
-2. Use the exact returned URL as the Markdown target, with a label meaning "View Fotor plans" in the conversation language. Preserve its path, query, and fragment; the login handoff endpoint, `code` parameter, expiry, and single-consumption rules do not apply to ordinary pricing links. If the link is missing or invalid, explain that the pricing entry is unavailable instead of constructing a replacement.
-3. Let the user click the link. A balance or recharge request alone does not call `get_website_url`, open a browser, or refresh a supposed ticket. If the user also explicitly requests a signed-in website session, complete the [website connection flow](mcp-integration.md#connect-to-the-website) separately, then provide the pricing link for them to open in that same browser.
-
-Leave plan selection and payment to the user. A link or a loaded page does not establish website login, a completed payment, or an increased balance. Keep credentials and website-login tickets out of files and diagnostic logs.
+1. When the user requests their own balance, follow [MCP authentication](mcp-integration.md#authenticate-mcp). Reuse valid authorization and discover `get_credits`. If it is unavailable, report that and stop.
+2. Call `get_credits` without arguments. The authenticated session identifies the account. Report only the nonnegative numeric `credits` value, including zero, and finish. A balance query needs no website visit.
+3. If authentication fails, the service reports an error, or the balance is missing or invalid, report it as unavailable. An unknown balance is not zero. Never infer a balance from task consumption.
 
 ## Insufficient credits during media submission
 
-When an image-generation, image-processing, or video submission explicitly returns `insufficient_credits`, report that error. If its `top_up_url` is non-null and valid, deliver it using the pricing-link rules above unless the user prohibited links. Missing or invalid links do not change the error into a balance value; no extra balance query is required.
-
-Stop dependent operations and retain any task ID returned. Do not automatically resubmit, infer that payment completed, or turn the error into `submission_uncertain`. A lost response or an explicit uncertain-submission result still follows the [task recovery workflow](mcp-integration.md#submission-recovery-and-results).
+When a submission explicitly reports `insufficient_credits`, explain that the task could not proceed for that reason. Retain any known task ID and reported consumption, stop dependent operations, and finish without extra links, a balance query or another submission. A lost response is a different outcome; follow [task recovery](mcp-integration.md#submission-recovery-and-results).

package/skills/fotor-credits/references/mcp-integration.md

@@ -21,7 +21,7 @@ Use the runtime routing, authentication, and website flow below. Keep credential
 | Connect to Fotor, connect to the Fotor website, or connect and open Fotor | Authenticate MCP, then follow the website flow below |
 | Connect to Fotor MCP or check MCP connectivity without a website request; explicitly keep the website closed | Perform the requested MCP check; omit the website handoff |
 | Introduce features or query models | Answer from current tool descriptions or model queries; omit website navigation unless also requested |
-| Credit-account questions or reported limits | Follow the [credits workflow](credits.md); ordinary connection does not query balance |
+| The user asks for their own Fotor credit balance | Follow the [credits workflow](credits.md); ordinary connection does not query balance |
 
 Equivalent wording in other languages follows the same routing. Uploads, image processing, and media generation alone do not request website access. Ordinary website connection requests authorize the final visible navigation; they do not authorize media submissions.
 
@@ -67,7 +67,7 @@ This budget covers automatic MCP connection recovery, not website navigation, cr
 
 ### Connect to the website
 
-1. Complete MCP authentication and authenticated tool discovery, using [bounded connection recovery](#bounded-connection-recovery) for eligible failures. When available, require a successful `list_models` read-only check without dumping its catalog before requesting a website link. Determine browser availability before creating the short-lived link, following the browser route in the packaged [authentication guidance](authentication.md). Otherwise prepare the manual fallback. Only a successful discovery that omits `get_website_url` establishes a missing website capability; an unavailable chat tool surface or failed discovery does not establish the service version. Report MCP and website outcomes separately, without substituting a top-up link or claiming ordinary page access as automatic login.
+1. Complete MCP authentication and authenticated tool discovery, using [bounded connection recovery](#bounded-connection-recovery) for eligible failures. When available, require a successful `list_models` read-only check without dumping its catalog before requesting a website link. Determine browser availability before creating the short-lived link, following the browser route in the packaged [authentication guidance](authentication.md). Otherwise prepare the manual fallback. Only a successful discovery that omits `get_website_url` establishes a missing website capability; an unavailable chat tool surface or failed discovery does not establish the service version. Report MCP and website outcomes separately, without claiming an ordinary page visit established automatic login.
 2. Call `get_website_url` without arguments. Its public response contains `handoff_url` and integer `expires_in` from 0 to 600; it does not expose `target_url`. Require a usable link and remaining lifetime greater than zero. A zero lifetime is already expired: use the bounded replacement rule below. Missing, malformed, or out-of-range fields are a handoff failure. The server configures and validates the destination; before navigation, the plugin can check only the handoff endpoint against the [connection table](#connection), not the hidden target. Never decode the ticket, rewrite its URL, or change environments to recover a mismatch.
 3. Follow [one-time browser links](#one-time-browser-links) for the returned `handoff_url`, using the actual remaining lifetime. This final visible navigation is the requested website visit and consumes the ticket.
 4. Inspect the resulting page in that same browser session. Compare its HTTPS origin with the selected website in the connection table and verify authenticated state before reporting the website connected. A valid handoff endpoint alone does not prove the hidden redirect target is correct. On a different environment or unexpected origin, stop further interaction and report the mismatch; do not follow it as a fallback. A link, a generic page, or a login/error screen is insufficient. If state is unclear, ask the user to confirm it. Website failure does not justify resetting working MCP credentials.
@@ -75,7 +75,7 @@ This budget covers automatic MCP connection recovery, not website navigation, cr
 
 ### One-time browser links
 
-Apply this section only to `get_website_url.handoff_url`. This plugin's selected website connection flow uses one final visible navigation in the browser specified by the packaged [authentication guidance](authentication.md). The service description instead prescribes a user-clicked link to prevent early consumption; the plugin's selected browser action is the intended final visit, never a pre-opening check. Honor an explicit user preference for manual delivery and any host restriction; use the manual fallback when direct navigation is unavailable. Handle other returned account links only under the packaged [credit-link policy](credits.md#validate-and-deliver-pricing-links).
+Apply this section only to `get_website_url.handoff_url`. This plugin's selected website connection flow uses one final visible navigation in the browser specified by the packaged [authentication guidance](authentication.md). The service description instead prescribes a user-clicked link to prevent early consumption; the plugin's selected browser action is the intended final visit, never a pre-opening check. Honor an explicit user preference for manual delivery and any host restriction; use the manual fallback when direct navigation is unavailable.
 
 - Parse the returned URL before use. It must have the exact HTTPS origin and path of the selected environment's [login handoff endpoint](#connection), no username/password or fragment, and one nonempty `code` query parameter only. Check URL components rather than hostname substrings. Reject an unknown environment or mismatch without fetching the address, rewriting the host, or switching services.
 - Immediately navigate once in the selected visible host browser. Do not first fetch, preview, probe, or open the ticket in a hidden tab. After navigation, treat it as consumed and never offer it as a reusable login link.
@@ -97,13 +97,20 @@ Inspect the connected service's actual tool descriptions and input schemas. The
 | `submit_first_frame_video_task` | Animate `image_url` as the first frame; a successful call may consume Fotor credits |
 | `submit_first_last_frame_video_task` | Use ordered `start_image_url` and `end_image_url`; a successful call may consume Fotor credits |
 | `submit_multimodal_video_task` | Use supported image, video, and/or audio references; a successful call may consume Fotor credits |
-| `get_task` | Query an existing image-processing, image-generation, or video task by `task_id` |
+| `submit_soundtrack_task` | Compose a separate MP3 from exactly one source image or video |
+| `submit_audio_track_task` | Generate a new track from reference audio |
+| `submit_song_edit_task` | Extend, remix or edit a section of a song |
+| `submit_speech_task` | Generate speech or a scripted podcast with built-in voices |
+| `submit_audio_separation_task` | Separate existing vocals and accompaniment into a ZIP |
+| `get_task` | Look up one known image, video or audio task using existing credentials |
 | `get_website_url` | Obtain an environment-bound, one-time website login link for the verified MCP user |
-| `get_credits` | Query available balance; apply the packaged [credits workflow](credits.md) to any other returned fields |
+| `get_credits` | Query only the authenticated user's own balance; follow the [balance lookup](credits.md#query-the-selected-account) |
 
 For model-based generation/editing, start with `list_models`, optionally filtering by `media_type` and `mode`. Uploads and fixed image-processing operations use their own tool contracts without model selection. Filters combine with AND; an empty filtered result is not evidence of a failed connection. Then query `list_models` with the chosen `model_id` before submitting. Model IDs, available modes, and catalog sizes can change; an unknown or retired ID requires a new selection, not an invented replacement.
 
-Use the returned resolutions, aspect ratios, qualities, duration values/ranges, reference types, and defaults. Honor an explicit model or output preference; explain an unsupported constraint before changing it. When no preference is given, choose a suitable supported model and use its reported defaults. `duration=0` selects `default_duration`; duration ranges are inclusive integer seconds, while a list permits only its listed values. `explicit_aspect_ratio_modes` requires a concrete supported ratio instead of `auto`; for multimodal references this condition applies when images are supplied without videos.
+For standalone audio, read the selected model’s `operations[]`. Use its tool, selector, required parameters, result format and synchronous behavior. Only soundtrack creation accepts a model ID.
+
+For images and videos, use the returned resolutions, aspect ratios, qualities, duration values/ranges, reference types, and defaults. Honor an explicit model or output preference; explain an unsupported constraint before changing it. When no preference is given, choose a suitable supported model and use its reported defaults. `duration=0` selects `default_duration`; duration ranges are inclusive integer seconds, while a list permits only its listed values. `explicit_aspect_ratio_modes` requires a concrete supported ratio instead of `auto`; for multimodal references this condition applies when images are supplied without videos.
 
 ### Inputs and native capabilities
 
@@ -113,7 +120,7 @@ Use native model resolutions and supported output options for generation. Explic
 
 ### Credit consumption before submission
 
-Every discovered tool whose name matches `submit_*_task` may consume Fotor credits when its call succeeds. This applies to all image and video submissions, including future tools matching that name pattern; discovery and the actual schema still determine whether a tool can be called.
+Every discovered tool whose name matches `submit_*_task` may consume Fotor credits when its call succeeds. This applies to all image, video and audio submissions, including future tools matching that name pattern; discovery and the actual schema still determine whether a tool can be called.
 
 Before submitting, briefly tell the user in their conversation language that the successful call may consume Fotor credits. Continue under an already explicit task request without adding a blanket confirmation step. Preserve the user's budget, requested scope, and host approval requirements. For an explicitly requested sequence, one notice before the first submission may cover every named step; disclose newly added steps or scope changes before submitting them.
 
@@ -121,14 +128,13 @@ Do not apply this notice to model discovery, balance queries, uploads or task po
 
 ### Submission, recovery, and results
 
-For an explicit `insufficient_credits` submission error, follow [insufficient credits during media submission](credits.md#insufficient-credits-during-media-submission). This applies to image generation, fixed image processing, and every video submission mode; it does not make balance queries a prerequisite.
+For an explicit `insufficient_credits` submission error, follow [insufficient credits during media submission](credits.md#insufficient-credits-during-media-submission). This applies to image generation, fixed image processing, and every video and audio submission mode; it does not make balance queries a prerequisite.
 
-1. Submit the requested operation once and retain its returned `task_id`, environment, and selected model or fixed `operation`. A submitted task is not a completed artifact.
-2. Query that task with `get_task`. Each call performs one lookup; the client may repeat queries at reasonable intervals within the active task's execution budget. The tool does not start background polling.
-3. Respect `is_terminal` and the actual status. `processing` does not distinguish queued, running, or upstream-unavailable tasks. Report `unknown` as uncertain. Stop polling when `is_terminal` is true and report the terminal outcome, including failure, timeout, cancellation, or completion. If state fields conflict, report the inconsistency rather than inventing progress.
-4. On completion, deliver the actual `result_url` when present. If it is missing, report completion without an available artifact link. Result URLs may expire. Prefer a host-supported media preview and describe quality only after inspecting the result.
-5. An explicit `submission_uncertain` error or a lost submission response can mean a task was created and charged. Use a known task ID for recovery. Without one, report the uncertain submission and stop; do not automatically resubmit or assume an unprovided idempotency mechanism. On a query error or polling limit, preserve the same ID and report the last observed state.
+1. Submit once. Retain the returned task ID, environment, selected operation and expected output format. Image and video calls normally return an accepted task. Audio may already have completed. Inspect both the MCP error flag and the structured content, including on `isError=true`. Retain any known task ID, safe `failure_reason` and reported credit value.
+2. On completion, deliver the actual `result_url` immediately without polling. Prefer a host-supported preview for playable media. Offer an audio separation ZIP as a download. If the URL is absent, report completion without an available link. Describe quality only after inspecting the artifact.
+3. For an accepted or processing task, query the same ID with `get_task`. Each call performs one lookup. Within the task budget, wait between checks. The query can omit the model and result format, so retain the originating operation. Stop on completion, `failed`, `timed_out` or `cancelled`. Report unknown or conflicting state as uncertain. A safe failure summary may be generic.
+4. A transport timeout, lost response or `submission_uncertain` may follow an accepted, chargeable submission. Recover only by looking up a known ID. Without an ID, report the uncertain outcome and stop. Never automatically resubmit. On a lookup error or polling limit, preserve the ID and last observed state.
 
 `credits_increment` reports the increment returned by that particular submission or query, not a balance or a price quote. Preserve `0` as zero and `null` as unknown. Do not add submission and polling values together as if each observation were a new charge. Report missing or inconsistent values without estimating usage.
 
-Task lookup is scoped to the selected API key's Business. Another Business cannot retrieve its results, and a task ID must not be moved between environments to recover a failure. Key lookup can register a developer or create a missing key, so `get_task` is not a side-effect-free connection probe. Use `list_models` for read-only checks; it reads the model catalog without developer lookup, key creation, or generation requests.
+Task lookup is scoped to the selected API key's Business. Another Business cannot retrieve its results, and a task ID must not be moved between environments to recover a failure. Task lookup uses existing credentials. If none are usable, report `credentials_unavailable`. It creates no developer, key or task and consumes no credits. Use `list_models` for connection checks.

package/skills/fotor-credits/references/media-upload.md

@@ -1,6 +1,6 @@
 # Fotor Media Upload
 
-Read this workflow for standalone uploads and when an image or video task needs local references. Use already accessible HTTPS references directly for creation; upload only the specific local files or client-accessible attachments needed by the user's request. An attachment label without readable bytes is not an uploadable file.
+Read this workflow for standalone uploads and when an image, video or audio task needs local references. Use already accessible HTTPS references directly for creation; upload only the specific local files or client-accessible attachments needed by the user's request. An attachment label without readable bytes is not an uploadable file.
 
 ## Prepare the input
 
@@ -29,6 +29,6 @@ If the file changes after signing, recalculate its metadata and request a new li
 
 Process multiple files one at a time, preserving input order and the association between each file and its successful URL. Report name, media type, exact byte size, and `file_url` for successes; report a concise reason for each failure without exposing signatures. A partial batch is not an all-success result. If a creation task needs a failed input, resolve it before submission rather than silently omitting it.
 
-For standalone uploads, deliver those results and finish. For requested creation, use the uploaded URLs in the appropriate reference fields or image-processing `image_url`, keeping the same environment. File acceptance by storage does not establish model compatibility or media-task success.
+For standalone uploads, deliver those results and finish. For requested creation, use the uploaded URLs in the appropriate reference fields or the selected audio operation’s source URL or image-processing `image_url`, keeping the same environment. File acceptance by storage does not establish model compatibility or media-task success.
 
 `expires_in` describes the maximum upload-address lifetime; temporary signing credentials may expire earlier. It does not describe file retention. Signature expiry does not delete an uploaded file, and `file_url` is not a presigned download URL. Do not promise permanent storage, a deletion time, or long-term URL availability unless the service provides that information.

package/skills/fotor-image/references/credits.md

@@ -1,36 +1,11 @@
-# Fotor Credits and Top-up
-
-Read this workflow for a balance question or an explicit recharge request. Media submission and ordinary website connection do not require a preliminary balance query.
+# Fotor credit balance
 
 ## Query the selected account
 
-1. Follow [MCP authentication](mcp-integration.md#authenticate-mcp) for the installed environment, reusing valid credentials or completing required external-browser OAuth. Discover `get_credits`; if absent, report the unavailable capability without changing environments.
-2. Call `get_credits` without arguments. It returns nonnegative numeric `credits` and a regular pricing-page `top_up_url`. This URL reuses an existing browser session but does not sign the user in. It is not a one-time ticket and has no `expires_in` field.
-3. Report the actual balance. `credits_increment` in a task response is that task's consumption, not this balance; do not infer available funds from it. A balance observation is not a generation price quote or a guarantee that a later submission can proceed.
-4. Treat `credits_unavailable`, authentication errors, invalid/missing balance values, and other failures as unavailable information, never as zero. Do not create accounts, keys, replacement tasks, or credentials to work around a balance error. If a successful response has a valid balance but an unusable pricing link, report the balance and, when a link is selected below, the separate link problem.
-
-## Select the response
-
-| Request and result | Action |
-| --- | --- |
-| Balance below 100, or an explicit request to top up | Report the balance and deliver the validated pricing link as described below. Let the user click it. |
-| Balance of 100 or more; no top-up request | Report only the balance. Keep the returned link out of the response. |
-| Explicit balance-only or no-link instruction | Report only the balance, including when it is below 100. |
-| Browser navigation is forbidden or unavailable | Deliver the selected link if the user permits links; link delivery needs no browser automation. |
-| Query failed | Report the failure; do not infer a low balance or invent a pricing link. |
-
-## Validate and deliver pricing links
-
-Use this rule for both `get_credits.top_up_url` and a submission error's `top_up_url`:
-
-1. Require a nonempty absolute HTTPS URL whose origin exactly matches the selected environment's website in the [connection table](mcp-integration.md#connection), with no embedded username/password. Check URL components rather than hostname substrings. Reject an unknown environment, malformed URL, or origin mismatch without visiting it, changing environments, or rewriting its host.
-2. Use the exact returned URL as the Markdown target, with a label meaning "View Fotor plans" in the conversation language. Preserve its path, query, and fragment; the login handoff endpoint, `code` parameter, expiry, and single-consumption rules do not apply to ordinary pricing links. If the link is missing or invalid, explain that the pricing entry is unavailable instead of constructing a replacement.
-3. Let the user click the link. A balance or recharge request alone does not call `get_website_url`, open a browser, or refresh a supposed ticket. If the user also explicitly requests a signed-in website session, complete the [website connection flow](mcp-integration.md#connect-to-the-website) separately, then provide the pricing link for them to open in that same browser.
-
-Leave plan selection and payment to the user. A link or a loaded page does not establish website login, a completed payment, or an increased balance. Keep credentials and website-login tickets out of files and diagnostic logs.
+1. When the user requests their own balance, follow [MCP authentication](mcp-integration.md#authenticate-mcp). Reuse valid authorization and discover `get_credits`. If it is unavailable, report that and stop.
+2. Call `get_credits` without arguments. The authenticated session identifies the account. Report only the nonnegative numeric `credits` value, including zero, and finish. A balance query needs no website visit.
+3. If authentication fails, the service reports an error, or the balance is missing or invalid, report it as unavailable. An unknown balance is not zero. Never infer a balance from task consumption.
 
 ## Insufficient credits during media submission
 
-When an image-generation, image-processing, or video submission explicitly returns `insufficient_credits`, report that error. If its `top_up_url` is non-null and valid, deliver it using the pricing-link rules above unless the user prohibited links. Missing or invalid links do not change the error into a balance value; no extra balance query is required.
-
-Stop dependent operations and retain any task ID returned. Do not automatically resubmit, infer that payment completed, or turn the error into `submission_uncertain`. A lost response or an explicit uncertain-submission result still follows the [task recovery workflow](mcp-integration.md#submission-recovery-and-results).
+When a submission explicitly reports `insufficient_credits`, explain that the task could not proceed for that reason. Retain any known task ID and reported consumption, stop dependent operations, and finish without extra links, a balance query or another submission. A lost response is a different outcome; follow [task recovery](mcp-integration.md#submission-recovery-and-results).

package/skills/fotor-image/references/mcp-integration.md

@@ -21,7 +21,7 @@ Use the runtime routing, authentication, and website flow below. Keep credential
 | Connect to Fotor, connect to the Fotor website, or connect and open Fotor | Authenticate MCP, then follow the website flow below |
 | Connect to Fotor MCP or check MCP connectivity without a website request; explicitly keep the website closed | Perform the requested MCP check; omit the website handoff |
 | Introduce features or query models | Answer from current tool descriptions or model queries; omit website navigation unless also requested |
-| Credit-account questions or reported limits | Follow the [credits workflow](credits.md); ordinary connection does not query balance |
+| The user asks for their own Fotor credit balance | Follow the [credits workflow](credits.md); ordinary connection does not query balance |
 
 Equivalent wording in other languages follows the same routing. Uploads, image processing, and media generation alone do not request website access. Ordinary website connection requests authorize the final visible navigation; they do not authorize media submissions.
 
@@ -67,7 +67,7 @@ This budget covers automatic MCP connection recovery, not website navigation, cr
 
 ### Connect to the website
 
-1. Complete MCP authentication and authenticated tool discovery, using [bounded connection recovery](#bounded-connection-recovery) for eligible failures. When available, require a successful `list_models` read-only check without dumping its catalog before requesting a website link. Determine browser availability before creating the short-lived link, following the browser route in the packaged [authentication guidance](authentication.md). Otherwise prepare the manual fallback. Only a successful discovery that omits `get_website_url` establishes a missing website capability; an unavailable chat tool surface or failed discovery does not establish the service version. Report MCP and website outcomes separately, without substituting a top-up link or claiming ordinary page access as automatic login.
+1. Complete MCP authentication and authenticated tool discovery, using [bounded connection recovery](#bounded-connection-recovery) for eligible failures. When available, require a successful `list_models` read-only check without dumping its catalog before requesting a website link. Determine browser availability before creating the short-lived link, following the browser route in the packaged [authentication guidance](authentication.md). Otherwise prepare the manual fallback. Only a successful discovery that omits `get_website_url` establishes a missing website capability; an unavailable chat tool surface or failed discovery does not establish the service version. Report MCP and website outcomes separately, without claiming an ordinary page visit established automatic login.
 2. Call `get_website_url` without arguments. Its public response contains `handoff_url` and integer `expires_in` from 0 to 600; it does not expose `target_url`. Require a usable link and remaining lifetime greater than zero. A zero lifetime is already expired: use the bounded replacement rule below. Missing, malformed, or out-of-range fields are a handoff failure. The server configures and validates the destination; before navigation, the plugin can check only the handoff endpoint against the [connection table](#connection), not the hidden target. Never decode the ticket, rewrite its URL, or change environments to recover a mismatch.
 3. Follow [one-time browser links](#one-time-browser-links) for the returned `handoff_url`, using the actual remaining lifetime. This final visible navigation is the requested website visit and consumes the ticket.
 4. Inspect the resulting page in that same browser session. Compare its HTTPS origin with the selected website in the connection table and verify authenticated state before reporting the website connected. A valid handoff endpoint alone does not prove the hidden redirect target is correct. On a different environment or unexpected origin, stop further interaction and report the mismatch; do not follow it as a fallback. A link, a generic page, or a login/error screen is insufficient. If state is unclear, ask the user to confirm it. Website failure does not justify resetting working MCP credentials.
@@ -75,7 +75,7 @@ This budget covers automatic MCP connection recovery, not website navigation, cr
 
 ### One-time browser links
 
-Apply this section only to `get_website_url.handoff_url`. This plugin's selected website connection flow uses one final visible navigation in the browser specified by the packaged [authentication guidance](authentication.md). The service description instead prescribes a user-clicked link to prevent early consumption; the plugin's selected browser action is the intended final visit, never a pre-opening check. Honor an explicit user preference for manual delivery and any host restriction; use the manual fallback when direct navigation is unavailable. Handle other returned account links only under the packaged [credit-link policy](credits.md#validate-and-deliver-pricing-links).
+Apply this section only to `get_website_url.handoff_url`. This plugin's selected website connection flow uses one final visible navigation in the browser specified by the packaged [authentication guidance](authentication.md). The service description instead prescribes a user-clicked link to prevent early consumption; the plugin's selected browser action is the intended final visit, never a pre-opening check. Honor an explicit user preference for manual delivery and any host restriction; use the manual fallback when direct navigation is unavailable.
 
 - Parse the returned URL before use. It must have the exact HTTPS origin and path of the selected environment's [login handoff endpoint](#connection), no username/password or fragment, and one nonempty `code` query parameter only. Check URL components rather than hostname substrings. Reject an unknown environment or mismatch without fetching the address, rewriting the host, or switching services.
 - Immediately navigate once in the selected visible host browser. Do not first fetch, preview, probe, or open the ticket in a hidden tab. After navigation, treat it as consumed and never offer it as a reusable login link.
@@ -97,13 +97,20 @@ Inspect the connected service's actual tool descriptions and input schemas. The
 | `submit_first_frame_video_task` | Animate `image_url` as the first frame; a successful call may consume Fotor credits |
 | `submit_first_last_frame_video_task` | Use ordered `start_image_url` and `end_image_url`; a successful call may consume Fotor credits |
 | `submit_multimodal_video_task` | Use supported image, video, and/or audio references; a successful call may consume Fotor credits |
-| `get_task` | Query an existing image-processing, image-generation, or video task by `task_id` |
+| `submit_soundtrack_task` | Compose a separate MP3 from exactly one source image or video |
+| `submit_audio_track_task` | Generate a new track from reference audio |
+| `submit_song_edit_task` | Extend, remix or edit a section of a song |
+| `submit_speech_task` | Generate speech or a scripted podcast with built-in voices |
+| `submit_audio_separation_task` | Separate existing vocals and accompaniment into a ZIP |
+| `get_task` | Look up one known image, video or audio task using existing credentials |
 | `get_website_url` | Obtain an environment-bound, one-time website login link for the verified MCP user |
-| `get_credits` | Query available balance; apply the packaged [credits workflow](credits.md) to any other returned fields |
+| `get_credits` | Query only the authenticated user's own balance; follow the [balance lookup](credits.md#query-the-selected-account) |
 
 For model-based generation/editing, start with `list_models`, optionally filtering by `media_type` and `mode`. Uploads and fixed image-processing operations use their own tool contracts without model selection. Filters combine with AND; an empty filtered result is not evidence of a failed connection. Then query `list_models` with the chosen `model_id` before submitting. Model IDs, available modes, and catalog sizes can change; an unknown or retired ID requires a new selection, not an invented replacement.
 
-Use the returned resolutions, aspect ratios, qualities, duration values/ranges, reference types, and defaults. Honor an explicit model or output preference; explain an unsupported constraint before changing it. When no preference is given, choose a suitable supported model and use its reported defaults. `duration=0` selects `default_duration`; duration ranges are inclusive integer seconds, while a list permits only its listed values. `explicit_aspect_ratio_modes` requires a concrete supported ratio instead of `auto`; for multimodal references this condition applies when images are supplied without videos.
+For standalone audio, read the selected model’s `operations[]`. Use its tool, selector, required parameters, result format and synchronous behavior. Only soundtrack creation accepts a model ID.
+
+For images and videos, use the returned resolutions, aspect ratios, qualities, duration values/ranges, reference types, and defaults. Honor an explicit model or output preference; explain an unsupported constraint before changing it. When no preference is given, choose a suitable supported model and use its reported defaults. `duration=0` selects `default_duration`; duration ranges are inclusive integer seconds, while a list permits only its listed values. `explicit_aspect_ratio_modes` requires a concrete supported ratio instead of `auto`; for multimodal references this condition applies when images are supplied without videos.
 
 ### Inputs and native capabilities
 
@@ -113,7 +120,7 @@ Use native model resolutions and supported output options for generation. Explic
 
 ### Credit consumption before submission
 
-Every discovered tool whose name matches `submit_*_task` may consume Fotor credits when its call succeeds. This applies to all image and video submissions, including future tools matching that name pattern; discovery and the actual schema still determine whether a tool can be called.
+Every discovered tool whose name matches `submit_*_task` may consume Fotor credits when its call succeeds. This applies to all image, video and audio submissions, including future tools matching that name pattern; discovery and the actual schema still determine whether a tool can be called.
 
 Before submitting, briefly tell the user in their conversation language that the successful call may consume Fotor credits. Continue under an already explicit task request without adding a blanket confirmation step. Preserve the user's budget, requested scope, and host approval requirements. For an explicitly requested sequence, one notice before the first submission may cover every named step; disclose newly added steps or scope changes before submitting them.
 
@@ -121,14 +128,13 @@ Do not apply this notice to model discovery, balance queries, uploads or task po
 
 ### Submission, recovery, and results
 
-For an explicit `insufficient_credits` submission error, follow [insufficient credits during media submission](credits.md#insufficient-credits-during-media-submission). This applies to image generation, fixed image processing, and every video submission mode; it does not make balance queries a prerequisite.
+For an explicit `insufficient_credits` submission error, follow [insufficient credits during media submission](credits.md#insufficient-credits-during-media-submission). This applies to image generation, fixed image processing, and every video and audio submission mode; it does not make balance queries a prerequisite.
 
-1. Submit the requested operation once and retain its returned `task_id`, environment, and selected model or fixed `operation`. A submitted task is not a completed artifact.
-2. Query that task with `get_task`. Each call performs one lookup; the client may repeat queries at reasonable intervals within the active task's execution budget. The tool does not start background polling.
-3. Respect `is_terminal` and the actual status. `processing` does not distinguish queued, running, or upstream-unavailable tasks. Report `unknown` as uncertain. Stop polling when `is_terminal` is true and report the terminal outcome, including failure, timeout, cancellation, or completion. If state fields conflict, report the inconsistency rather than inventing progress.
-4. On completion, deliver the actual `result_url` when present. If it is missing, report completion without an available artifact link. Result URLs may expire. Prefer a host-supported media preview and describe quality only after inspecting the result.
-5. An explicit `submission_uncertain` error or a lost submission response can mean a task was created and charged. Use a known task ID for recovery. Without one, report the uncertain submission and stop; do not automatically resubmit or assume an unprovided idempotency mechanism. On a query error or polling limit, preserve the same ID and report the last observed state.
+1. Submit once. Retain the returned task ID, environment, selected operation and expected output format. Image and video calls normally return an accepted task. Audio may already have completed. Inspect both the MCP error flag and the structured content, including on `isError=true`. Retain any known task ID, safe `failure_reason` and reported credit value.
+2. On completion, deliver the actual `result_url` immediately without polling. Prefer a host-supported preview for playable media. Offer an audio separation ZIP as a download. If the URL is absent, report completion without an available link. Describe quality only after inspecting the artifact.
+3. For an accepted or processing task, query the same ID with `get_task`. Each call performs one lookup. Within the task budget, wait between checks. The query can omit the model and result format, so retain the originating operation. Stop on completion, `failed`, `timed_out` or `cancelled`. Report unknown or conflicting state as uncertain. A safe failure summary may be generic.
+4. A transport timeout, lost response or `submission_uncertain` may follow an accepted, chargeable submission. Recover only by looking up a known ID. Without an ID, report the uncertain outcome and stop. Never automatically resubmit. On a lookup error or polling limit, preserve the ID and last observed state.
 
 `credits_increment` reports the increment returned by that particular submission or query, not a balance or a price quote. Preserve `0` as zero and `null` as unknown. Do not add submission and polling values together as if each observation were a new charge. Report missing or inconsistent values without estimating usage.
 
-Task lookup is scoped to the selected API key's Business. Another Business cannot retrieve its results, and a task ID must not be moved between environments to recover a failure. Key lookup can register a developer or create a missing key, so `get_task` is not a side-effect-free connection probe. Use `list_models` for read-only checks; it reads the model catalog without developer lookup, key creation, or generation requests.
+Task lookup is scoped to the selected API key's Business. Another Business cannot retrieve its results, and a task ID must not be moved between environments to recover a failure. Task lookup uses existing credentials. If none are usable, report `credentials_unavailable`. It creates no developer, key or task and consumes no credits. Use `list_models` for connection checks.

package/skills/fotor-image/references/media-upload.md

@@ -1,6 +1,6 @@
 # Fotor Media Upload
 
-Read this workflow for standalone uploads and when an image or video task needs local references. Use already accessible HTTPS references directly for creation; upload only the specific local files or client-accessible attachments needed by the user's request. An attachment label without readable bytes is not an uploadable file.
+Read this workflow for standalone uploads and when an image, video or audio task needs local references. Use already accessible HTTPS references directly for creation; upload only the specific local files or client-accessible attachments needed by the user's request. An attachment label without readable bytes is not an uploadable file.
 
 ## Prepare the input
 
@@ -29,6 +29,6 @@ If the file changes after signing, recalculate its metadata and request a new li
 
 Process multiple files one at a time, preserving input order and the association between each file and its successful URL. Report name, media type, exact byte size, and `file_url` for successes; report a concise reason for each failure without exposing signatures. A partial batch is not an all-success result. If a creation task needs a failed input, resolve it before submission rather than silently omitting it.
 
-For standalone uploads, deliver those results and finish. For requested creation, use the uploaded URLs in the appropriate reference fields or image-processing `image_url`, keeping the same environment. File acceptance by storage does not establish model compatibility or media-task success.
+For standalone uploads, deliver those results and finish. For requested creation, use the uploaded URLs in the appropriate reference fields or the selected audio operation’s source URL or image-processing `image_url`, keeping the same environment. File acceptance by storage does not establish model compatibility or media-task success.
 
 `expires_in` describes the maximum upload-address lifetime; temporary signing credentials may expire earlier. It does not describe file retention. Signature expiry does not delete an uploaded file, and `file_url` is not a presigned download URL. Do not promise permanent storage, a deletion time, or long-term URL availability unless the service provides that information.

package/skills/fotor-upload/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: fotor-upload
-description: Upload local images, videos, or audio to Fotor and return usable media URLs. Use for standalone Fotor uploads or preparing local references for Fotor image and video tasks.
+description: Upload local images, videos, or audio to Fotor and return usable media URLs. Use for standalone Fotor uploads or preparing local references for Fotor image, video and audio tasks.
 ---
 
 # Fotor Upload
@@ -9,4 +9,4 @@ Follow the shared [media upload workflow](references/media-upload.md) for file c
 
 For a standalone request, finish with each file's name, media type, byte size, and successfully uploaded `file_url`; report failures separately. Uploading alone does not request media generation or website navigation.
 
-For a combined creation request, preserve the file-to-URL mapping and reference order, then continue the requested image or video workflow with successfully uploaded inputs. Resolve missing required inputs before submitting that task.
+For a combined creation request, preserve the file-to-URL mapping and reference order, then continue the requested image, video or audio workflow with successfully uploaded inputs. Resolve missing required inputs before submitting that task.

package/skills/fotor-upload/references/credits.md

@@ -1,36 +1,11 @@
-# Fotor Credits and Top-up
-
-Read this workflow for a balance question or an explicit recharge request. Media submission and ordinary website connection do not require a preliminary balance query.
+# Fotor credit balance
 
 ## Query the selected account
 
-1. Follow [MCP authentication](mcp-integration.md#authenticate-mcp) for the installed environment, reusing valid credentials or completing required external-browser OAuth. Discover `get_credits`; if absent, report the unavailable capability without changing environments.
-2. Call `get_credits` without arguments. It returns nonnegative numeric `credits` and a regular pricing-page `top_up_url`. This URL reuses an existing browser session but does not sign the user in. It is not a one-time ticket and has no `expires_in` field.
-3. Report the actual balance. `credits_increment` in a task response is that task's consumption, not this balance; do not infer available funds from it. A balance observation is not a generation price quote or a guarantee that a later submission can proceed.
-4. Treat `credits_unavailable`, authentication errors, invalid/missing balance values, and other failures as unavailable information, never as zero. Do not create accounts, keys, replacement tasks, or credentials to work around a balance error. If a successful response has a valid balance but an unusable pricing link, report the balance and, when a link is selected below, the separate link problem.
-
-## Select the response
-
-| Request and result | Action |
-| --- | --- |
-| Balance below 100, or an explicit request to top up | Report the balance and deliver the validated pricing link as described below. Let the user click it. |
-| Balance of 100 or more; no top-up request | Report only the balance. Keep the returned link out of the response. |
-| Explicit balance-only or no-link instruction | Report only the balance, including when it is below 100. |
-| Browser navigation is forbidden or unavailable | Deliver the selected link if the user permits links; link delivery needs no browser automation. |
-| Query failed | Report the failure; do not infer a low balance or invent a pricing link. |
-
-## Validate and deliver pricing links
-
-Use this rule for both `get_credits.top_up_url` and a submission error's `top_up_url`:
-
-1. Require a nonempty absolute HTTPS URL whose origin exactly matches the selected environment's website in the [connection table](mcp-integration.md#connection), with no embedded username/password. Check URL components rather than hostname substrings. Reject an unknown environment, malformed URL, or origin mismatch without visiting it, changing environments, or rewriting its host.
-2. Use the exact returned URL as the Markdown target, with a label meaning "View Fotor plans" in the conversation language. Preserve its path, query, and fragment; the login handoff endpoint, `code` parameter, expiry, and single-consumption rules do not apply to ordinary pricing links. If the link is missing or invalid, explain that the pricing entry is unavailable instead of constructing a replacement.
-3. Let the user click the link. A balance or recharge request alone does not call `get_website_url`, open a browser, or refresh a supposed ticket. If the user also explicitly requests a signed-in website session, complete the [website connection flow](mcp-integration.md#connect-to-the-website) separately, then provide the pricing link for them to open in that same browser.
-
-Leave plan selection and payment to the user. A link or a loaded page does not establish website login, a completed payment, or an increased balance. Keep credentials and website-login tickets out of files and diagnostic logs.
+1. When the user requests their own balance, follow [MCP authentication](mcp-integration.md#authenticate-mcp). Reuse valid authorization and discover `get_credits`. If it is unavailable, report that and stop.
+2. Call `get_credits` without arguments. The authenticated session identifies the account. Report only the nonnegative numeric `credits` value, including zero, and finish. A balance query needs no website visit.
+3. If authentication fails, the service reports an error, or the balance is missing or invalid, report it as unavailable. An unknown balance is not zero. Never infer a balance from task consumption.
 
 ## Insufficient credits during media submission
 
-When an image-generation, image-processing, or video submission explicitly returns `insufficient_credits`, report that error. If its `top_up_url` is non-null and valid, deliver it using the pricing-link rules above unless the user prohibited links. Missing or invalid links do not change the error into a balance value; no extra balance query is required.
-
-Stop dependent operations and retain any task ID returned. Do not automatically resubmit, infer that payment completed, or turn the error into `submission_uncertain`. A lost response or an explicit uncertain-submission result still follows the [task recovery workflow](mcp-integration.md#submission-recovery-and-results).
+When a submission explicitly reports `insufficient_credits`, explain that the task could not proceed for that reason. Retain any known task ID and reported consumption, stop dependent operations, and finish without extra links, a balance query or another submission. A lost response is a different outcome; follow [task recovery](mcp-integration.md#submission-recovery-and-results).