@remixmate/cli 0.1.0 → 0.1.2

package/dist/registry.js

@@ -1,29 +1,21 @@
 /**
  * Skill registry — scan skills/ and load skill.json definitions.
  *
- * skill.json schema:
- *   { name, toolName, description, parameters, entry?, scriptPath? }
- *
- * `entry` is the dispatcher hint. Missing entry falls back to the legacy
- * top-level scriptPath, treated as { type:'python', scriptPath } so older
- * skills keep working without a touch.
+ * Validation and entry-normalization live in `skill-schema.ts` (shared with
+ * the build-time manifest generator and smoke test). A record that fails
+ * validation is skipped with a warning rather than crashing the whole CLI.
  */
 import { readdirSync, readFileSync, existsSync, statSync } from 'node:fs';
 import path from 'node:path';
 import { fileURLToPath } from 'node:url';
+import { normalizeEntry, validateSkillJson, } from './skill-schema.js';
 const __dirname = path.dirname(fileURLToPath(import.meta.url));
 export const SKILLS_DIR = path.resolve(__dirname, '..', 'skills');
-function normalizeEntry(raw) {
-    if (raw.entry)
-        return raw.entry;
-    if (raw.scriptPath)
-        return { type: 'python', scriptPath: raw.scriptPath };
-    return null;
-}
 function loadOne(skillDir) {
     const skillJsonPath = path.join(skillDir, 'skill.json');
     if (!existsSync(skillJsonPath))
         return null;
+    const skillId = path.basename(skillDir);
     let raw;
     try {
         raw = JSON.parse(readFileSync(skillJsonPath, 'utf-8'));
@@ -32,16 +24,18 @@ function loadOne(skillDir) {
         console.error(`[remixmate] failed to parse ${skillJsonPath}:`, err);
         return null;
     }
-    const entry = normalizeEntry(raw);
-    if (!entry) {
-        console.warn(`[remixmate] skipping ${raw.name}: missing entry/scriptPath`);
+    const errors = validateSkillJson(raw, skillId);
+    if (errors.length > 0) {
+        console.warn(`[remixmate] skipping ${skillId}:\n${errors.map((e) => `    - ${e}`).join('\n')}`);
         return null;
     }
+    // validateSkillJson guarantees a resolvable entry.
+    const entry = normalizeEntry(raw);
     const def = {
         name: raw.name,
         toolName: raw.toolName,
         description: raw.description,
-        parameters: raw.parameters,
+        parameters: raw.parameters ?? {},
         entry,
         skillDir,
     };

package/dist/skill-schema.d.ts

@@ -0,0 +1,65 @@
+/**
+ * Single source of truth for skill.json shape + validation.
+ *
+ * Imported directly by `registry.ts` (runtime loader) and — via the compiled
+ * `dist/skill-schema.js` — by `scripts/build-manifest.mjs` and `scripts/smoke.mjs`.
+ * Previously each of those reimplemented `normalizeEntry` and its own subset of
+ * field checks, so "valid at build" ≠ "loadable at runtime". Centralizing here
+ * means one definition of a well-formed skill.
+ *
+ * Error policy is the caller's choice: `validateSkillJson` returns a list of
+ * human-readable problems (empty = OK). The runtime loader skips + warns;
+ * the build treats them as fatal.
+ */
+export type SkillEntry = {
+    type: 'python';
+    scriptPath: string;
+} | {
+    type: 'http';
+    handler: string;
+} | {
+    type: 'builtin';
+    handler: string;
+};
+/**
+ * Skill 类别 — 区分"创作期 / 消费期 / 元数据型" skill。
+ *
+ * - "authoring": 创建 / 编辑模板期间使用，例如 template-registry / gen-script /
+ *                render-video（用于 try_render） / prepare-video-assets。
+ * - "consuming": 消费已有模板生成媒体，例如 export-jianying / video-parser /
+ *                web-capture（与"创建模板"无关，是消费侧场景）。
+ * - "asset":     生成单一类型素材的原子 skill：gen-image / gen-voice /
+ *                gen-video / gen-digital-human。authoring 也会用，但通过 stub
+ *                方式占位；consuming 场景下是真调用。
+ * - "meta":      元 skill（如未来加入 doc-only 的 template-creator）。
+ *
+ * 下游消费方（如 ab-template-studio）按 category 自动挑选白名单，避免每加一个
+ * skill 就要改两侧 hardcode。
+ */
+export type SkillCategory = 'authoring' | 'consuming' | 'asset' | 'meta';
+export declare const CATEGORY_VALUES: readonly ["authoring", "consuming", "asset", "meta"];
+export interface RawSkillJson {
+    name: string;
+    toolName: string;
+    description: string;
+    title?: string;
+    tier?: string;
+    category?: SkillCategory;
+    parameters?: Record<string, unknown>;
+    scriptPath?: string;
+    entry?: SkillEntry;
+    envVars?: string[];
+}
+export declare const TIER_VALUES: readonly ["atomic", "orchestration", "tool"];
+export declare const REQUIRED_SKILL_JSON_FIELDS: readonly ["name", "tier", "title", "description"];
+/**
+ * Resolve the dispatcher entry. A missing `entry` falls back to the legacy
+ * top-level `scriptPath`, treated as `{ type: 'python', scriptPath }` so older
+ * skills keep working untouched. Returns null when neither is present.
+ */
+export declare function normalizeEntry(raw: Pick<RawSkillJson, 'entry' | 'scriptPath'>): SkillEntry | null;
+/**
+ * Validate a parsed skill.json against the directory it lives in. Returns an
+ * array of problem strings; an empty array means the record is well-formed.
+ */
+export declare function validateSkillJson(raw: RawSkillJson, skillId: string): string[];

package/dist/skill-schema.js

@@ -0,0 +1,53 @@
+/**
+ * Single source of truth for skill.json shape + validation.
+ *
+ * Imported directly by `registry.ts` (runtime loader) and — via the compiled
+ * `dist/skill-schema.js` — by `scripts/build-manifest.mjs` and `scripts/smoke.mjs`.
+ * Previously each of those reimplemented `normalizeEntry` and its own subset of
+ * field checks, so "valid at build" ≠ "loadable at runtime". Centralizing here
+ * means one definition of a well-formed skill.
+ *
+ * Error policy is the caller's choice: `validateSkillJson` returns a list of
+ * human-readable problems (empty = OK). The runtime loader skips + warns;
+ * the build treats them as fatal.
+ */
+export const CATEGORY_VALUES = ['authoring', 'consuming', 'asset', 'meta'];
+export const TIER_VALUES = ['atomic', 'orchestration', 'tool'];
+export const REQUIRED_SKILL_JSON_FIELDS = ['name', 'tier', 'title', 'description'];
+/**
+ * Resolve the dispatcher entry. A missing `entry` falls back to the legacy
+ * top-level `scriptPath`, treated as `{ type: 'python', scriptPath }` so older
+ * skills keep working untouched. Returns null when neither is present.
+ */
+export function normalizeEntry(raw) {
+    if (raw.entry)
+        return raw.entry;
+    if (raw.scriptPath)
+        return { type: 'python', scriptPath: raw.scriptPath };
+    return null;
+}
+/**
+ * Validate a parsed skill.json against the directory it lives in. Returns an
+ * array of problem strings; an empty array means the record is well-formed.
+ */
+export function validateSkillJson(raw, skillId) {
+    const errors = [];
+    for (const field of REQUIRED_SKILL_JSON_FIELDS) {
+        const value = raw[field];
+        if (value == null || value === '')
+            errors.push(`skill.json missing required field '${field}'`);
+    }
+    if (raw.tier != null && !TIER_VALUES.includes(raw.tier)) {
+        errors.push(`skill.json.tier must be one of ${TIER_VALUES.join(' | ')}, got '${raw.tier}'`);
+    }
+    if (raw.category != null && !CATEGORY_VALUES.includes(raw.category)) {
+        errors.push(`skill.json.category must be one of ${CATEGORY_VALUES.join(' | ')}, got '${raw.category}'`);
+    }
+    if (raw.name && raw.name !== skillId) {
+        errors.push(`skill.json.name='${raw.name}' does not match directory name '${skillId}'`);
+    }
+    if (!normalizeEntry(raw)) {
+        errors.push("skill.json missing 'entry' (or legacy 'scriptPath')");
+    }
+    return errors;
+}

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@remixmate/cli",
-  "version": "0.1.0",
-  "description": "AI media generation skills for Claude Code / Codex — 9 skills covering image, video, voice, digital human, script, template binding, rendering, Jianying export, and video deconstruction.",
+  "version": "0.1.2",
+  "description": "AI media generation skills for Claude Code / Codex — 11 skills covering image, video, voice, digital human, web capture, script, template registry, rendering, Jianying export, and video deconstruction.",
   "type": "module",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
@@ -15,13 +15,14 @@
     "LICENSE"
   ],
   "scripts": {
-    "build": "tsc && node scripts/build-manifest.mjs",
+    "build": "node scripts/clean-dist.mjs && tsc && node scripts/build-manifest.mjs",
     "prepare": "npm run build",
     "list": "node dist/cli.js --list",
     "smoke": "node scripts/smoke.mjs",
+    "test:cli": "npm run build && node --test test/*.test.mjs",
     "test:validators": "PYTHONDONTWRITEBYTECODE=1 python3 scripts/test-validators.py",
     "test:template-pipeline": "PYTHONDONTWRITEBYTECODE=1 python3 scripts/test-template-pipeline.py",
-    "test:contracts": "PYTHONDONTWRITEBYTECODE=1 python3 skills/template-bind/scripts/check_contracts.py",
+    "test:contracts": "PYTHONDONTWRITEBYTECODE=1 python3 skills/template-registry/scripts/check_contracts.py",
     "clean": "node scripts/clean.mjs"
   },
   "keywords": [

package/skills/export-jianying/scripts/gen_jianying_draft.py

@@ -986,13 +986,13 @@ Scene fields:
         if not PRIVATE_TOKEN:
             print("❌ --from-job-id mode requires PRIV_TOKEN", file=sys.stderr)
             sys.exit(1)
-        # render_job_client lives in skills/template-bind/scripts/ — the
+        # render_job_client lives in skills/template-registry/scripts/ — the
         # shared location for cross-skill Python helpers (matches the pattern
         # render-video uses for the same import).
-        _template_bind_scripts = os.path.join(
-            os.path.dirname(__file__), "..", "..", "template-bind", "scripts"
+        _template_registry_scripts = os.path.join(
+            os.path.dirname(__file__), "..", "..", "template-registry", "scripts"
         )
-        sys.path.insert(0, _template_bind_scripts)
+        sys.path.insert(0, _template_registry_scripts)
         from render_job_client import get_plan as rjc_get_plan
         try:
             render_plan_str = rjc_get_plan(args.from_job_id, PRIVATE_TOKEN)

package/skills/export-jianying/skill.json

@@ -2,6 +2,7 @@
   "name": "export-jianying",
   "toolName": "export_jianying",
   "tier": "orchestration",
+  "category": "consuming",
   "title": "Jianying (CapCut) Draft Export",
   "description": "Jianying (CapCut) draft export: package asset URLs into a draft ZIP that Jianying can import. Supports automatic conversion from a RenderPlan.",
   "envVars": ["PRIV_TOKEN", "MM_API_BASE_URL", "AGENT_NAME"],

package/skills/gen-digital-human/SKILL.md

@@ -19,7 +19,9 @@ triggers:
 
 # Digital-Human Skill
 
-Wraps ab-api's digital-human endpoints (the same ones the web studio uses), authenticated with the **Tianyan privateToken**. Two providers: **Jimeng** (image-driven) and **HiFly** (video-driven).
+Wraps ab-api's digital-human endpoints (the same ones the web studio uses), authenticated with the **Tianyan privateToken**. Two providers: **Jimeng** (image-driven) and **HiFly** (video-driven). Generation is async — the handler submits the task and polls `/digital-human/video/status` until completion.
+
+> This skill was migrated from a Python script to an ab-skill CLI HTTP handler (`entry.type: http`). The agent invocation is unchanged (same tool name `gen_digital_human`, same params as in `skill.json`); local repro goes through `ab-skill gen-digital-human ...`.
 
 ## Capabilities
 
@@ -34,54 +36,52 @@ Wraps ab-api's digital-human endpoints (the same ones the web studio uses), auth
 
 ## Auth & environment
 
-No skill-local env file — the executing process inherits the system environment. Examples below say `python`; on macOS you may need `python3`.
+No skill-local env file — the executing process inherits the system environment.
 
 - **Enterprise OpenClaw**: auth is already injected, **no need** for `PRIV_TOKEN` / `--priv-token`.
-- **Other environments**: configure the token. Without a token, non-interactive runs fail; interactive ones may prompt.
+- **Other environments**: configure the token. Without a token, non-interactive runs fail.
 
 | Env var | Description | Default |
 |---------|-------------|---------|
 | `PRIV_TOKEN` | Tianyan token; `--priv-token` overrides | none |
-| `MM_API_BASE_URL` | API root | see `gen_digital_human_video.py` default |
+| `MM_API_BASE_URL` | API root; `--api-base-url` overrides | `http://localhost:2999/api` |
 | `AGENT_NAME` | Optional `x-invoke-agent` header | none |
 
 ## Operations
 
-**Script path**: read the system-injected `Base directory for this skill: <path>` as `<SkillDir>`. Always use `<SkillDir>/scripts/gen_digital_human_video.py`. Do not hardcode paths.
+By default only the URL is printed; generation is async and the handler polls until done (typically 1–5 minutes), emitting `__progress__` lines. The resulting video URL is cloud-persisted — show it directly, no download needed.
 
 ### 1. List avatars
 
 ```bash
-python3 <SkillDir>/scripts/gen_digital_human_video.py --list-avatars
+ab-skill gen-digital-human --list-avatars
 ```
 
 Optional filters:
 
 ```bash
 # Filter by source (jimeng = image-driven, hifly = video-driven)
-python3 <SkillDir>/scripts/gen_digital_human_video.py --list-avatars --source jimeng
-python3 <SkillDir>/scripts/gen_digital_human_video.py --list-avatars --source hifly
+ab-skill gen-digital-human --list-avatars --source jimeng
+ab-skill gen-digital-human --list-avatars --source hifly
 
 # Filter by gender
-python3 <SkillDir>/scripts/gen_digital_human_video.py --list-avatars --gender female
+ab-skill gen-digital-human --list-avatars --gender female
 
 # Show your custom avatars
-python3 <SkillDir>/scripts/gen_digital_human_video.py --list-avatars --mine
+ab-skill gen-digital-human --list-avatars --mine
 
 # Filter by name
-python3 <SkillDir>/scripts/gen_digital_human_video.py --list-avatars --name "alice"
+ab-skill gen-digital-human --list-avatars --name "alice"
 ```
 
-> Custom avatars require `--mine`. When generating a video the script auto-falls back from the public list to `mine: true` if needed.
+> Custom avatars require `--mine`. When generating a video the handler auto-falls back from the public list to `mine: true` if needed.
 
 ### 2. Generate a digital-human video
 
-By default only the URL is printed; pass `--download` (and optional `--output`) to save locally. Generation is async; the script polls until done (typically 1–5 minutes).
-
 #### TTS mode
 
 ```bash
-python3 <SkillDir>/scripts/gen_digital_human_video.py \
+ab-skill gen-digital-human \
   --avatar-id 7 \
   --text "Hi everyone, welcome to the live stream — today I'll introduce a new product." \
   --voice-id "male-qn-qingse"
@@ -90,7 +90,7 @@ python3 <SkillDir>/scripts/gen_digital_human_video.py \
 #### TTS + custom voice + aspect ratio
 
 ```bash
-python3 <SkillDir>/scripts/gen_digital_human_video.py \
+ab-skill gen-digital-human \
   --avatar-id 7 \
   --text "Hi class, here's our brand-new course." \
   --voice-id "female-shaonv" \
@@ -100,37 +100,19 @@ python3 <SkillDir>/scripts/gen_digital_human_video.py \
 #### Audio-driven mode
 
 ```bash
-python3 <SkillDir>/scripts/gen_digital_human_video.py \
+ab-skill gen-digital-human \
   --avatar-id 39 \
   --source hifly \
   --audio-url "https://example.com/voice.mp3" \
   --aspect-ratio "16:9"
 ```
 
-#### Download to disk
-
-```bash
-python3 <SkillDir>/scripts/gen_digital_human_video.py \
-  --avatar-id 7 \
-  --text "Hello world" \
-  --download \
-  --output "digital_human_output.mp4"
-```
-
 ### 3. Check job status
 
 ```bash
-# Status only
-python3 <SkillDir>/scripts/gen_digital_human_video.py \
-  --check-status --generation-id 123
-
-# Download once it's done
-python3 <SkillDir>/scripts/gen_digital_human_video.py \
-  --check-status --generation-id 123 --download --output result.mp4
+ab-skill gen-digital-human --check-status --generation-id 123
 ```
 
-For the full flag list: `python3 <SkillDir>/scripts/gen_digital_human_video.py --help`.
-
 ## Common CLI flags
 
 ### List avatars
@@ -155,11 +137,8 @@ For the full flag list: `python3 <SkillDir>/scripts/gen_digital_human_video.py -
 | `--source` | `jimeng` / `hifly` (inferable from avatar) | auto |
 | `--aspect-ratio` | `9:16` / `16:9` / `3:4` / `1:1` | avatar's default |
 | `--prompt` | Action prompt (e.g. "more hand gestures") | none |
-| `--download` | Download the video locally | off |
-| `-o` / `--output` | Download path (only with `--download`) | `digital_human_video.mp4` |
-| `--poll-interval` | Polling interval (seconds) | `5` |
-| `--max-wait` | Max wait time (seconds) | `600` |
-| `--private-token` | Override token | see env vars |
+| `--api-base-url` | Override API root | see env vars |
+| `--priv-token` | Override token | see env vars |
 
 ### Check status
 
@@ -167,8 +146,6 @@ For the full flag list: `python3 <SkillDir>/scripts/gen_digital_human_video.py -
 |------|-------------|---------|
 | `--check-status` | Enter status-check mode | — |
 | `--generation-id` | Job id (required) | — |
-| `--download` | Download when finished | off |
-| `-o` / `--output` | Download path | `digital_human_video.mp4` |
 
 ## Typical flows
 
@@ -180,7 +157,7 @@ For the full flag list: `python3 <SkillDir>/scripts/gen_digital_human_video.py -
 3. Confirm or polish the speech text
 4. (Optional) pick a voice → use gen-voice --list-voices
 5. Generate → --avatar-id <id> --text "..." --voice-id "female-shaonv"
-6. Show URL or local path
+6. Show URL
 ```
 
 ### Flow B — Audio-driven
@@ -189,7 +166,7 @@ For the full flag list: `python3 <SkillDir>/scripts/gen_digital_human_video.py -
 1. List avatars → --list-avatars [--mine]
 2. Prepare an audio URL (gen-voice can produce one)
 3. Generate → --avatar-id <id> --audio-url "https://..." [--source hifly]
-4. Show URL or local path
+4. Show URL
 ```
 
 ## Text guidance (TTS)
@@ -203,7 +180,7 @@ For the full flag list: `python3 <SkillDir>/scripts/gen_digital_human_video.py -
 - **401** / **token missing** (non-OpenClaw): set `PRIV_TOKEN`.
 - **Business `code != 0`**: read `msg` on stderr.
 - **429**: rate-limited; retry later.
-- **Generation timeout**: increase `--max-wait`, or use `--check-status` later.
+- **Generation timeout**: the handler caps polling at ~10 minutes; use `--check-status --generation-id <id>` later.
 - **Empty TTS text**: provide non-empty `--text` or use `--audio-url`.
 - **Invalid voice id**: re-check via `gen-voice --list-voices`.
 - **Avatar id not found**: re-check via `--list-avatars` (or `--list-avatars --mine`).

package/skills/gen-digital-human/skill.json

@@ -2,10 +2,11 @@
   "name": "gen-digital-human",
   "toolName": "gen_digital_human",
   "tier": "atomic",
+  "category": "asset",
   "title": "Digital-Human Talking-Head",
   "description": "Digital-human video: list available avatars; produce a talking-head video from text via TTS, or drive an avatar from an existing audio URL.",
   "envVars": ["PRIV_TOKEN", "MM_API_BASE_URL", "AGENT_NAME"],
-  "scriptPath": "scripts/gen_digital_human_video.py",
+  "entry": { "type": "http", "handler": "gen-digital-human" },
   "parameters": {
     "type": "object",
     "properties": {
@@ -16,7 +17,8 @@
       "text": { "type": "string", "description": "Narration text (TTS mode)" },
       "audio_url": { "type": "string", "description": "Audio URL (audio-driven mode)" },
       "voice_id": { "type": "string", "description": "Voice id" },
-      "aspect_ratio": { "type": "string", "description": "Aspect ratio" }
+      "aspect_ratio": { "type": "string", "description": "Aspect ratio" },
+      "json_output": { "type": "boolean", "description": "Emit a JSON result (generate: { url, generationId }; list: { avatars }; check-status: { status, url }) instead of human-readable output" }
     },
     "required": []
   }

package/skills/gen-digital-human/version.json

@@ -2,6 +2,6 @@
   "skillName": "gen-digital-human",
   "repoName": "agent-skill-media-maker",
   "skillId": "336",
-  "version": "V5",
+  "version": "V7",
   "skillDescription": "数字人口播视频技能，支持查询形象、TTS 口播、音频驱动口播和查询生成状态（调用 ab-api 数字人接口，即梦 / 飞影）。\n\n当用户提到以下任何需求时，立即使用本 skill：\n- 数字人、数字人视频、数字人口播、生成数字人视频\n- 用户提供已有音频 URL（MP3 等）、用外链音频驱动数字人口型\n- AI 主播、虚拟主播、虚拟人物视频、口播视频\n- 让数字人说话、让虚拟人说一段话、让 AI 人物播报\n- 查看/列出数字人形象、有哪些数字人可以用\n- 使用即梦/飞影数字人\n\n即使用户没有明确说「使用 AI」，只要他们想要让一个虚拟人物朗读/播报一段文字并生成视频，也要使用本 skill。"
 }

package/skills/gen-image/SKILL.md

@@ -23,7 +23,7 @@ Wraps ab-api's `POST /model/genImg` (the same endpoint the web studio uses), aut
 
 ## Models and sizes
 
-Aligned with `gen_image.py`'s `GEN_IMG_MODEL_PRESETS` and the backend `ModelGenImgDTO`:
+Aligned with the gen-image handler's model presets and the backend `ModelGenImgDTO`:
 
 | LiteLLM `model` | Display name | Provider |
 |-----------------|--------------|----------|
@@ -46,7 +46,7 @@ No skill-local env file — the executing process inherits the system environmen
 |---------|-------------|---------|
 | `PRIV_TOKEN` | Tianyan token; `--priv-token` overrides | none |
 | `MM_IMAGE_MODEL` | Default model id | `doubao/doubao-seedream-4-5-251128` |
-| `MM_API_BASE_URL` | API root | see `gen_image.py` default |
+| `MM_API_BASE_URL` | API root; `--api-base-url` overrides | `http://localhost:2999/api` |
 | `AGENT_NAME` | Optional `x-invoke-agent` header | none |
 
 ## Operations

package/skills/gen-image/skill.json

@@ -2,6 +2,7 @@
   "name": "gen-image",
   "toolName": "gen_image",
   "tier": "atomic",
+  "category": "asset",
   "title": "AI Image Generation",
   "description": "AI image generation: produce an image from a text prompt. Supports Seedream and Gemini models, plus image-to-image with reference images.",
   "envVars": ["PRIV_TOKEN", "MM_API_BASE_URL", "AGENT_NAME", "MM_IMAGE_MODEL"],
@@ -15,7 +16,8 @@
       "resolution": { "type": "string", "enum": ["1K", "2K", "4K"], "description": "Output resolution (Gemini only)" },
       "n": { "type": "number", "description": "Number of images, 1-4" },
       "reference": { "type": "string", "description": "Reference image path or URL" },
-      "negative_prompt": { "type": "string", "description": "Negative prompt — content to avoid" }
+      "negative_prompt": { "type": "string", "description": "Negative prompt — content to avoid" },
+      "json_output": { "type": "boolean", "description": "Emit a JSON result ({ urls: [...] }) instead of human-readable output" }
     },
     "required": ["prompt"]
   }

package/skills/gen-image/version.json

@@ -2,6 +2,6 @@
   "skillName": "gen-image",
   "repoName": "agent-skill-media-maker",
   "skillId": "337",
-  "version": "V6",
+  "version": "V8",
   "skillDescription": "AI 生图技能，根据文字描述生成图片，也支持参考图进行图生图（调用 ab-api /model/genImg，支持 Seedream 与 Gemini）。\n\n当用户提到以下任何需求时，立即使用本 skill：\n- AI 生图、AI 画图、文生图、文字生成图片、生成图像、帮我画、生成一张图\n- 图生图、以图生图、参考图、风格迁移、图片变体\n- 使用 doubao / 豆包 / seedream、Gemini 等生成图片\n- 用户提供图片提示词并希望生成图片\n\n即使用户没有明确说「使用 AI」，只要他们想要根据描述生成图片，也要使用本 skill。"
 }

package/skills/gen-script/SKILL.md

@@ -28,11 +28,11 @@ Turns a user-supplied **topic** into a **Video DSL v1alpha1** JSON describing wh
 
 ## DSL schema
 
-The full schema is `template-bind` skill's `video_dsl/schema/video-dsl-v1alpha1.json`; examples live in `video_dsl/schema/examples/` (locate them through `template-bind`'s `Base directory for this skill`).
+The full schema is `template-registry` skill's `video_dsl/schema/video-dsl-v1alpha1.json`; examples live in `video_dsl/schema/examples/` (locate them through `template-registry`'s `Base directory for this skill`).
 
 ## Agent behavior: DSL generation when a template is selected
 
