ppt-workbench-studio

Read source links, shape a Studio prompt, and launch browser-based deck generation.

17|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Mijiang111/SylvaDeck --skill ppt-workbench-studio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ppt-workbench-studio
Source: https://github.com/Mijiang111/SylvaDeck/tree/main/skills/ppt-workbench-studio
Command: npx skills add https://github.com/Mijiang111/SylvaDeck --skill ppt-workbench-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates the initial Studio-driven deck creation workflow by translating user-provided source links into a precise Studio prompt and initiating the browser-based generation flow through the local bridge.

Core Features & Use Cases

  • Read source links and shape a Studio prompt that respects the bridge workflow.
  • Post the prompt to the local Studio bridge to obtain an openUrl and open it in the user’s default browser.
  • Support a headless fallback for API-first generation when automation is required.

Quick Start

Describe your deck goal or provide a source link, and I will read it, shape a Studio prompt, and launch Studio.

Frequently Asked Questions about ppt-workbench-studio

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

FAQPage Schema
How do I automate deck generation from source links using a browser-based workflow?▼

Deck generation from source links is automated by reading the sources, shaping a Studio prompt, and posting it to the local bridge to open the launch URL in your default browser.

Can I generate a presentation deck without opening a browser window?▼

Yes, you can generate a presentation deck without a browser by using the headless option, which enables API-first generation through the local Studio bridge.

What is a Studio prompt and how does it drive deck creation?▼

A Studio prompt is a shaped instruction derived from your source links that drives deck creation when posted to the local bridge endpoint to initiate the generation flow.

How do I launch Studio using a specific URL for presentation generation?▼

To launch Studio for presentation generation, the workflow posts your prompt to the bridge launch endpoint, parses the returned openUrl, and opens it in your default browser.

Do I need a local Studio bridge running to automate my presentation workflow?▼

Yes, a local Studio bridge is required because the workflow posts prompts to its API endpoint to retrieve the openUrl needed to launch the browser-based generation flow.

What are the limitations of using a headless option for deck generation?▼

The headless option skips the default browser interface for API-first generation, meaning you will not visually interact with the Studio deck preview during the automated workflow.