media-toolkit

Upload, transcribe, segment, transform, and matte media files through a JSON-output CLI.

25|1|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/wisdom-in-a-nutshell/agents --skill media-toolkit-wisdom-in-a-nutshell
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: media-toolkit
Source: https://github.com/wisdom-in-a-nutshell/agents/tree/main/skills-source/owned/media-toolkit
Command: npx skills add https://github.com/wisdom-in-a-nutshell/agents --skill media-toolkit-wisdom-in-a-nutshell

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, and includes scripts (resource) and references (resource) components.

What problem does it solve? Running media operations like transcription, segmentation, video transforms, and foreground matting against a backend job API normally requires manual upload handling, bearer-token management, and job polling. This Skill wraps all of that into one deterministic command surface that accepts a local file or URL and returns a stable JSON result envelope. ## Core Features & Use Cases - Artifact-backed transcription: Transcribe local or remote audio/video through the WIN local_transcription provider with diarization, caching, and optional speaker identification, returning transcript text plus transcript/words/sentences artifact URLs. - SAM 3.1 segmentation and matting: Segment images or videos by prompt with anchor/window controls, generating mask URLs by default and optional alpha artifacts, or produce foreground matte manifests. - Upload, transform, and job inspection: Upload local files to S3-backed storage, submit trim/scale/crop transform jobs, and poll or inspect existing jobs by job_id. - Use Case: Given a local podcast recording, run the transcribe subcommand to get the transcript text and cached artifact URLs written to a JSON file for downstream editing steps. ## Quick Start Ask the agent to transcribe a local audio file with the media-toolkit transcribe command and write the JSON result envelope to a file.

Frequently Asked Questions about media-toolkit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I transcribe an audio or video file from the command line?▼

Run the transcribe subcommand with either --file for a local path or --url for remote media. It uses the WIN artifact-backed local_transcription provider with diarization and caching, and returns transcript text plus transcript, words, and sentences artifact URLs in a JSON envelope.

How do I segment an object in a video with SAM 3.1?▼

Use the segment video subcommand with a prompt describing the target, plus optional anchor and window controls like --anchor-seconds, --window-start-seconds, and --window-end-seconds. A mask URL is generated by default, and --with-alpha adds a precomposited alpha artifact.

Can I process a remote media URL without uploading a local file?▼

Yes, every submit command accepts exactly one of --file or --url. When a URL is passed, it is sent directly as media_url; local files are uploaded to S3 cache storage first and then submitted as URLs.

Where does the toolkit read API credentials from?▼

The bearer token is read from ~/.secrets/aipodcasting/env by default, or from the file set by AIPODCASTING_WIN_API_KEY_FILE. Environment fallbacks include WIN_API_KEY, AIP_API_KEY, or the first value in WIN_API_KEYS or AIP_API_KEYS, and secrets should never be passed on command lines.

What happens when a media job takes a long time to finish?▼

Submit commands wait for a terminal job state by default, emitting progress to stderr while the JSON result stays on stdout. Use --no-wait to get the job_id immediately, or inspect later with status --job-id, and tune --poll-timeout-seconds for long jobs.

Why did the media-toolkit command fail with an authentication error?▼

Exit code 3 with an E_AUTH error means the backend rejected the request as unauthorized. Verify that the secret file at ~/.secrets/aipodcasting/env contains a valid WIN_API_KEY or AIP_API_KEY, or set one of the supported environment variables.