Craft and stage a C# tool and XML scenario

Use this scenario

Run

Run addon_craft 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": "addon_craft",
  "inputs": {
    "name": "your name",
    "request": "your request"
  }
}

addon_craft2 INPUTS / 1 TOOLS / 1 STEPS

Inputs

PARAMETERS

Input	Requirement	Default value
`name`	Required	`No default`
`request`	Required	`No default`

Agent instructions

SYSTEM PROMPT

Delegate separate C# and XML writers and an independent reviewer. The host stages exact sources in workspace Addons, enforces Ask/YOLO, compiles using a fixed project and requests an addon runtime restart. Never self-approve or claim generated behavior was tested.

Tool access

CAPABILITIES

addon_craft_operation — selected from this version's tool catalog.

Ordered steps

EXECUTION

01
BOUND OPERATION / HOST EXECUTED
addon_craft_operation
- name = {{name}}
- request = {{request}}
Save output as receipt.

Return to main

COPY EXIT

Return the exact staging/approval receipt.

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

Complete XML, including any embedded C#. Copy it without changing the file's contents.

XMLStructureInputsTools / C#StepsExit

<scenario schemaVersion="3" id="addon_craft" title="Craft and stage a C# tool and XML scenario">
  <inputs>
    <input name="name" required="true" />
    <input name="request" required="true" />
  </inputs>
  <systemPrompt>Delegate separate C# and XML writers and an independent reviewer. The host stages exact sources in workspace Addons, enforces Ask/YOLO, compiles using a fixed project and requests an addon runtime restart. Never self-approve or claim generated behavior was tested.</systemPrompt>
  <tools>
    <allow name="addon_craft_operation" />
  </tools>
  <steps>
    <tool name="addon_craft_operation" result="receipt">
      <input name="name" value="{{name}}" />
      <input name="request" value="{{request}}" />
    </tool>
  </steps>
  <exit mode="copy">Return the exact staging/approval receipt.</exit>
</scenario>

Download XML ↓

EVERY XML ELEMENT / IN FILE ORDER

Every part, briefly.

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

01
<scenario>
Names and versions the workflow.
Writing example ↗
02
<inputs>
Declares input values.
Writing example ↗
03
<input>name
Requires a supplied value.
Writing example ↗
04
<input>request
Requires a supplied value.
Writing example ↗
05
<systemPrompt>
Sets the child's instructions.
Writing example ↗
06
<tools>
Defines available capabilities.
Writing example ↗
07
<allow>addon_craft_operation
Grants an existing tool.
Writing example ↗
08
<steps>
Orders the chat turns.
Writing example ↗
09
<tool>addon_craft_operation
Executes a declared host operation.
Writing example ↗
10
<input>name
Binds a named operation or child input.
Writing example ↗
11
<input>request
Binds a named operation or child input.
Writing example ↗
12
<exit>
Returns the output unchanged.
Writing example ↗

Write a scenario, step by step ↗How sub-agents work ↗