prose-install
Install OpenProse for AIWG when not found. Tries `npx skills add`, falls back to git clone, then saves the resolved path to .aiwg/config.json.
What this skill does
# Prose Install Skill
You install OpenProse for AIWG use when `/prose-detect` reports no installation is found.
## Triggers
- Invoked by `/prose-detect` when all detection signals fail
- "install prose" / "install openprose"
- "prose install"
- "set up prose"
## Behavior
### Step 1: Confirm with User
Before installing, ask:
```
OpenProse is not installed. Install it to ~/.aiwg/prose/ so AIWG prose skills can use it?
Primary method: npx skills add openprose/prose
Fallback method: git clone https://github.com/openprose/prose ~/.aiwg/prose
[Y/n]
```
If the user declines, stop and report:
```
Installation cancelled. Set PROSE_ROOT to an existing OpenProse installation to proceed.
```
### Step 2: Try Primary Method
```bash
npx skills add openprose/prose --target ~/.aiwg/prose
```
If this succeeds and `~/.aiwg/prose/skills/open-prose/prose.md` exists, proceed to Step 4.
### Step 3: Fallback — git clone
If npx fails (not available or package not found):
```bash
git clone --depth=1 https://github.com/openprose/prose.git ~/.aiwg/prose
```
### Step 4: Validate Installation
Check that required files are present:
```bash
ls ~/.aiwg/prose/skills/open-prose/prose.md
ls ~/.aiwg/prose/skills/open-prose/forme.md
```
If either is missing, report failure:
```
Installation failed: prose.md or forme.md not found at ~/.aiwg/prose/skills/open-prose/.
Try cloning manually: git clone https://github.com/openprose/prose.git ~/.aiwg/prose
```
### Step 5: Save to Config
Write the resolved path to `.aiwg/config.json`:
```json
{
"prose": {
"path": "~/.aiwg/prose/skills/open-prose",
"installedVia": "npx|git-clone",
"installedAt": "2026-04-02T00:00:00Z"
}
}
```
### Step 6: Report Success
```markdown
## OpenProse Installed
**Location**: ~/.aiwg/prose/skills/open-prose
**Method**: npx skills add | git clone
**prose.md**: present
**forme.md**: present
**Config saved**: .aiwg/config.json → prose.path
All prose-integration skills are now ready to use.
```
## Updating an Existing Installation
If OpenProse is already installed and the user wants to update:
```bash
cd ~/.aiwg/prose && git pull origin main
```
Or use `/prose-setup` which handles both install and update.
## Model
This skill runs on **Haiku** — it's confirmation prompts and shell commands.
## References
- @$AIWG_ROOT/agentic/code/addons/prose-integration/README.md — prose-integration addon overview
- @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/human-authorization.md — Explicit user confirmation required before installing
- @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/research-before-decision.md — Validate installation after each method before declaring success
- @$AIWG_ROOT/docs/cli-reference.md — CLI reference for AIWG addon configuration
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.