使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/oxbshw/watch-skill --skill recovering-from-errors開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
Recovering from errors
Failures use stable error codes and include an actionable fix. Preserve that evidence; do not replace it with a generic explanation.
Diagnose first
watch-skill doctor --jsonRead the failing checks and apply only their stated fixes. doctor can repair managed ffmpeg and yt-dlp binaries, stale locks, corrupt caches, missing frame directories, and known local-model health failures. Re-run it once after remediation.
Retry the original operation once
After doctor is green, repeat the command that failed. If it returns another structured error, report its code, message, and fix. Do not loop indefinitely, silently switch cloud providers, enable cloud STT, or reprocess an already indexed video.
Common routes:
- acquisition or extractor failure:
watch-skill doctor --json, then retry the watch; - provider authentication: verify the matching
WATCHSKILL_*_API_KEYlocally; - provider model not found: run
watch-skill setup-visionwith a valid vision model; - low memory or local server failure: reduce the local model/context or select a cloud
provider the user already has;
- unknown video ID:
watch-skill list, then use the listed ID or original source.
Security and cost policy are invariants during recovery. Never upload the video file, enable a paid provider, or raise the cost ceiling merely to make an error disappear.
