reef

Solid

Launch the coral-reef dashboard (auto-install, build, and start)

AI & Automation 11 stars 3 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
36
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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 ```bash 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...

Details

Author
kangig94
Repository
kangig94/coral
Created
6 months ago
Last Updated
yesterday
Language
TypeScript
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Solid

developing-reef

REQUIRED before any non-test code change in Reef. Load this skill before modifying Reef runtime architecture, `App` state, tabs/panels, rendering code, input dispatch (`crates/reef-tui/src/input.rs`, any picker overlay, the commit textarea, any new text-input field), background work, git/file-tree/diff/graph loading, performance-sensitive paths, or when the user asks about "how Reef is structured", "render blocking", "heavy tasks", "new tab", "new feature architecture", "input handling", "text input", "picker", "PickerCore", "input_edit", or "project conventions". Do NOT start editing Reef source without loading this skill first — the architecture has non-obvious invariants (render-pure, async generation tokens, three-layer text-input stack) whose violation has been re-introduced and re-fixed across multiple PRs. Pair with `testing-reef` whenever adding or changing tests.

81 Updated today
Blushyes
AI & Automation Featured

running-coral-experiments

Run and manage CORAL experiments from the operator side — launch agents with `coral start` (dotlist overrides, model/count, tmux vs local), monitor with `coral status` / `coral log` / `coral show` / the web dashboard, and drive the loop with `coral resume` (inject instructions, fork from an attempt), `coral heartbeat` (tune reflection cadence), and `coral stop`. Use whenever the user wants to start a CORAL run, check on agents, read scores/leaderboard, steer or resume a run, diagnose agents that keep restarting or fail every eval, scale to more agents or islands, or stop a run. Deep references for steering/heartbeat tuning and scaling/troubleshooting live alongside this skill.

975 Updated 3 days ago
Human-Agent-Society
AI & Automation Featured

coral-quickstart

The fast path from zero to a running CORAL experiment — what CORAL is and when to reach for it, installing the `coral` CLI, registering a runtime with `coral setup`, and the `.coral_workspace/` convention for pointing CORAL at code you already have and want optimized. Use this whenever the user asks "what is coral", "should I use coral for this", wants to install or get coral set up, hits a "command not found" for coral or doesn't have it installed yet, or says "use coral to optimize / speed up / improve this code" and you need the end-to-end onboarding from install to a launched run. Hands off to `setting-up-coral` (runtime bindings), `creating-a-coral-task` (grader authoring), and `running-coral-experiments` (operating a run) for depth.

975 Updated 3 days ago
Human-Agent-Society