---
name: skills-hub-curator
description: Use when creating, importing, promoting, rolling back, or auditing Jeevan repo-local skills and the Skills Hub registry, including sandbox state, rollback markers, and missing skill coverage.
---

# Skills Hub Curator

Use this skill when the work is about Jeevan's own skill system: building the first skill pack, checking what is live, preparing an import, promoting a skill, or hardening the import workflow.

## Read First

- `apps/api/src/skills-hub.js`
- `apps/api/src/server.js`
- `apps/web/index.html`
- `projects/control-plane/data/team.json`
- `skills/`

For the operating map and current limitations, read [references/skills-hub-map.md](references/skills-hub-map.md).

## Main Jobs

1. Keep the repo-local `skills/` directory populated with real skills.
2. Make sure Skills Hub reads meaningful local registry entries.
3. Preserve sandbox-first promotion and rollback behavior.
4. Call out where the implementation is still manual or incomplete.

## Workflow

### 1. Check what already exists

- Inspect `skills/` first.
- Then inspect `summarizeSkillsHub` behavior in `apps/api/src/skills-hub.js`.
- Treat the repo-local skill folders as the live registry source.

### 2. Build or update skills

- Create narrowly scoped skills with reusable workflows.
- Keep `SKILL.md` concise and specific.
- Add `references/` files only when they help the skill stay small and reusable.
- Avoid extra files such as README or changelog documents.

### 3. Validate import behavior

- Local-path imports are the only fully implemented import path today.
- Git URL imports currently stop at a sandbox marker and `remote-source.json`.
- Do not describe Git imports as complete unless clone/fetch behavior has been added.

### 4. Preserve promotion safety

- Promotion should remain sandbox first.
- Rollback markers should exist before a live overwrite is possible.
- If a change would bypass rollback protection, treat it as a regression.

### 5. Confirm dashboard visibility

- Check Skills Hub cards in `apps/web/index.html`.
- A skill is not operationally useful if the files exist but the dashboard still shows an empty registry because of naming or path mistakes.

## Guardrails

- Prefer repo-local, project-aware skills over generic placeholder skills.
- Keep skill names stable and hyphenated.
- Do not add fake sample registry entries; create actual usable skills instead.
- Call out unsupported Git import behavior plainly.

## Outputs

- New or improved skills under `skills/`.
- A short note on local registry count, imports, promoted items, and rollback readiness.
- A precise statement when the hub is “present but incomplete.”