A checklist with an embedded C# helper
A small CDATA example splits semicolon-separated items deterministically before the child formats a checklist. The embedded helper uses only in-memory text processing.
User-authored XML examples for Lilith V3. These are website-only recipes, not files bundled with the application. Each example targets this specific version.
Only scenarios introduced in V3 are listed. Earlier additions are available under their version tabs.
A small CDATA example splits semicolon-separated items deterministically before the child formats a checklist. The embedded helper uses only in-memory text processing.
Compare supplied options against explicit constraints, then hand a compact recommendation back to the main agent. It demonstrates the respond exit without external research.
Read the actual current time, choose priorities and produce a small time-boxed plan. This V3 example does not create timers, access the workspace or save the result.
Turn a topic and audience into a focused outline, a short draft and a final editorial pass. This text-only V3 example makes no web requests and writes no files.
No scenarios match this search.
These XML files are documentation downloads only. Reading or downloading one does not install it, execute it, or add it to the Lilith source archive.
Start with the bundled Scenarios directory from Lilith V3. Copy that matching catalog to a trusted editable folder and add your example XML alongside it. Keep the filename equal to its scenario ID.
Point LILITH_SCENARIOS_ROOT at that folder before starting Lilith. A custom root replaces the bundled catalog rather than merging with it, so keep the bundled files you still need, including greeting.xml for startup and scheduled greetings. Then ask Lilith to run the scenario by name and supply its required values.
Saved XML is trusted application content. Embedded C# executes with the host's permissions and requires the .NET SDK; it is not sandboxed. Workspace and scheduling operations keep their selected version's access and approval rules. Examples are authored against the documented contract; they are not live model execution guarantees.