specs-leaf-run-in-preview

Runs LEAF scenarios in the Lens Studio Preview panel via the Lens Studio MCP.

16|2|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/lens-studio-devs/ls-extensions --skill specs-leaf-run-in-preview-lens-studio-devs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specs-leaf-run-in-preview
Source: https://github.com/lens-studio-devs/ls-extensions/tree/main/plugins/ls-clad/skills/specs-leaf-run-in-preview
Command: npx skills add https://github.com/lens-studio-devs/ls-extensions --skill specs-leaf-run-in-preview-lens-studio-devs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running LEAF test scenarios inside Lens Studio normally requires manual panel interaction and log digging. This Skill automates opening the LeafPlugin panel, listing registered scenarios, executing them, and diagnosing failures directly from the Lens Studio log. ## Core Features & Use Cases - Panel and scenario orchestration: Verifies the LeafPlugin is installed, opens the LEAF panel, and lists all registered scenarios with their configs through the Lens Studio MCP. - Parameterized scenario execution: Runs scenarios by id with optional parameter overrides and per-call timeout control, enforcing serial execution to avoid scene-reset aborts. - Log-based failure diagnosis: Sets a log baseline, re-runs failures at DEBUG level, and reads the Lens Studio log slice to distinguish explicit failures, scene-reset aborts, and genuine hangs. - Use Case: After authoring scenarios with the specs-leaf-write-scenarios skill, run them in the Preview panel, then get a report table with each scenario's outcome and the verbatim scenario-manager error line for any failure. ## Quick Start Run my registered LEAF scenarios in the Lens Studio Preview panel and report which ones passed or failed.

Frequently Asked Questions about specs-leaf-run-in-preview

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

FAQPage Schema
How do I run LEAF scenarios in Lens Studio Preview?

Open the LEAF panel through the Lens Studio MCP, list the registered scenarios, then invoke the scenario-run capability with the scenario id. Runs must be issued serially because each run resets the Lens scene.

How do I pass parameters to a LEAF scenario run?

Pass a parameters object alongside the scenarioId in the scenario-run call. Keys must already exist in the scenario's default config, and you can override the timeout with __leaf__timeout_secs.

Why did my LEAF scenario run time out without a result?

A timeout usually means the scenario was aborted by a scene reset from a parallel run, or it hung on an unresolved await. Read the Lens Studio log from a baseline offset to find the scenario-manager RUNS, PASSED, or FAILED entries.

What is required before running LEAF scenarios in preview?

You need the Lens Studio MCP with LEAF capabilities, the LeafPlugin installed from the Lens Studio Asset Library and enabled in Plugin Manager, and at least one registered LEAF scenario in the project.

Can I run multiple LEAF scenarios in parallel?

No. Scenario-run calls must be serial because each call resets the Lens scene. A second call dispatched mid-run aborts the first scenario, which then times out with a generic error.