prose

Coordinate multi-agent sessions and manage execution state in OpenProse.

1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/seasonmac/Full-Scene-Agents --skill prose-seasonmac
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prose
Source: https://github.com/seasonmac/Full-Scene-Agents/tree/main/openclaw/extensions/open-prose/skills/prose
Command: npx skills add https://github.com/seasonmac/Full-Scene-Agents --skill prose-seasonmac

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenProse provides a unified entry point to activate and orchestrate the OpenProse VM, enabling teams to coordinate multi-agent sessions, route commands, and track execution state from a single interface.

Core Features & Use Cases

  • Unified VM activation and command routing for prose commands, with automatic session spawning via the Task tool.
  • Modular agent composition, imports, and blocks to build reusable workflows across projects.
  • Robust state management and resumption options across filesystem, in-context, and database backends for long-running tasks.
  • Use cases include end-to-end content pipelines, code reviews, and production workflows with auditable traces.

Quick Start

Run a minimal OpenProse program to spawn a session and observe its output.

Frequently Asked Questions about prose

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

FAQPage Schema
How do I coordinate multi-agent sessions for long-running workflows?

Multi-agent session coordination is handled by activating a unified VM that routes commands, spawns sessions via the Task tool, and tracks execution state for long-running workflows. It manages orchestration from a single interface to ensure robust execution.

What is the best way to persist execution state across multiple agent runs?

Persisting execution state across agent runs is supported through robust state management options spanning filesystem, in-context, and database backends. This enables long-running tasks to pause and resume without losing execution context or workflow progress.

Can I build reusable workflows with modular agent composition?

Reusable workflows are built using modular agent composition, imports, and blocks. This allows teams to construct end-to-end content pipelines and code review processes that can be imported and reused across different projects.

Does multi-agent orchestration support resuming interrupted long-running tasks?

Multi-agent orchestration supports resuming interrupted long-running tasks through its robust state management across filesystem, in-context, and database backends. This provides auditable traces and ensures execution state persists across runs.

How do I route commands to spawned agents in an orchestrated workflow?

Command routing to spawned agents is managed by the unified VM activation interface, which automatically spawns sessions via the Task tool. This routes prose commands to the appropriate agents within the orchestrated workflow.

Why does my multi-agent workflow need a unified VM for session orchestration?

A unified VM is needed for session orchestration to provide a single entry point for routing commands, spawning sessions, and tracking execution state. Without it, coordinating multiple agents across long-running workflows lacks centralized state management and auditable traces.