observal registry prompt
Manage reusable prompt templates in the Registry. Prompts can be submitted, listed, rendered, edited, archived, restored, transferred, and shared with co-authors. Standalone prompt installation has been removed; attach prompts to agents instead.
Commands
submit
Submit a prompt or save a draft
list
List approved visible prompts
my
List your prompts across all statuses
show
Show one prompt and its template
render
Render a prompt with variables
edit
Edit a draft, pending, or rejected prompt
archive
Archive an approved prompt
unarchive
Restore an archived prompt
transfer-owner
Transfer ownership
co-authors
List, add, or remove co-authors
All structured commands support table and JSON output.
Submit
observal registry prompt submit \
--name review \
--description "Review code" \
--category code-review \
--template "Review {{code}}" \
--output json
observal registry prompt submit --from-file prompt.json --output json
observal registry prompt submit --submit acme/review --output jsonJSON mode never prompts. A plain template file requires explicit name, description, and category options. A JSON file may contain the complete payload.
Valid categories are system-prompt, code-review, code-generation, testing, documentation, debugging, and general.
List and show
Row numbers are scoped to the latest Prompt list. Empty Prompt lists clear previous Prompt row references. Human output escapes template text so bracketed content is rendered literally.
Render
Every variable must use key=value syntax with a non-empty key. JSON returns the direct server result. Human output prints the rendered prompt as literal text.
Edit
Invalid categories, versions, files, and edit-lock conflicts preserve their shared error category and stable exit code.
Agent usage
Prompts are agent components rather than standalone harness installations:
Related
observal registry: complete Registry referenceobserval agent: compose and publish agents
Last updated
Was this helpful?