V17 / BUNDLED SCENARIO

Start a website preview and capture three screenshots

Start a website preview and capture three screenshots: 2 ordered steps in Lilith V17, with no tool access. Read the exact bundled XML and its input and exit contracts.

V17Pinned source · d6d373561692Exit: copy

Use this scenario

Run

Run project_website_screenshots scenario.

Use run_scenario with the saved scenario name and string-valued inputs. Required values are requested before execution.

View invocation JSON
JSON
{
  "scenario_name": "project_website_screenshots",
  "inputs": {
    "name": "your name",
    "draft_id": ""
  }
}
SCENARIO BLUEPRINT

Read the workflow.

project_website_screenshots2 INPUTS / 0 TOOLS / 2 STEPS
01

Inputs

PARAMETERS
InputRequirementDefault value
nameRequiredNo default
draft_idOptional
02

Agent instructions

SYSTEM PROMPT

Delegate server startup and screenshot capture to separate fresh subagents. Host execution permission is mandatory. Never start a browser without it or present screenshots as functional test results.

03

Tool access

CAPABILITIES

No tools are granted to this child conversation.

04

Ordered steps

EXECUTION
  1. 01
    NESTED SCENARIO / FRESH CHILD

    project_preview_start ↗

    • name = {{name}}
    • draft_id = {{draft_id}}

    Save output as server.

  2. 02
    CONDITION / HOST EVALUATED

    Input server.status equals started

    THEN

    1. 01
      NESTED SCENARIO / FRESH CHILD

      project_preview_capture ↗

      ELSE

      1. 01
        STRUCTURED RESULT / HOST COMPOSED
        • status = {{server.status}}
        • message = {{server.message}}
    05

    Return to main

    COPY EXIT

    Return actual screenshot paths and hashes or the host execution request unchanged.

    The final text returns without model rewriting. Bound operation scenarios return application results; pending changes still require host approval.

    EVERY XML ELEMENT / IN FILE ORDER

    Every part, briefly.

    Short explanations of every element and chat step in this scenario.

    1. 01
      <scenario>

      Names and versions the workflow.

      Writing example ↗
    2. 02
      <inputs>

      Declares input values.

      Writing example ↗
    3. 03
      <input>name

      Requires a supplied value.

      Writing example ↗
    4. 04
      <input>draft_id

      Provides an optional value.

      Writing example ↗
    5. 05
      <systemPrompt>

      Sets the child's instructions.

      Writing example ↗
    6. 06
      <steps>

      Orders the chat turns.

      Writing example ↗
    7. 07
      <run>

      Invokes a fresh saved child scenario.

      Writing example ↗
    8. 08
      <input>name

      Binds a named operation or child input.

      Writing example ↗
    9. 09
      <input>draft_id

      Binds a named operation or child input.

      Writing example ↗
    10. 10
      <if>

      Checks real workspace state or an input value.

      Writing example ↗
    11. 11
      <then>

      Runs when the condition matches.

      Writing example ↗
    12. 12
      <run>

      Invokes a fresh saved child scenario.

      Writing example ↗
    13. 13
      <else>

      Runs when the condition does not match.

      Writing example ↗
    14. 14
      <result>

      Returns structured JSON data.

      Writing example ↗
    15. 15
      <field>status

      Binds one returned field.

      Writing example ↗
    16. 16
      <field>message

      Binds one returned field.

      Writing example ↗
    17. 17
      <exit>

      Returns the output unchanged.

      Writing example ↗