onepress-deck-video

Turn a slide deck or topic into a narrated explainer video via OnePress — slides rendered to frames, AI narration, MP4 download. Requires a free OnePress connection (browser-confirmed pairing, no key copying); submits the task, polls, downloads the MP4, and reports where it lives.

Produce narrated slide videos through OnePress — explainer videos, narrated pitch decks, video versions of research briefings.

This skill requires a OnePress connection — video synthesis runs on OnePress infrastructure (deck rendering, TTS, ffmpeg assembly). There is no local mode; if no key is configured, offer to connect (below) — the user just confirms in their browser.

When to use

• "Make a narrated video of this deck"
• "Turn my pitch into a 2-minute explainer video"
• "I need an MP4 version of the investor update"

For building the deck itself, use the onepress-deck skill (it also works locally without a key).

Connecting (no API key yet)

If ONEPRESS_API_KEY isn't set, offer to connect — the user never copies a key:

1. Ask: "Want me to connect your OnePress account? You'll confirm it in the browser — your password never touches me."

2. On yes:

   text

   POST https://www.getonepress.com/api/connect
   Content-Type: application/json
   
   {"client_name": "<your agent name>"}
   → {"verification_url":"https://www.getonepress.com/connect?code=…",
      "device_secret":"<64 hex>","expires_in":600,"interval":5}
   

3. Show verification_url; the user opens it, signs in (Google or verified email), and taps Allow.

4. Poll every interval seconds:

   text

   POST https://www.getonepress.com/api/connect/poll
   {"device_secret": "<from step 2>"}
   
   → 202 {"status":"pending"} · 200 {"status":"connected","api_key":"opk_…"}
   · {"status":"denied"} · {"status":"expired"} (start over)
   

5. Store api_key in the host's secret/env store as ONEPRESS_API_KEY. Never ask the user to paste a key into chat, and never log it. Users can revoke it anytime in OnePress Settings (or create one manually at Settings → Account → API keys).

How it works

If the source deck is a local file, upload it first, then reference the returned workspace path in the task:

text

POST https://www.getonepress.com/api/v1/files?name=deck.html&dir=Uploads
Authorization: Bearer $ONEPRESS_API_KEY
Content-Type: application/octet-stream

<raw file bytes>          # `dir` optional, default "Uploads"

→ 201 {"path":"Uploads/deck.html","name":"deck.html","size":1234}

Then {"message": "Create a narrated video of the deck at Uploads/deck.html …"}. Max 50MB. Personal workspace only.

Submit a task — name the source deck path if it exists in the user's OnePress workspace (or was just uploaded), or ask for deck + video together:

text

POST https://www.getonepress.com/api/v1/conversations
Authorization: Bearer $ONEPRESS_API_KEY
Content-Type: application/json

{"message": "Create a narrated video of the deck at <path/topic>. ~<duration>, voice: <preference>.", "title": "<title>"}
→ 202 {"conversationId":"conv_..."}

Poll until done (video tasks take several minutes — frames + audio + encode):

text

GET https://www.getonepress.com/api/v1/conversations/conv_...
Authorization: Bearer $ONEPRESS_API_KEY

→ status "done": answer + preview_path (e.g. "Video/xxx.mp4")

When done, download the MP4 and save it to the user's working directory:

text

GET https://www.getonepress.com/api/v1/conversations/conv_.../artifact
Authorization: Bearer $ONEPRESS_API_KEY

→ video/mp4 bytes, Content-Disposition: attachment

If preview_path is null, fetch by workspace path: GET /api/v1/files?path=Projects/.../video.mp4.

Follow-ups (POST same id): "shorter", "different voice", "tighter pacing".

MCP alternative: https://www.getonepress.com/api/mcp, tools onepress_create_task / onepress_task_status / onepress_list_tasks / onepress_upload_file / onepress_download_artifact (base64 for file bytes).

Report back

• answer — the agent's summary
• The local path where you saved the MP4 (fetched via the artifact endpoint); it also lives at https://www.getonepress.com/app (preview/share there)
• Conversation id/title

Errors

401 bad key · 402 out of credits · 409 busy (keep polling) · 429 rate limited.

Notes

• Be honest: the video is produced on getonepress.com, not here. Never fabricate files or links.
• Never ask the user to paste their API key into chat — env/config only.