-**When the user explicitly specifies a template id, the agent must first read the existing `*.dsl.json` and `*.binding.json` examples in `template-bind`'s `video_dsl/schema/examples/`, then generate the DSL in the template's native shape using both those examples and the template's `template.json`. The agent must not generate the DSL from scratch ignoring the examples, and must not produce a generic DSL first and rely on `template-bind` to force-match the template later.**
+**When the user explicitly specifies a template id, the agent must first read the existing `*.dsl.json` and `*.binding.json` examples in `template-registry`'s `video_dsl/schema/examples/`, then generate the DSL in the template's native shape using both those examples and the template's `template.json`. The agent must not generate the DSL from scratch ignoring the examples, and must not produce a generic DSL first and rely on `template-registry` to force-match the template later.**
 
 The intent is to reuse the validated example shapes already in the repo and to avoid the failure mode where "the generic DSL looks compatible on the surface, but is missing template-specific fields, has the wrong nesting, or binds incorrectly — only to fail later at binding or render time". Examples:
 
@@ -41,7 +41,7 @@ The intent is to reuse the validated example shapes already in the repo and to a
 
 ### Mandatory steps
 
-1. Visit `template-bind/video_dsl/schema/examples/` and locate the closest existing `*.dsl.json` and `*.binding.json` for the requested template.
+1. Visit `template-registry/video_dsl/schema/examples/` and locate the closest existing `*.dsl.json` and `*.binding.json` for the requested template.
 2. Read those examples and understand the actual DSL shape, the `templateData` fields, the scene organization, and the binding style the template uses.
 3. Read the template's `template.json`.
 4. Combine the examples and `template.json` to understand the template's `slotMapping`, `requiredProps`, `optionalProps`, `propExtractors`, `assetRequirements`, `supportedAspectRatios`, and `scenePatterns`.
