read-existing-content

Files (1)

• SKILL.md

SKILL.md (first lines)

# Read Existing Content

This is a **Routine** skill — a reliable, repeatable sequence of Actions. Follow the steps exactly. Minimize judgment — the process is fixed.

## Purpose

Answer requests like **"show me the content of lesson X in course Y"** or **"what does this topic say"** when the user refers to content by **title or admin URL**, not by UUID. This routine resolves the IDs and returns the real HTML **body** of the topic(s) — the flow that previously failed when reads returned no content.

Use this whenever someone wants to *see* existing content. (To change it afterwards, hand off to **`rewrite-lesson`** or **`update-course-content`**.)

## Process

### Step 1 — Resolve the reference to IDs

Run the **`resolve-content`** action with whatever the user gave you (course title, slug, admin/catalog URL, or UUID), plus an optional lesson/topic name:

```bash
node "${CLAUDE_PLUGIN_ROOT:+$CLAUDE_PLUGIN_ROOT/skills/actions/resolve-content/}resolve-content.js" --course="COURSE TITLE | slug | URL | UUID" [--lesson="LESSON NAME"] [--topic="TOPIC NAME"]
```

- If it returns `"resolved": true`, use `ids.courseId` (and any `ids.lessonId` / `ids.topics`).
- If it returns `candidates`, present them to the user and ask which one — **never guess a UUID**.
- If nothing matched, tell the user and offer to browse with `list-course-groups`.

### Step 2 — Read the actual content bodies

Run the **`get-full-content`** action with the resolved `courseId`. If a lesson was resolved, focus the tree on it:

```bash
node "${CLAUDE_PLUGIN_ROOT:+$CLAUDE_PLUGIN_ROOT/skills/actions/get-full-content/}get-full-content.js" --id=COURSE_UUID [--lesson=LESSON_UUID]
```

Use the `_tree` view to line up each topic's `id`, `title`, and `body`.

> Do **not** try to read content with `get-topic` or `get-topics-by-lesson` — those return metadata only, never the `body`.

### Step 3 — Present the content

Show the requested topic(s) with their titles and rendered/plain body. If the user asked about a specific lesson or topic, filter to it. Keep the topic `id`s handy in case the user next asks to edit — a follow-up edit goes through `update-course-content` (see `rewrite-lesson`), and existing content **is** editable via the API (do not defer to manual TI editing for a plain body change).

<HARD-GATE>
This routine is read-only. Do not modify, create, delete, or publish any content.
</HARD-GATE>

From thoughtindustries/ti-admin-plugin, MIT.

More from thoughtindustries/ti-admin-plugin