omt-setup

Files (1)

• SKILL.md

SKILL.md (first lines)

> **TIL_PATH**: All `${TIL_PATH}/...` references below resolve to the vault's configured TIL path (injected at SessionStart). Bash expands `${TIL_PATH}` automatically. For `Read`/`Edit`/`Glob`/`Write` tools, substitute the resolved value before passing it as an argument (e.g. `${TIL_PATH}/SCHEMA.md` → `40-Resources/til/SCHEMA.md`). Default `til` when not injected; call MCP `til_get_path` if you need the current value.

# OMT Setup Skill

Manage oh-my-til vault assets and configuration. Operates via subcommands.

## Subcommands

### `/omt-setup` (no arguments)

1. Seed `${TIL_PATH}/SCHEMA.md` if missing (idempotent — see below)
2. Read `oh-my-til.json`, display current configuration + subcommand guide:
  - `deploy` — GitHub Pages deployment configuration

### `/omt-setup deploy`

Configure GitHub Pages deployment:
1. Check for `.git/` (if not found, notify and exit)
2. Check `.github/workflows/deploy-til.yml` (if exists, ask whether modification is needed)
3. Configure deploy section in `oh-my-til.json` (title, subtitle, GitHub URL)
4. Generate workflow YAML
5. Show completion guide (Settings → Pages → select GitHub Actions, commit & push commands)

## SCHEMA.md Seeding (idempotent)

`${TIL_PATH}/SCHEMA.md` is the single source of TIL conventions, read by `/save`, `/til`, and `/til-lint` at runtime. Skills fall back to built-in defaults when missing, but seeding it once aligns the whole vault.

Seeding rules:

1. Use `Read` to check `${TIL_PATH}/SCHEMA.md` (substitute the resolved value before calling Read). **If exists → skip silently** (preserves user customization).
2. If missing, seed via the `Bash` tool (Bash expands both `${CLAUDE_PLUGIN_ROOT}` and `${TIL_PATH}`; `Read`/`Edit` cannot):

   ```bash
   mkdir -p "${TIL_PATH}" && cp "${CLAUDE_PLUGIN_ROOT}/vault-assets/til-schema-template.md" "${TIL_PATH}/SCHEMA.md"
   ```

   In development without `CLAUDE_PLUGIN_ROOT`, substitute the repo root path.
3. Notify the user once: "Seeded `${TIL_PATH}/SCHEMA.md`. Customize freely — `/omt-setup` will not overwrite it."

For categories with crowded TIL collections (10+ files), suggest creating `${TIL_PATH}/{category}/MOC.md` (curated map). Do not auto-create — MOCs are user-curated entry points.

## Rules

- Preserve existing settings in `oh-my-til.json`, only add/modify the relevant section
- **Preserve `${TIL_PATH}/SCHEMA.md` if it exists** (Read → skip; never overwrite user customization)
- Do not commit (only show the user the commands)

From SongYunSeop/oh-my-til, MIT.

More from SongYunSeop/oh-my-til