prose

Execute OpenProse .prose programs with a VM-style multi-agent orchestration model.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/nomad3/openclaw-k8s --skill prose-nomad3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prose
Source: https://github.com/nomad3/openclaw-k8s/tree/main/package/extensions/open-prose/skills/prose
Command: npx skills add https://github.com/nomad3/openclaw-k8s --skill prose-nomad3

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns OpenProse .prose programs into an executable virtual machine that can coordinate multi-agent workflows, manage state, and route commands like run and compile.

Core Features & Use Cases

  • Command-driven VM execution: Run, compile/validate, migrate workspaces, and browse bundled examples through a single entry skill.
  • Multi-agent orchestration: Define agents, spawn sessions, route tasks, and coordinate parallel work using OpenProse language constructs.
  • State management modes: Execute with filesystem state by default, or switch to in-context, SQLite, and experimental PostgreSQL state for different workflow scales.
  • Modular composition and reuse: Import programs (use statements), define reusable blocks, and share context between steps for robust pipelines.

Quick Start

Ask the AI to run your workflow by executing: prose run path/to/workflow.prose

Frequently Asked Questions about prose

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

FAQPage Schema
How do I orchestrate multi-agent workflows with state management?

Multi-agent orchestration is handled by running OpenProse .prose programs through a VM-style execution model that coordinates parallel agent sessions and manages state across iterative or parallel agent graphs.

What is the best way to compile and validate OpenProse programs?

Compiling and validating OpenProse programs is achieved by routing compile commands through the execution VM, which checks program constructs like agents, sessions, and blocks before running the workflow.

Does OpenProse support different state backends for workflow automation?

State management supports filesystem state by default, and can switch to in-context, SQLite, and experimental PostgreSQL backends to accommodate different workflow scales and execution requirements.

How do I execute a local .prose file from the command line?

Executing a local .prose file requires routing a run command to the VM semantics, which processes the YAML-defined activation and orchestrates the defined agents, sessions, and context passing.

Can I import reusable blocks and share context between workflow steps?

Importing reusable blocks and sharing context between steps is supported through OpenProse language constructs, allowing modular composition via use statements and robust pipeline construction.

What are the limitations of using in-context state for parallel agent graphs?

In-context state execution operates within the session's runtime memory, limiting scalability compared to filesystem or database state backends like SQLite and PostgreSQL for large parallel agent graphs.