@@ -51,15 +51,15 @@ The intent is to reuse the validated example shapes already in the repo and to a
 
 ### Hard constraints
 
-- **Forbidden**: the user specified a template, but the agent generated the DSL without reading any of the existing examples under `template-bind/video_dsl/schema/examples/`.
+- **Forbidden**: the user specified a template, but the agent generated the DSL without reading any of the existing examples under `template-registry/video_dsl/schema/examples/`.
 - **Forbidden**: only reading `template.json` while ignoring the existing `*.dsl.json` and `*.binding.json` examples.
-- **Forbidden**: the user specified a template, but the agent first generated a generic DSL and then passed `--template-id` to `template-bind` to force-bind it.
+- **Forbidden**: the user specified a template, but the agent first generated a generic DSL and then passed `--template-id` to `template-registry` to force-bind it.
 - **Forbidden**: continuing into binding / rendering despite knowing that template-specific fields, scene shapes, or binding details are missing.
 - **Forbidden**: silently degrading to a generic DSL because the current script cannot support a template, leaving the failure to the downstream stage.
 
 ### When a template is not yet supported
 
-If `template-bind/video_dsl/schema/examples/` has no matching example for the requested template, or `gen_script.py` cannot yet build the required DSL shape, the agent must clearly tell the user "this template is not yet supported for auto-generation from existing examples" and explain what key fields, structure, or binding info are missing. Possible next steps:
+If `template-registry/video_dsl/schema/examples/` has no matching example for the requested template, or `gen_script.py` cannot yet build the required DSL shape, the agent must clearly tell the user "this template is not yet supported for auto-generation from existing examples" and explain what key fields, structure, or binding info are missing. Possible next steps:
 
 1. Ask the user to switch to a template that has an example and is already supported.
 2. Have the agent take the closest `*.dsl.json` / `*.binding.json` as a reference and hand-craft the required DSL structure for this template, then show it to the user for confirmation.
