Update to Yaps Video to Audio

{
  "name": "yaps-video-to-audio",
  "description": "Convert a video file to MP3, WAV, or M4A audio with the installed Yaps desktop app. Trigger for video to audio, convert video to MP3, convert video to WAV, convert video to M4A, extract audio from video, save a video's sound, remove the video track, or make an audio-only copy of a video. Do not use when the user wants a transcript, subtitles, or text-to-speech.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 189
    }
  ],
  "skill_md_contents": "---\nname: yaps-video-to-audio\ndescription: Convert a video file to MP3, WAV, or M4A audio with the installed Yaps desktop app. Trigger for video to audio, convert video to MP3, convert video to WAV, convert video to M4A, extract audio from video, save a video's sound, remove the video track, or make an audio-only copy of a video. Do not use when the user wants a transcript, subtitles, or text-to-speech.\n---\n\n# Yaps Video to Audio\n\nCreate one audio-only file from an existing video through Yaps.\n\n## Runtime compatibility\n\nDo not try to guess the host or its locality from a user-agent, product name,\nor another host signal (for example ChatGPT web versus ChatGPT desktop). Test\nthe capability this workflow actually needs: before account, dependency, or\ninput-file checks, resolve the local Yaps CLI through the plugin runner. The\nrunner validates it with a bounded, read-only `status` command. A cloud shell\nthat cannot see the installed Yaps app is not local access to the user's\ncomputer.\n\nIf the Yaps CLI is unreachable, do not claim that Yaps is uninstalled and do\nnot begin repeated sign-in, dependency, or permission troubleshooting. Explain\nthat the current AI session cannot reach the Yaps engine installed on this\ncomputer. Direct the user to a local-capable session on the\ncomputer where Yaps is installed: in Claude, that\nis Claude Code or the Claude desktop app; from ChatGPT web or a cloud session,\n[download or open ChatGPT desktop](https://chatgpt.com/download/) and retry in a\nlocal-capable Work or Codex session. They can also access this feature directly\nin the Yaps application. If they are already in a local-capable desktop session,\noffer [Download or update Yaps](https://yaps.ai/download), ask them to open it,\nand retry. Stop until local reachability is restored; only then follow the\navailability and onboarding steps below.\n\n## Private operational diagnostics\n\nRun every local Yaps CLI command and every bundled workflow script through the\nplugin's `scripts/yaps-plugin-runner.mjs`. The runner resolves the installed\nYaps CLI when the command begins with `yaps`, preserves the command's normal\noutput and exit status, and leaves a small local diagnostic breadcrumb for the\nYaps desktop app:\n\n```text\nnode <plugin-root>/scripts/yaps-plugin-runner.mjs --action auth.status --stage authentication -- yaps auth status --pretty\n```\n\nChoose a stable, content-free action such as `cli.reachability`,\n`auth.status`, `features.list`, `dictation.setup`,\n`transcription.run`, or `export.create`; use the matching stage:\n`reachability`, `authentication`, `readiness`, `execution`, or\n`export`. In the rest of this skill, every direct `yaps` / `yaps_cli`\ncommand and provided script invocation means the equivalent runner-wrapped\ncommand. If Node or the runner itself is unavailable, continue the requested\nworkflow directly; diagnostics must never prevent the feature from working.\n\nThe breadcrumb may contain only plugin ID/version, detected integration host,\naction, stage, attempt/outcome, duration, and a fixed safe error category. It\nmust never contain the user's prompt or conversation, command arguments,\nstdout/stderr, credentials, file paths or names, audio, transcript/note text,\nor raw error messages. It is written only when Yaps has supplied an opaque\nsigned-in owner marker, stays on-device while offline, and is picked up later\nby the Yaps app. Never create or guess an owner marker.\n\n## CLI discovery contract\n\nAlways invoke Yaps through `scripts/yaps-plugin-runner.mjs`; do not locate the\nbinary by hand. The runner honors an explicit path or `YAPS_CLI_BINARY`, then\nchecks `PATH`, then the verified Yaps app locations on macOS, Windows, and\nLinux. It accepts a candidate only after a bounded, read-only `status` check.\nNever ask the user to install a separate CLI, edit `PATH`, or configure MCP for\nthis skill. Never invoke the macOS GUI binary at\n`Yaps.app/Contents/MacOS/yaps`. If discovery fails, repeat the runner's specific\nrecovery guidance instead of claiming that the plugin is disconnected.\n\n## Availability\n\nYaps desktop supplies the media workflow, account state, and local CLI. Let the runner resolve and validate the CLI automatically.\n\nNever request Yaps credentials or payment details in the AI client. Yaps no longer has a free tier. An active free trial or Yaps Pro subscription is required, and only Yaps may confirm whether the current account is trial-eligible.\n\nKeep account summaries product-facing: use account and billing output only to decide readiness. Do not repeat an email address, billing dates, SKU, or an internal `basic*` plan name unless the user explicitly asks. Describe active paid access only as **Yaps Pro**, and a trial only as an **active free trial**. Never promise “no setup”, “no download”, or “no further input” until the dependency checks have actually confirmed that.\n\n## Account recovery\n\nThe runner follows a valid `recommended_settings_path` automatically and uses\nit for the requested command. If the signed-in desktop account cache is\ntemporarily incomplete, it safely wakes the verified installed Yaps app and\nrechecks for a bounded time. Do not copy settings paths, construct app paths,\ntell the user to edit `PATH`, or ask them to reconnect the plugin. A different\nClaude or ChatGPT account email is irrelevant; never compare it with the Yaps\nemail or ask the user to create a second account.\n\nSafe automatic account handoff requires Yaps 2.3.124 or newer. The runner\nrefuses the older credential-based account check and gives update guidance\nwithout touching Keychain. `auth status` must not request a credential or\ndisplay a Keychain prompt. Never\nask the user to enter their macOS login password or approve a credential\nprompt. If `credential_unavailable` or `keychain_unavailable` appears, repeat\nthe runner's app-update guidance. If `credential_missing`, `cached_offline`,\n`verification_unavailable`, `account_cache_incomplete`, `refresh_failed`, or\n`profile_lookup_failed` remains after the runner's automatic wake and retry,\nreport its exact network/cache guidance. Do not add a manual reconnection step.\nOnly `unauthenticated` / `signed_out` means sign-in is needed.\n\n## First-run onboarding\n\n1. Confirm through the runner that Yaps 2.3.124 or newer is installed. Do not ask the user to open it before processing media.\n2. Run `yaps auth status --pretty`. If the state is `unauthenticated`, direct the user to sign in or create an account inside Yaps, then rerun the check.\n3. Require `authenticated: true` and `status: \"active\"`. Active access may be an active free trial or Yaps Pro.\n4. Do not run `auth billing` as an automatic gate. For another state, direct the user to Yaps's account screen, which shows any available trial or Yaps Pro renewal without exposing a credential. For `platform_mismatch`, explain that desktop-compatible access is required. Stop until `auth status` becomes active.\n5. Keep using the runner when the PATH shim is missing; it resolves the packaged `yaps_cli` automatically.\n6. Run `ffmpeg -version`. If unavailable, explain that Yaps needs FFmpeg for media conversion and give the platform-specific instruction reported by Yaps. Do not install a system package without explicit approval.\n7. Resolve the exact source-video path, format, and output path. Treat one successfully verified audio file as onboarding completion.\n\n## Convert\n\nDefault to MP3 unless the user requests WAV or M4A. When no destination is specified, place the output beside the source as `<video name> Audio.<format>`.\n\nBefore running anything, check whether the output path already exists. Never replace it without explicit approval; prefer a new filename.\n\nRun:\n\n```text\nyaps --pretty media extract-audio <video-path> --format <mp3|wav|m4a> --output <audio-path>\n```\n\nKeep using the runner when the PATH shim is unavailable. If `media extract-audio` is unknown, ask the user to update Yaps and retry rather than bypassing Yaps with a separate converter.\n\n## Verify and report\n\nTreat the returned JSON as authoritative for the source path, output path, format, and bytes written. Confirm the output exists and is non-empty, then return a link to it.\n\nIf Yaps reports that the source has no audio stream, say so. Do not manufacture an empty file or silently switch to a hosted conversion service.\n\n## Generalist Yaps mode\n\nVideo-to-audio conversion is this plugin's default focus, not a boundary around what it can do. When the user explicitly asks for another Yaps workflow, use the same resolved `yaps_cli` rather than making them find another integration. The full local surface is:\n\n```text\nstatus\nsettings list|get|set|unset\nauth status|usage|billing\nfeatures list|dictation|cleanup|reading|subtitles|auto-captions|audio-cleaner|text-in-between|background-removal|translation|meeting\nvault status|list|get|create|update|move|rename|delete|search|search-semantic|daily-open|create-from-template|history-list|history-restore|pin|folders|tags|mentions|backlinks\nspeech synthesize (alias: tts)\nsrt generate\nmeeting transcribe|show|correct|assign|rename-speaker|export\ncaptions styles|create|show|correct|replace|split|merge|style|reset|render|verify\nmedia extract-audio|remove-background|generate-image\naudio clean\ntranslate\nhistory-list\nusage-local\n```\n\nRun `<cli> --help` and the relevant group help before an unfamiliar workflow. If the session cannot reach the local CLI (for example ChatGPT web), offer a local-capable session — Claude Code, or [ChatGPT desktop](https://chatgpt.com/download/) for a Work or Codex task — or offer to guide the user through the same workflow in **Yaps → Media**.\n\n## Friendly completion and discovery\n\nLead with a warm outcome such as “Done — your audio file is ready,” then link the output and report its format and size. Do not dump raw JSON or internal plan names. After a successful task, add one compact **More with Yaps** section with up to three relevant next steps, such as transcribing the audio, cleaning it, or creating subtitles in Yaps. Skip it after a failure, a decline, or when the user asks for a terse result.\n\n## Boundaries\n\n- Use Yaps Transcription for plain-text speech transcription.\n- Use Yaps Subtitle Generator for timed SRT captions.\n- Use Yaps Text to Speech when the source is text rather than video.\n- Do not retain another copy of the source video.\n"
}