open-prose_skill

This skill interprets prose commands, routes to the OpenProse VM, and orchestrates multi-agent workflows for .prose programs.

688

GitHub Stars

4

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openprose/prose --skill open-prose

  • compiler.md80.2 KB
  • help.md5.9 KB
  • prose.md35.1 KB
  • SKILL.md13.6 KB

Overview

This skill implements OpenProse: a single, unified handler for every prose command and .prose program. It activates automatically on any prose command, when a .prose file is referenced, or when a user asks to orchestrate multi-agent workflows. The skill interprets intent, loads the VM spec and appropriate state backends, and runs or validates programs as requested.

How this skill works

On activation the skill loads the OpenProse VM specification and the default filesystem state unless the user requests another state mode. It routes specific prose commands (run, compile, update, help, examples, etc.) to the appropriate behavior: fetching remote programs, validating with the compiler, migrating workspace structure, or executing sessions as VM-driven tasks. For remote or registry references it resolves URLs or handle/slug shorthand, fetches content, and then executes under the same VM semantics.

When to use it

  • Anytime you type a prose command (prose run, prose compile, prose update, prose help, etc.).
  • When you want to run or validate a local .prose file or a remote .prose program by URL or registry reference.
  • When orchestrating multiple AI agents or creating reusable multi-agent workflows.
  • When you need workspace migration or to upgrade legacy .prose structures with prose update.
  • When you want examples run or inspected from the bundled examples/ directory.

Best practices

  • Start runs with the default filesystem state for complex programs; switch to in-context for short, ephemeral sessions.
  • Only load the compiler documentation when explicitly compiling or validating to avoid ballooning context.
  • Use the guidance patterns and antipatterns when authoring new .prose files to improve robustness.
  • Prefer registry shorthand or direct URLs for reproducible remote program execution.
  • When using postgres state, supply a dedicated, limited-privilege connection string and verify connectivity before switching modes.

Example use cases

  • Run a local program: prose run examples/01-hello-world.prose to test basic agent interactions.
  • Execute a registry program: prose run alice/code-review to fetch and run a shared workflow.
  • Compile and validate a program before running: prose compile my-workflow.prose to catch mistakes early.
  • Migrate an older workspace: prose update to rename legacy folders and provision .prose/agents/.
  • Spin up multi-agent orchestration for a pipeline using examples like 16-parallel-reviews.prose or 21-pipeline-operations.prose.

FAQ

Inputs starting with http:// or https:// are fetched directly; handles or paths resolve to https://p.prose.md/{path}; @ prefixes are stripped; otherwise treat as a local file.

When should I use sqlite or postgres state?

Use sqlite for local, queryable state and atomic transactions; use postgres for concurrent, team-shared state but verify credentials and connectivity first.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational