diff --git a/skills/objectstack-platform/SKILL.md b/skills/objectstack-platform/SKILL.md
index a9bf7acd62d..3a85ad34d1a 100644
--- a/skills/objectstack-platform/SKILL.md
+++ b/skills/objectstack-platform/SKILL.md
@@ -188,16 +188,18 @@ what the platform owns.
 
 `blank` is the only template `create-objectstack` offers, and it is the default:
 
-- Bundled with `create-objectstack` — works offline, no network fetch
-- One example object, and `requires: ['automation']` plus the three generic
-  connector executors in `plugins:`. The memory driver and the Hono server are
-  NOT in the file — the CLI auto-registers both at boot
+- Bundled with `create-objectstack` — no network fetch
+- One example object; `requires: ['automation', 'triggers']` plus the three
+  generic connector executors in `plugins:`; and the seven generator barrels
+  (`objects`, `views`, `actions`, `flows`, `dashboards`, `apps`, `skills`),
+  each `src/*/index.ts` handed to the stack key of its name through
+  `exportsOf` — the scaffolded `AGENTS.md` says how to add to them. The
+  memory driver and the Hono server are NOT in the file — the CLI
+  auto-registers both at boot
 - A clean slate to extend with the metadata this skill describes
 
-The five remote content templates (`todo`, `compliance`, `content`,
-`contracts`, `procurement`) are **retired** — delisted from the marketplace and
-no longer maintained. Do not recommend them; asking for one by name is refused.
-Build domain metadata on top of `blank` instead.
+The five retired remote templates (`todo`, `compliance`, `content`,
+`contracts`, `procurement`) are refused by name.
 
 → Moved verbatim to [references/bootstrap.md](./references/bootstrap.md) § Scaffolding Command.
 
@@ -369,7 +371,7 @@ token through the `CAPABILITY_PROVIDERS` registry in
 | `audit` `email` `sharing` `approvals` `webhooks` | `@objectstack/plugin-` + the token |
 | `pinyin-search` | `@objectstack/plugin-pinyin-search` |
 | `mcp` | `@objectstack/mcp` |
-| `triggers` | `@objectstack/trigger-record-change`, plus `trigger-schedule` and `trigger-api`. **Pair it with `job`** — schedule and time-relative triggers run on the job service |
+| `triggers` | `@objectstack/trigger-record-change`, plus `trigger-schedule` and `trigger-api` |
 
 The tokens in `PLATFORM_CAPABILITY_TOKENS` not in that map do not resolve
 through it: