prose
OpenProse VM skill pack. Activate on any `prose` command, .prose files, or OpenProse mentions; orchestrates multi-agent workflows.
68
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
40%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description relies heavily on product-specific jargon ('OpenProse VM', 'multi-agent workflows') without explaining what concrete value it provides to users. While it includes activation triggers, it fails to describe specific capabilities or use cases that would help Claude understand when this skill is genuinely appropriate versus other workflow tools.
Suggestions
Replace 'orchestrates multi-agent workflows' with specific concrete actions (e.g., 'coordinates document editing, code review, and content generation across multiple agents')
Add natural language trigger terms that describe user intent (e.g., 'Use when users need to coordinate complex tasks, run prose scripts, or manage multi-step content workflows')
Explain what OpenProse actually does in plain language so Claude can match it to user requests that don't explicitly mention 'OpenProse'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'orchestrates multi-agent workflows' without specifying concrete actions. It doesn't explain what the skill actually does beyond abstract terminology. | 1 / 3 |
Completeness | Has a 'when' clause ('Activate on any prose command...') but the 'what' is extremely weak - 'orchestrates multi-agent workflows' doesn't explain what the skill actually accomplishes for the user. | 2 / 3 |
Trigger Term Quality | Includes some trigger terms ('prose command', '.prose files', 'OpenProse mentions') but these are technical/product-specific rather than natural user language. Missing common variations of what users might actually say. | 2 / 3 |
Distinctiveness Conflict Risk | The specific triggers (.prose files, OpenProse) provide some distinctiveness, but 'multi-agent workflows' is generic enough to potentially overlap with other orchestration or automation skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that effectively guides Claude through a complex multi-file system. The command routing, file location tables, and conditional loading instructions are clear and actionable. Minor verbosity in the introductory framing and some redundant explanations of file locations prevent a perfect conciseness score, but overall the skill is production-ready.
Suggestions
Trim the philosophical opening paragraph ('LLMs are simulators...') to a single sentence - Claude doesn't need this explanation to execute the skill.
Consolidate the two 'File Locations' and 'Core Documentation' tables which have overlapping information about the same files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains useful information but includes some unnecessary verbosity, particularly the philosophical framing about 'simulation with sufficient fidelity is implementation' and repeated explanations of file locations. The tables are efficient, but some sections could be tightened. | 2 / 3 |
Actionability | Provides concrete command routing tables, specific file paths, executable bash commands for PostgreSQL setup, clear migration steps with exact file format conversions, and copy-paste ready Docker commands. The guidance is specific and actionable throughout. | 3 / 3 |
Workflow Clarity | Multi-step processes like migration and PostgreSQL setup have clear numbered sequences with explicit validation checkpoints (e.g., 'verify connectivity' before loading state backend, 'Only after successful connection check'). The command routing table provides unambiguous decision paths. | 3 / 3 |
Progressive Disclosure | Excellent structure with clear overview sections and well-signaled one-level-deep references to companion files (prose.md, compiler.md, state/*.md, guidance/*.md). The 'When to Load' column explicitly guides when to pull in additional context, preventing unnecessary loading. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.