Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub Β· AI
Prose
OpenProse VM skill pack. Activate on any `prose` command, .prose files, or OpenProse mentions; orchestrates multi-agent workflows.
skill openclawclawhub Free
OpenProse VM skill pack. Activate on any `prose` command, .prose files, or OpenProse mentions; orchestrates multi-agent workflows.
β¬ 0 downloads β
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, alt-borges.md, alts/arabian-nights.md, alts/borges.md, alts/folk.md, alts/homer.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 0.1.0
Provenance
- Publisher
- mondilo1
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
OpenProse Skill
OpenProse is a programming language for AI sessions. LLMs are simulatorsβwhen given a detailed system description, they don't just describe it, they simulate it. The prose.md specification describes a virtual machine with enough fidelity that a Prose Complete system reading it becomes that VM. Simulation with sufficient fidelity is implementation. You are the Prose Complete system.
Moltbot Runtime Mapping
Task tool in the upstream spec == Moltbot sessions_spawn File I/O == Moltbot read/write Remote fetch == Moltbot web_fetch (or exec with curl when POST is required)
When to Activate
Activate this skill when the user: Uses ANY prose command (e.g., prose boot, prose run, prose compile, prose update, prose help, etc.) Asks to run a .prose file Mentions "OpenProse" or "prose program" Wants to orchestrate multiple AI agents from a script Has a file with session "..." or agent name: syntax Wants to create a reusable workflow
Command Routing
When a user invokes prose <command>, intelligently route based on intent: CommandActionprose helpLoad help.md, guide user to what they needprose run <file>Load VM (prose.md + state backend), execute the programprose run handle/slugFetch from registry, then execute (see Remote Programs below)prose compile <file>Load compiler.md, validate the programprose updateRun migration (see Migration section below)prose examplesShow or run example programs from examples/OtherIntelligently interpret based on context
Important: Single Skill
There is only ONE skill: open-prose. There are NO separate skills like prose-run, prose-compile, or prose-boot. All prose commands route through this single skill.
Resolving Example References
Examples are bundled in examples/ (same directory as this file). When users reference examples by name (e.g., "run the gastown example"): Read examples/ to list available files Match by partial name, keyword, or number Run with: prose run examples/28-gas-town.prose Common examples by keyword: KeywordFilehello, hello worldexamples/01-hello-world.prosegas town, gastownexamples/28-gas-town.prosecaptain, chairexamples/29-captains-chair.proseforge, browserexamples/37-the-forge.proseparallelexamples/16-parallel-reviews.prosepipelineexamples/21-pipeline-operations.proseerror, retryexamples/22-error-handling.prose
Remote Programs
You can run any .prose program from a URL or registry reference: # Direct URL β any fetchable URL works prose run https://raw.githubusercontent.com/openprose/prose/main/skills/open-prose/examples/48-habit-miner.prose # Registry shorthand β handle/slug resolves to p.prose.md prose run irl-danb/habit-miner prose run alice/code-review Resolution rules: InputResolutionStarts with http:// or https://Fetch directly from URLContains / but no protocolResolve to https://p.prose.md/{path}OtherwiseTreat as local file path Steps for remote programs: Apply resolution rules above Fetch the .prose content Load the VM and execute as normal This same resolution applies to use statements inside .prose files: use "https://example.com/my-program.prose" # Direct URL use "alice/research" as research # Registry shorthand
File Locations
Do NOT search for OpenProse documentation files. All skill files are co-located with this SKILL.md file: FileLocationPurposeprose.mdSame directory as this fileVM semantics (load to run programs)help.mdSame directory as this fileHelp, FAQs, onboarding (load for prose help)state/filesystem.mdSame directory as this fileFile-based state (default, load with VM)state/in-context.mdSame directory as this fileIn-context state (on request)state/sqlite.mdSame directory as this fileSQLite state (experimental, on request)state/postgres.mdSame directory as this filePostgreSQL state (experimental, on request)compiler.mdSame directory as this fileCompiler/validator (load only on request)guidance/patterns.mdSame directory as this fileBest practices (load when writing .prose)guidance/antipatterns.mdSame directory as this fileWhat to avoid (load when writing .prose)examples/Same directory as this file37 example programs User workspace files (these ARE in the user's project): File/DirectoryLocationPurpose.prose/.envUser's working directoryConfig (key=value format).prose/runs/User's working directoryRuntime state for file-based mode.prose/agents/User's working directoryProject-scoped persistent agents*.prose filesUser's projectUser-created programs to execute User-level files (in user's home directory, shared across all projects): File/DirectoryLocationPurpose~/.prose/agents/User's home dirUser-scoped persistent agents (cross-project) When you need to read prose.md or compiler.md, read them from the same directory where you found this SKILL.md file. Never search the user's workspace for these files.
Core Documentation
FilePurposeWhen to Loadprose.mdVM / InterpreterAlways load to run programsstate/filesystem.mdFile-based stateLoad with VM (default)state/in-context.mdIn-context stateOnly if user requests --in-context or says "use in-context state"state/sqlite.mdSQLite state (experimental)Only if user requests --state=sqlite (requires sqlite3 CLI)state/postgres.mdPostgreSQL state (experimental)Only if user requests --state=postgres (requires psql + PostgreSQL)compiler.mdCompiler / ValidatorOnly when user asks to compile or validateguidance/patterns.mdBest practicesLoad when writing new .prose filesguidance/antipatterns.mdWhat to avoidLoad when writing new .prose files
Authoring Guidance
When the user asks you to write or create a new .prose file, load the guidance files: guidance/patterns.md β Proven patterns for robust, efficient programs guidance/antipatterns.md β Common mistakes to avoid Do not load these when running or compilingβthey're for authoring only.
State Modes
OpenProse supports three state management approaches: ModeWhen to UseState Locationfilesystem (default)Complex programs, resumption needed, debugging.prose/runs/{id}/ filesin-contextSimple programs (<30 statements), no persistence neededConversation historysqlite (experimental)Queryable state, atomic transactions, flexible schema.prose/runs/{id}/state.dbpostgres (experimental)True concurrent writes, external integrations, team collaborationPostgreSQL database Default behavior: When loading prose.md, also load state/filesystem.md. This is the recommended mode for most programs. Switching modes: If the user says "use in-context state" or passes --in-context, load state/in-context.md instead. Experimental SQLite mode: If the user passes --state=sqlite or says "use sqlite state", load state/sqlite.md. This mode requires sqlite3 CLI to be installed (pre-installed on macOS, available via package managers on Linux/Windows). If sqlite3 is unavailable, warn the user and fall back to filesystem state. Experimental PostgreSQL mode: If the user passes --state=postgres or says "use postgres state": β οΈ Security Note: Database credentials in OPENPROSE_POSTGRES_URL are passed to subagent sessions and visible in logs. Advise users to use a dedicated database with limited-privilege credentials. See state/postgres.md for secure setup guidance. Check for connection configuration first: # Check .prose/.env for OPENPROSE_POSTGRES_URL cat .prose/.env 2>/dev/null | grep OPENPROSE_POSTGRES_URL # Or check environment variable echo $OPENPROSE_POSTGRES_URL If connection string exists, verify connectivity: psql "$OPENPROSE_POSTGRES_URL" -c "SELECT 1" 2>&1 If not configured or connection fails, advise the user: β οΈ PostgreSQL state requires a connection URL. To configure: 1. Set up a PostgreSQL database (Docker, local, or cloud) 2. Add connection string to .prose/.env: echo "OPENPROSE_POSTGRES_URL=postgresql://user:pass@localhost:5432/prose" >> .prose/.env Quick Docker setup: docker run -d --name prose-pg -e POSTGRES_DB=prose -e POSTGRES_HOST_AUTH_METHOD=trust -p 5432:5432 postgres:16 echo "OPENPROSE_POSTGRES_URL=postgresql://postgres@localhost:5432/prose" >> .prose/.env See state/postgres.md for detailed setup options. Only after successful connection check, load state/postgres.md This mode requires both psql CLI and a running PostgreSQL server. If either is unavailable, warn and offer fallback to filesystem state. Context warning: compiler.md is large. Only load it when the user explicitly requests compilation or validation. After compiling, recommend /compact or a new session before runningβdon't keep both docs in context.
Examples
The examples/ directory contains 37 example programs: 01-08: Basics (hello world, research, code review, debugging) 09-12: Agents and skills 13-15: Variables and composition 16-19: Parallel execution 20-21: Loops and pipelines 22-23: Error handling 24-27: Advanced (choice, conditionals, blocks, interpolation) 28: Gas Town (multi-agent orchestration) 29-31: Captain's chair pattern (persistent orchestrator) 33-36: Production workflows (PR auto-fix, content pipeline, feature factory, bug hunter) 37: The Forge (build a browser from scratch) Start with 01-hello-world.prose or try 37-the-forge.prose to watch AI build a web browser.
Execution
When first invoking the OpenProse VM in a session, display this banner: βββββββββββββββββββββββββββββββββββββββ β β OpenProse VM β β β A new kind of computer β βββββββββββββββββββββββββββββββββββββββ To execute a .prose file, you become the OpenProse VM: Read prose.md β this document defines how you embody the VM You ARE the VM β your conversation is its memory, your tools are its instructions Spawn sessions β each session statement triggers a Task tool call Narrate state β use the narration protocol to track execution ([Position], [Binding], [Success], etc.) Evaluate intelligently β **...** markers require your judgment
Help & FAQs
For syntax reference, FAQs, and getting started guidance, load help.md.
Migration (prose update)
When a user invokes prose update, check for legacy file structures and migrate them to the current format.
Legacy Paths to Check
Legacy PathCurrent PathNotes.prose/state.json.prose/.envConvert JSON to key=value format.prose/execution/.prose/runs/Rename directory
Migration Steps
Check for .prose/state.json If exists, read the JSON content Convert to .env format: {"OPENPROSE_TELEMETRY": "enabled", "USER_ID": "user-xxx", "SESSION_ID": "sess-xxx"} becomes: OPENPROSE_TELEMETRY=enabled USER_ID=user-xxx SESSION_ID=sess-xxx Write to .prose/.env Delete .prose/state.json Check for .prose/execution/ If exists, rename to .prose/runs/ The internal structure of run directories may also have changed; migration of individual run state is best-effort Create .prose/agents/ if missing This is a new directory for project-scoped persistent agents
Migration Output
π Migrating OpenProse workspace... β Converted .prose/state.json β .prose/.env β Renamed .prose/execution/ β .prose/runs/ β Created .prose/agents/ β Migration complete. Your workspace is up to date. If no legacy files are found: β Workspace already up to date. No migration needed.
Skill File References (for maintainers)
These documentation files were renamed in the skill itself (not user workspace): Legacy NameCurrent Namedocs.mdcompiler.mdpatterns.mdguidance/patterns.mdantipatterns.mdguidance/antipatterns.md If you encounter references to the old names in user prompts or external docs, map them to the current paths.
Category context
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
6 Docs
- SKILL.md
- alt-borges.md
- alts/arabian-nights.md
- alts/borges.md
- alts/folk.md
- alts/homer.md