prose-detect
Locate an existing OpenProse installation using a prioritized signal chain — env var, AIWG config, AIWG-local install, project plugin manifest, user home directory, or global CLI. Returns the resolved PROSE_ROOT path. Does not install OpenProse; triggers prose-setup if no installation is found.
Best use case
prose-detect is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
It is a strong fit for teams already working in Codex.
Locate an existing OpenProse installation using a prioritized signal chain — env var, AIWG config, AIWG-local install, project plugin manifest, user home directory, or global CLI. Returns the resolved PROSE_ROOT path. Does not install OpenProse; triggers prose-setup if no installation is found.
Teams using prose-detect should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/prose-detect/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How prose-detect Compares
| Feature / Agent | prose-detect | Standard Approach |
|---|---|---|
| Platform Support | Codex | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Locate an existing OpenProse installation using a prioritized signal chain — env var, AIWG config, AIWG-local install, project plugin manifest, user home directory, or global CLI. Returns the resolved PROSE_ROOT path. Does not install OpenProse; triggers prose-setup if no installation is found.
Which AI agents support this skill?
This skill is designed for Codex.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
SKILL.md Source
# Prose Detect Skill
You locate an existing OpenProse installation by checking a priority-ordered list of signals. You return the resolved `PROSE_ROOT` path (pointing to `skills/open-prose/` inside the OpenProse repo), or report that no installation was found and suggest running `/prose-setup`.
All other prose-integration skills call this skill before operating — detection is centralized here so each skill doesn't re-implement discovery independently.
## Triggers
- "detect prose" / "find prose" / "locate openprose"
- "where is prose installed"
- "check if prose is available"
- "prose-detect" (direct invocation from other skills)
- Called automatically by prose-run, prose-reader, prose-validate, forme-manifest before execution
## Detection Protocol
Work through the following signals **in order**. Use the first one that resolves to a valid installation.
### Signal 1: Environment Variable
```bash
# Check PROSE_ROOT or AIWG_PROSE_ROOT
echo "$PROSE_ROOT"
echo "$AIWG_PROSE_ROOT"
```
If set, validate that `$PROSE_ROOT/prose.md` exists. If valid, use this path.
### Signal 2: AIWG Config File
```bash
# Check .aiwg/config.json for saved prose path
cat .aiwg/config.json 2>/dev/null | python3 -c "import sys,json; d=json.load(sys.stdin); print(d.get('prose',{}).get('path',''))" 2>/dev/null
```
If `prose.path` is set and `{prose.path}/prose.md` exists, use this path.
### Signal 3: AIWG-Local Install
```bash
# Check if AIWG installed Prose locally
ls ~/.aiwg/prose/skills/open-prose/prose.md 2>/dev/null
```
If exists, `PROSE_ROOT` = `~/.aiwg/prose/skills/open-prose`.
### Signal 4: Project Plugin Manifest
Walk CWD upward looking for `.claude-plugin/plugin.json` with OpenProse entry:
```bash
# Search CWD and ancestors for .claude-plugin/plugin.json
dir="$(pwd)"
while [ "$dir" != "/" ]; do
if [ -f "$dir/.claude-plugin/plugin.json" ]; then
# Check if it references open-prose
python3 -c "
import json, sys
with open('$dir/.claude-plugin/plugin.json') as f:
d = json.load(f)
# Plugin root is the directory containing .claude-plugin/
if d.get('name') == 'open-prose':
print('$dir/skills/open-prose')
" 2>/dev/null
break
fi
dir="$(dirname "$dir")"
done
```
If found, use the resolved path.
### Signal 5: User Home Directory
```bash
# Check if user has previously run Prose
ls ~/.prose/agents/ 2>/dev/null
```
If `~/.prose/agents/` exists, `PROSE_ROOT` is likely nearby. Check:
```bash
ls ~/.prose/skills/open-prose/prose.md 2>/dev/null
```
### Signal 6: Global CLI
```bash
# Check for global CLI install
which prose 2>/dev/null
```
If found, use `prose --root` or `prose info` to resolve the installation path.
### Signal 7: Not Found
If no signal resolves to a valid `PROSE_ROOT`, output:
```markdown
## OpenProse Not Found
No OpenProse installation was detected. Checked:
- $PROSE_ROOT / $AIWG_PROSE_ROOT environment variables
- .aiwg/config.json prose.path
- ~/.aiwg/prose/ (AIWG-local install)
- .claude-plugin/plugin.json in CWD and ancestors
- ~/.prose/ (user home)
- `prose` CLI on PATH
To install OpenProse, run:
```bash
/prose-setup
```
Or provide a custom path:
```bash
# Set env var
export PROSE_ROOT=/path/to/prose/skills/open-prose
# Or configure in .aiwg/config.json
{"prose": {"path": "/path/to/prose/skills/open-prose"}}
```
```
Do NOT install silently. Always confirm with the user before running `/prose-setup`.
## Validation
After resolving a candidate path, validate it by checking for required files:
```bash
# Minimum required files
ls "$PROSE_ROOT/prose.md"
ls "$PROSE_ROOT/forme.md"
```
If either file is missing, the path is invalid — continue to the next signal.
## Output
On success, output:
```markdown
## OpenProse Located
**PROSE_ROOT**: /path/to/prose/skills/open-prose
**Detected via**: [signal name — env var | aiwg-config | aiwg-local | plugin-manifest | user-home | cli]
**prose.md**: present
**forme.md**: present
Prose integration skills are ready to use.
```
Also set `PROSE_ROOT` in the session environment if the platform supports it.
## Caching
Once detected, save the resolved path to `.aiwg/config.json` so Signal 2 succeeds on future calls:
```json
{
"prose": {
"path": "/resolved/path/to/skills/open-prose",
"detectedVia": "aiwg-local",
"lastVerified": "2026-04-02T00:00:00Z"
}
}
```
Only write the cache if the detection succeeds and the path is validated.
## Model
This skill runs on **Haiku** — it's pure file-system checks and shell commands. No reasoning needed.
## Used By
All prose-integration skills call prose-detect as their first step:
- `/prose-reader`
- `/prose-run`
- `/prose-validate`
- `/forme-manifest`
## References
- @$AIWG_ROOT/agentic/code/addons/prose-integration/README.md — prose-integration addon overview
- @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/research-before-decision.md — Priority-ordered detection chain before deciding installation path
- @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/human-authorization.md — Never install silently; always confirm before running prose-setup
- @$AIWG_ROOT/docs/cli-reference.md — CLI reference for AIWG addon configurationRelated Skills
research-gap-detect
Build the mutual citation graph, find connected components, identify isolated clusters, and optionally search for bridge candidates and file gap issues. Automates the manual cluster analysis workflow.
prose-validate
Validate an OpenProse program file against Prose contract grammar without executing it — checks frontmatter, contract structure, service references, and strategy syntax
prose-setup
Clone or update the OpenProse repository to ensure AIWG prose tools hook into the latest version of the specification and examples
prose-run
Execute an OpenProse program within the current AIWG session, following the two-phase model (Forme wiring + Prose VM execution)
prose-reader
Read and parse an OpenProse program file, extracting its contract (requires, ensures, strategies, errors, invariants) and services into a structured representation
prose-install
Install OpenProse for AIWG use when no existing installation is found. Tries npx skills add first, falls back to git clone, then saves the resolved path to .aiwg/config.json.
flaky-detect
Identify flaky tests from CI history and test execution patterns. Use when debugging intermittent test failures, auditing test reliability, or improving CI stability.
ai-pattern-detection
Detects AI-generated writing patterns and suggests authentic alternatives. Auto-applies when reviewing content, editing documents, generating text, or when user mentions writing quality, AI detection, authenticity, or natural voice.
aiwg-orchestrate
Route structured artifact work to AIWG workflows via MCP with zero parent context cost
venv-manager
Create, manage, and validate Python virtual environments. Use for project isolation and dependency management.
pytest-runner
Execute Python tests with pytest, supporting fixtures, markers, coverage, and parallel execution. Use for Python test automation.
vitest-runner
Execute JavaScript/TypeScript tests with Vitest, supporting coverage, watch mode, and parallel execution. Use for JS/TS test automation.