@@ -67,7 +67,7 @@ If `template-bind/video_dsl/schema/examples/` has no matching example for the re
 
 ### Design principle
 
-When the user specifies a template, `gen-script`'s goal is no longer "produce a generally-compatible DSL" but "produce a template-native DSL based on the existing examples in `template-bind`".
+When the user specifies a template, `gen-script`'s goal is no longer "produce a generally-compatible DSL" but "produce a template-native DSL based on the existing examples in `template-registry`".
 
 ## Authentication & environment
 
@@ -75,16 +75,16 @@ This skill does not hit any external API; no token required. The script only doe
 
 | Env var | Description | Default |
 |---------|-------------|---------|
-| `VIDEO_DSL_SCHEMA_PATH` | DSL schema file path. | Reads `template-bind` skill's `video_dsl/schema/video-dsl-v1alpha1.json` by default. |
+| `VIDEO_DSL_SCHEMA_PATH` | DSL schema file path. | Reads `template-registry` skill's `video_dsl/schema/video-dsl-v1alpha1.json` by default. |
 
 ## Agent behavior: script confirmation
 
-**After the agent has generated a DSL it must first show the script summary to the user and get explicit confirmation before forwarding to downstream skills (template-bind / prepare-video-assets / render-video).** This lets the user review and adjust the scene structure, narration text, etc. before any asset is produced.
+**After the agent has generated a DSL it must first show the script summary to the user and get explicit confirmation before forwarding to downstream skills (template-registry / prepare-video-assets / render-video).** This lets the user review and adjust the scene structure, narration text, etc. before any asset is produced.
 
 ### Confirmation flow
 
 1. After the agent generates or modifies the DSL, **show the script summary first; do not pass it downstream yet**.
