reef

Coral Reef Dashboard

ARCHIVED — not a live skill. Moved out of skills/ so it is not discovered or exposed to users (Claude Code recursively registers every skills/<name>/SKILL.md; there is no frontmatter/naming flag to hide one in place). coral-reef development is paused. To re-enable: move this directory back to skills/reef/. Note the data dir (~/.claude/coral-reef/) still hardcodes ~/.claude and does not yet honor CLAUDE_CONFIG_DIR — fix that in the coral-reef server repo before re-enabling.

Launch the coral-reef dashboard. Handles installation, updates, builds, and startup automatically.

The runtime injects Base directory for this skill: which resolves to this skill's installed path. From there, the plugin root is two levels up, and coral-reef/ sits as a sibling directory.

Constants

REPO_URL = "https://github.com/kangig94/coral-reef"
REEF_DATA_DIR = ~/.claude/coral-reef/
REEF_PORT = 3100

Protocol

Step 1 — Resolve Paths

Derive the plugin root from the base directory injected by the framework:

PLUGIN_ROOT = resolve(base_directory, "../..")
REEF_DIR = resolve(PLUGIN_ROOT, "coral-reef")

Verify PLUGIN_ROOT contains package.json with "name": "coral" as a sanity check.

Step 2 — Ensure Data Directory

mkdir -p ~/.claude/coral-reef

This is coral-reef's permanent SQLite storage location, surviving /tmp reboots.

Step 3 — Clone or Update

Check if REEF_DIR exists:

• Not exists: git clone ${REPO_URL} ${REEF_DIR}
• Exists with .git/: cd ${REEF_DIR} && git pull --ff-only
• Exists without .git/: warn user and skip update (manual install)

Step 4 — Dependency Resolution

Detect the install layout by checking if this is a nested plugin install or a dev workspace:

# Read coral-reef's package.json
cd ${REEF_DIR}

Check if the coral dependency in package.json points to the correct location:

• Dev workspace layout (~/workspace/coral-reef sibling to ~/workspace/coral): The coral dependency should be "file:../coral". Leave as-is.