Skill rating
12 skills. The A–F grade combines safety (60%) and quality (40%); tests add a bonus. The rating refreshes automatically from open catalogs.
ManufacturingLogistics and warehouseProcurementQuality controlContact centreField serviceFinanceCustomer supportindustry shortcuts
| # | Grade | Skill | Score ▾ | Safety | Quality | Process | Tests | Popularity | Updated |
|---|---|---|---|---|---|---|---|---|---|
| 1 | A | Autonomously create, test, and optimize skills by detecting reusable patterns in your own work. Use when you notice repeated tool sequences, recurring code patterns across attempts, or insights that s | 100 | 92 | C | — | — | 7 h ago | |
| 2 | A | 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` / t | 100 | 88 | C | — | — | 7 h ago | |
| 3 | B | promoting-dev-to-mainAnalyzerGitHubSoftware developmentData and analyticsHuman-Agent-Society/CoralAgent Skills Use when preparing, reviewing, resolving conflicts for, or merging a CORAL release pull request from the long-lived dev branch into main. | 100 | 84 | D | — | — | 7 h ago | |
| 4 | B | creating-a-coral-taskGeneratorData and analyticsSoftware developmentHuman-Agent-Society/CoralAgent Skills Author a new CORAL task — the three pieces that must line up (`task.yaml`, `seed/`, a packaged `grader/`), the `coral init` → `coral validate` → smoke-test loop, and how to pick a grader pattern (stdo | 100 | 85 | F | — | — | 7 h ago | |
| 5 | B | 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/` conven | 95 | 92 | C | — | — | 7 h ago | |
| 6 | B | One-time machine setup after installing the `coral` CLI — register local agent runtimes as named bindings with `coral setup` / `coral setup agent`, validate them with `coral agents doctor` (incl. a li | 100 | 84 | C | — | — | 7 h ago | |
| 7 | B | Organize the shared notes directory when it becomes hard to navigate. Restructure within research/ and experiments/, deduplicate, update index.md. | 90 | 91 | C | — | — | 7 h ago | |
| 8 | B | Research the problem domain before coding. Web search for techniques, save raw sources, write structured findings, update the index. | 100 | 79 | D missing files | — | — | 7 h ago | |
| 9 | B | Add a new component to the CORAL framework itself — a new agent runtime under `coral/agent/builtin/` (claude_code/codex/cursor_agent style), a new CLI command in `coral/cli/`, a new bundled skill or s | 100 | 79 | D missing files | — | — | 7 h ago | |
| 10 | B | Verify and debug changes to CORAL itself — smallest reproduce loop per area (grader / daemon / CLI / hooks / manager / workspace / hub / template / config / web), where to look when something breaks ( | 100 | 79 | D missing files | — | — | 7 h ago | |
| 11 | C | Write a note to {shared_dir}/notes/ that future agents can actually act on. Use after every coral eval, when a heartbeat (reflect / consolidate / pivot) asks for a note, or when you discover a grader | 100 | 72 | D missing files | — | — | 7 h ago | |
| 12 | C | End-to-end recipe for adding a new task under `examples/` — the three pieces that have to line up (`task.yaml`, `seed/`, and `grader/`), what to put in each, the `TaskGrader` API surface, the `coral v | 100 | 72 | D missing files | — | — | 7 h ago |