-2. Wait for the user to explicitly confirm (e.g. "OK", "looks good", "continue with template binding") before handing it to `prepare-video-assets` (or `template-bind` for a list-only lookup).
+2. Wait for the user to explicitly confirm (e.g. "OK", "looks good", "continue with template binding") before handing it to `prepare-video-assets` (or `template-registry` for a list-only lookup).
 3. If the user asks for changes (adjust narration, add or remove scenes, change durations), the agent updates the DSL and shows the summary again, then waits for confirmation once more.
 
 ### Summary content
@@ -174,7 +174,7 @@ Env vars `STUB_IMAGE_URL` / `STUB_VIDEO_URL` also work — their priority is low
 
 1. **Script path**: read the system-injected `Base directory for this skill: <path>` as `<SkillDir>`. Every command below uses `<SkillDir>/scripts/gen_script.py`; never hard-code paths.
 2. **Understand the request**: extract topic, target platform, duration, style, audience, etc.
-3. **If the user specifies a template, read it first**: load the matching `template.json` via `template-bind` and confirm its template-specific fields and asset requirements. Do not skip this step.
+3. **If the user specifies a template, read it first**: load the matching `template.json` via `template-registry` and confirm its template-specific fields and asset requirements. Do not skip this step.
 4. **Generate the DSL**: pick the right command or DSL shape for the target template (see the per-template commands below).
 5. **Schema validation**: make sure the output DSL conforms to v1alpha1.
 6. **User confirmation**: show the script summary and wait for confirmation, per the rules above.
@@ -208,7 +208,7 @@ python3 <SkillDir>/scripts/gen_script.py \
   --output output.dsl.json
 ```
 
-5. **Result handling**: pass the generated DSL to `template-bind` for template lookup, or directly to `prepare-video-assets` (which auto-invokes template binding when `template_id` is provided).
+5. **Result handling**: pass the generated DSL to `template-registry` for template lookup, or directly to `prepare-video-assets` (which auto-invokes template binding when `template_id` is provided).
 
 ## Common CLI flags
 
@@ -280,4 +280,4 @@ Mirrors the `gen-image` skill and `GEN_IMG_MODEL_PRESETS` in `gen_image.py`. **O
 | `knowledge_card_script.json` | Intermediate knowledge-card script result. |
 | `script_knowledge_card.json` | Full knowledge-card script example. |
 
-These JSON files are reference data for development / debugging; they do not participate in runtime logic. The authoritative DSL examples live under `template-bind/video_dsl/schema/examples/`.
+These JSON files are reference data for development / debugging; they do not participate in runtime logic. The authoritative DSL examples live under `template-registry/video_dsl/schema/examples/`.