From “what is in this?” to evidence you can inspect.

From a terminal to your first grounded answer.

You do not need to clone the repository. Install the CLI once, let voidscape init add the bundled agent skill, then use it from any folder. No account, API key, or paid backend is required.

1. Install uv once

winget install --id=astral-sh.uv -e

2. Install Voidscape and initialize the skill

uv tool install https://github.com/RikepilB/void-scape/archive/refs/heads/main.zip
uv tool update-shell
voidscape init

init copies the bundled skill to Codex and shared-agent skill roots and checks FFmpeg, FFprobe, and yt-dlp. It never approves cloud processing or a model download. If voidscape is not recognized immediately, open one new terminal.

3. Choose local folders (optional)

Review an Inbox, Library, and local transcription defaults. Preferences save only after explicit confirmation.

voidscape customize

4. Read one file

Replace meeting.mp4 with a local image, audio file, video, folder, or supported public URL:

voidscape doctor
voidscape inspect "meeting.mp4"
voidscape preview "meeting.mp4"
voidscape read "meeting.mp4" --workdir voidscape-output

5. Ask your agent

If your currently open agent does not show Voidscape after installation, start a new agent session.

Choose one file or public URL you are allowed to use.

One local image, carousel folder, article, feed, recording, voice memo, demo, or supported public URL is enough. Start with the key-free demo fixture if you want to see the flow without an account, API key, or personal media.

Look before you process.

Inspect reads source facts: duration, resolution, audio, captions, and local sidecars. Nothing is uploaded or transformed. You learn what is actually available before choosing a path.

voidscape inspect "clip.mp4"

See the tradeoff before you approve it.

Preview explains the frame plan, transcription route, expected dependencies, and API-equivalent vision estimate. If audio would leave your computer or a local model must download for the first time, Voidscape stops for a separate explicit approval.

voidscape preview "clip.mp4" --tier both --backend captions

Create only the evidence you chose.

After the preview is acceptable, read creates an inspectable work folder. Video can produce frames and transcripts; images remain byte-preserving and ordered; articles and feeds become ordered text entries. Every reader writes a manifest. Source files are never changed.

voidscape read "clip.mp4" --tier both --backend captions --workdir out

Give the artifacts to an agent, not just a title.

Open manifest.json plus frames/, transcript.txt, images/, or entries/. Ask for a summary or a concrete answer. The agent cites video moments as [MM:SS], carousel positions as [image 1], articles as [article 1], and feed items as [entry 1]. The CLI prepares evidence; an agent authors the interpretation.

Working helpers and parked directions, clearly labeled.

Repository-only tools are not installed commands. Parked directions still need privacy, platform, and implementation review.

Five commands. The sequence stays the same.

The landing keeps the mechanism short. Use this reference when you need the complete guided surface.