---
title: RateRight Skill Catalog — README
created: 2026-05-06
created_by: claude-code-opsman (Wave 3.1 of upgrade plan)
status: live
related:
  - "[[../_Brain/README]]"
  - "[[_Log]]"
---

# RateRight Skill Catalog

Vault-scoped mirrors of the RateRight growth-engine skills. The user-level versions at `~/.claude/skills/<name>.md` remain CANONICAL for invocation (skills run from any working dir on Rocky's local). This vault directory is the **fixture + version-control surface** — for regression testing and discoverability.

## Naming convention

Single-word skill names matching `~/.claude/skills/<name>.md` filenames. No `rr-*` prefix.

## Structure per skill

```
<skill-name>/
  SKILL.md              ← mirrors user-level skill content
  fixtures/
    golden-output.md    ← expected output structure for regression
```

## Existing skills

| Skill | Trigger | Status | User-level path |
|---|---|---|---|
| `hunt` | `/hunt` | live | `~/.claude/skills/hunt.md` |
| `matchmaker` | `/matchmaker` | live | `~/.claude/skills/matchmaker.md` |
| `post` | `/post` | live | `~/.claude/skills/post.md` |
| `pulse` | `/pulse` | live | `~/.claude/skills/pulse.md` |

## Sync convention

When a skill is edited, **edit user-level first** (`~/.claude/skills/<name>.md` is canonical), then mirror to vault SKILL.md. Future automation: a sync script that detects user-level edits + auto-PRs vault mirror.

## Fixtures

Each skill's `fixtures/golden-output.md` describes the expected output STRUCTURE (column headers, row format, error patterns). RateRight skills query live data — we don't fix exact values. Fixtures are about format stability, not data values.

## Add/retire procedure

Same as LFCS lane:
1. Edit user-level skill at `~/.claude/skills/<name>.md`.
2. Mirror SKILL.md here.
3. Update fixtures if output structure changes.
4. Append `_Log.md` v-entry here with reason.
5. Append row to `_System/SKILLS.md` § Lane: 10_RateRight if new skill.